Which versions of @zapier/eslint-plugin-zapier are malicious?

The following npm versions of @zapier/eslint-plugin-zapier are flagged malicious: 11.0.3, 11.0.4, 11.0.5. Treat any of these as compromised.

How do I remediate @zapier/eslint-plugin-zapier if I installed it?

@zapier/eslint-plugin-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/eslint-plugin-zapier — how do I know if it already compromised me?

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

Yes — @zapier/eslint-plugin-zapier is associated with the GHSA-rfrc-w2hh-54fr 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/eslint-plugin-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/eslint-plugin-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/eslint-plugin-zapier across your stack and pipelines.

Malicious package

@zapier/eslint-plugin-zapiernpm

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

MAL-2025-190763

Immediate action

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

npm uninstall @zapier/eslint-plugin-zapier

What this malware does

The package @zapier/eslint-plugin-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

11.0.311.0.411.0.5

Indicators of compromise (SHA-256)

dcf962219031c8bc253fbb2ad41cc1fc126b81ff862f7d75bb6d17d124aa7848

c4f3af0dfab295d120b932902816e065f092b48671909a971a2994cb3cb5afd6

e181a92f4aef303d0c1d5f4cf963ed6c659ebdfa53778e082ad87479e35aeaf0

53f784ee16c8b214e965b83410a59bca625c2382dd1a70db45a43d345f1d9eaa

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/eslint-plugin-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/eslint-plugin-zapier across your stack and pipelines.
If you installed it — respond
@zapier/eslint-plugin-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/eslint-plugin-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/eslint-plugin-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/eslint-plugin-zapier on npm has been identified as a malicious package (versions 11.0.3, 11.0.4, 11.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rfrc-w2hh-54fr

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zapier/eslint-plugin-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