NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

fuzzy-findernpm

Advisory published Updated

fuzzy-finder is a confirmed malicious npm package (MAL-2025-191099) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.5, 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fuzzy-finder (npm)

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
  1. Find it

    Search your lockfiles and build artifacts for fuzzy-finder (2 malicious versions).

  2. 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.

  3. Did it already run?

    If fuzzy-finder was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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.

Explore

fuzzy-finder (npm) malicious package — MAL-2025-191099 | O3 Security