Which versions of zapier-scripts are malicious?

The following npm versions of zapier-scripts are flagged malicious: 7.8.3, 7.8.4. Treat any of these as compromised.

How do I remediate zapier-scripts if I installed it?

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

If zapier-scripts 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-scripts part of a known attack campaign?

Yes — zapier-scripts is associated with the GHSA-9mg9-5wqh-46qx 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-scripts 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-scripts (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zapier-scripts across your stack and pipelines.

Malicious package

zapier-scriptsnpm

Malicious code in zapier-scripts (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190861

Immediate action

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

npm uninstall zapier-scripts

What this malware does

The package zapier-scripts 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

7.8.37.8.4

Indicators of compromise (SHA-256)

a7ff5378c64d4e7f1b2a7f36f2ed69279219f697dd2cff8098a4de7e70f34ff0

c3ba8a867b632a8d6da937fdbfc075adef06017c7ab8a6b17924da7ac6d13470

68dad31f8438dd052dc0b6abdfaefadf6782d004db4853d483c3bac5c77e5e0d

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-scripts (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zapier-scripts across your stack and pipelines.
If you installed it — respond
zapier-scripts 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-scripts 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-scripts 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-scripts on npm has been identified as a malicious package (versions 7.8.3, 7.8.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9mg9-5wqh-46qx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zapier-scripts-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