@zapier/mcp-integrationnpm
Advisory published Updated
@zapier/mcp-integration is a confirmed malicious npm package (MAL-2025-190918) that steals credentials and exfiltrates sensitive data (malicious versions 3.0.1, 3.0.2, 3.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @zapier/mcp-integration (npm)
What this malware does
The package @zapier/mcp-integration was found to contain malicious code.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @zapier/mcp-integration (3 malicious versions).
If you installed it — respond
@zapier/mcp-integration 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/mcp-integration 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
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @zapier/mcp-integration-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.