Which versions of fuzzy-finder are malicious?

The following npm versions of fuzzy-finder are flagged malicious: 1.0.5, 1.0.6. Treat any of these as compromised.

How do I remediate fuzzy-finder if I installed it?

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

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

Yes — fuzzy-finder is associated with the GHSA-m66q-4c3m-7632 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 fuzzy-finder 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 fuzzy-finder (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fuzzy-finder across your stack and pipelines.

Malicious package

fuzzy-findernpm

Malicious code in fuzzy-finder (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191099

Immediate action

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

npm uninstall fuzzy-finder

What this malware does

The package fuzzy-finder 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

2 flagged

1.0.51.0.6

Indicators of compromise (SHA-256)

b064e69feb20e776021d6962b2b92236a4dbe803610364feb603e47595cc2473

aa38bb4eacd4b40312a27b1e9e78a7048240c477b3c535ef7d5ed89e5d268207

ebe54886101432e7b0f5fad8d751ca5493bfe6f8e067ab2010ef1a8aaa4cf435

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

Campaign

GHSA-m66q-4c3m-7632

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks fuzzy-finder-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