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/browserslist-config-zapiernpm

Advisory published Updated

@zapier/browserslist-config-zapier is a confirmed malicious npm package (MAL-2025-190762) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.3, 1.0.4, 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zapier/browserslist-config-zapier (npm)

MAL-2025-190762
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @zapier/browserslist-config-zapier

What this malware does

The package @zapier/browserslist-config-zapier 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.0.31.0.41.0.5

Indicators of compromise (SHA-256)

911593a8af4f2dab2b14579f1f1014294cc5d8109cb6e5ee9d7ba33aa7c3fe8b
a5146756159d44339572781661307fc36bb08adb636158ee54628f774506ae47
9db7871e6c9737ce3ba75d2b223265c3f1db6d133f6f8a936105ea867d7941c4
e10048643882817eb78f21680cf3cc9b40014fdede7b4336dbd46998c9abfd01

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

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

Campaign

GHSA-x7fh-q8wq-96rx

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @zapier/browserslist-config-zapier-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

Explore

All malware advisories How O3 detects malware Vulnerability database
@zapier/browserslist-config-zapier (npm) malicious package — MAL-2025-190762 | O3 Security