Which versions of sufetch are malicious?

The following npm versions of sufetch are flagged malicious: 0.4.1. Treat any of these as compromised.

How do I remediate sufetch if I installed it?

sufetch 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 sufetch — how do I know if it already compromised me?

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

Yes — sufetch is associated with the GHSA-x8hh-3gmf-mm9r 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 sufetch 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 sufetch (version 0.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sufetch across your stack and pipelines.

Malicious package

sufetchnpm

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

MAL-2025-191431

Immediate action

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

npm uninstall sufetch

What this malware does

The package sufetch 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.4.1

Indicators of compromise (SHA-256)

bf6e70d8dc6151899a1fa4429627f997c0eee9e6b793b799a74465919d790e58

96568dd37a7486f46399a553eecede4295c1c52321560fb15faaa4525e898642

8efd418803202b34256057a848e0e9fbd6ad735dd0a011b4e7ca9cd46d088b39

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 sufetch (version 0.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sufetch across your stack and pipelines.
If you installed it — respond
sufetch 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 sufetch 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 sufetch 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. sufetch on npm has been identified as a malicious package (version 0.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x8hh-3gmf-mm9r

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sufetch-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