Which versions of toonfetch are malicious?

The following npm versions of toonfetch are flagged malicious: 0.3.2. Treat any of these as compromised.

How do I remediate toonfetch if I installed it?

toonfetch is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed toonfetch — how do I know if it already compromised me?

If toonfetch 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 toonfetch part of a known attack campaign?

Yes — toonfetch is associated with the GHSA-xwjf-5fpw-52jq 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 toonfetch 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 toonfetch (version 0.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging toonfetch across your stack and pipelines.

Malicious package

toonfetchnpm

Malicious code in toonfetch (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191436

Immediate action

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

npm uninstall toonfetch

What this malware does

The package toonfetch was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.3.2

Indicators of compromise (SHA-256)

8106ab778e61e473ab5db57920a7cd38a6d4741aa5fbc3286a7f53ad5052d7e8

8f1f64461d3d386d7d2181a773a457fff937a380dac27240d83dfca672319ee9

34259fc3807663e7c172b15e761dc591d545f94c836f98941c9c570667b3e0f4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for toonfetch (version 0.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging toonfetch across your stack and pipelines.
If you installed it — respond
toonfetch is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If toonfetch 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 toonfetch 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. toonfetch on npm has been identified as a malicious package (version 0.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xwjf-5fpw-52jq

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks toonfetch-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring