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/ai-actionsnpm

Advisory published Updated

@zapier/ai-actions is a confirmed malicious npm package (MAL-2025-190830) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.18, 0.1.19, 0.1.20). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zapier/ai-actions (npm)

MAL-2025-190830
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @zapier/ai-actions

What this malware does

The package @zapier/ai-actions 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
0.1.180.1.190.1.20

Indicators of compromise (SHA-256)

16ee3609ca3d60178d0ca2b08f73affeee1debb94355d5d7cd0d8fcee838b897
a316e279c8bb03071a6e5197270ffbb95c5f23592a64c504271f47e0f9adb11f
a7ab97e0203044e214b4c17dfd9e0ef66f788799b8b128234c6c3953b3124aaa
118e185122f22f3a41f89879a11ed95d0695bcdd23eb1c846122b2f098c960c2

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

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

Campaign

GHSA-qpwh-h9px-43pw

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @zapier/ai-actions-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/ai-actions (npm) malicious package — MAL-2025-190830 | O3 Security