NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @zapier published 10 malicious packages. See the full campaign →
Malicious package

@zapier/secret-scrubbernpm

Advisory published Updated

@zapier/secret-scrubber is a confirmed malicious npm package (MAL-2025-190691) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.3, 1.1.4, 1.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zapier/secret-scrubber (npm)

MAL-2025-190691
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @zapier/secret-scrubber

What this malware does

The package @zapier/secret-scrubber 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

3 flagged
1.1.31.1.41.1.5

Indicators of compromise (SHA-256)

e92f2ea9639cafd208975780e2ac850ec257d2fd3e6ad2db327b0c8250cbcbb9
c109e973086267fe5b99a110c559267a26254a0bb87dcffbaf3fb69ea4bbca75
3abd19ac9c787ed3f19f74709ee3db98f129df4c9fb12e479b6f34f74bccc641
bcf94c5df99350baff9311f5d2b453ed296e3df621478a4fbfd2e66864190521

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @zapier/secret-scrubber (3 malicious versions).

  2. If you installed it — respond

    @zapier/secret-scrubber 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 @zapier/secret-scrubber 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. @zapier/secret-scrubber on npm has been identified as a malicious package (versions 1.1.3, 1.1.4, 1.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xg54-qg46-ph4x

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @zapier/secret-scrubber-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

@zapier/secret-scrubber (npm) malicious package — MAL-2025-190691 | O3 Security