Which versions of @zapier/browserslist-config-zapier are malicious?

The following npm versions of @zapier/browserslist-config-zapier are flagged malicious: 1.0.3, 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate @zapier/browserslist-config-zapier if I installed it?

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

I already installed @zapier/browserslist-config-zapier — how do I know if it already compromised me?

If @zapier/browserslist-config-zapier 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 @zapier/browserslist-config-zapier part of a known attack campaign?

Yes — @zapier/browserslist-config-zapier is associated with the GHSA-x7fh-q8wq-96rx 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 @zapier/browserslist-config-zapier 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 @zapier/browserslist-config-zapier (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zapier/browserslist-config-zapier across your stack and pipelines.

Malicious package

@zapier/browserslist-config-zapiernpm

Malicious code in @zapier/browserslist-config-zapier (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zapier/browserslist-config-zapier (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zapier/browserslist-config-zapier across your stack and pipelines.
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.
Did it already run?
If @zapier/browserslist-config-zapier 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 @zapier/browserslist-config-zapier 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. @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