Which versions of toskasldfjaldf-parser are malicious?

The following npm versions of toskasldfjaldf-parser are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate toskasldfjaldf-parser if I installed it?

Remove toskasldfjaldf-parser from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed toskasldfjaldf-parser — how do I know if it already compromised me?

If toskasldfjaldf-parser was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is toskasldfjaldf-parser part of a known attack campaign?

Yes — toskasldfjaldf-parser is associated with the GHSA-4gx3-vqpp-3c9g, RLMA-2025-05531, RLUA-2025-05969 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find toskasldfjaldf-parser across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for toskasldfjaldf-parser (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging toskasldfjaldf-parser across your stack and pipelines.

Malicious package

toskasldfjaldf-parsernpm

toskasldfjaldf-parser is a confirmed malicious npm package (MAL-2025-48006) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in toskasldfjaldf-parser (npm)

MAL-2025-48006

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall toskasldfjaldf-parser

What this malware does

The package communicates with a domain associated with malicious activity.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

e759a5c9e8da467a90adc10a682a68df15a878213a5e38a2a5dad06f95740103

6c6aad5393a291e308c37f0476a7ab4a22df38a7a85e1655e7e5e95d5ac2530a

6ec54c8a0c67fa35352b90b0d8fde401729d17a90338896573fcba05fef0a7b9

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for toskasldfjaldf-parser (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging toskasldfjaldf-parser across your stack and pipelines.
If you installed it — respond
Remove toskasldfjaldf-parser from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If toskasldfjaldf-parser was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks toskasldfjaldf-parser before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. toskasldfjaldf-parser on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4gx3-vqpp-3c9gRLMA-2025-05531RLUA-2025-05969

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks toskasldfjaldf-parser-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database