Malicious Code Detected in @zapier/mcp-integration Package - Security Alert

@zapier/mcp-integration Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190918: Malicious code in @zapier/mcp-integration (npm). Affects @zapier/mcp-integration versions 3.0.1 – 3.0.3. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @zapier/mcp-integration package is a Node.js library used for integrating with Zapier's services. It provides developers with tools to automate workflows and connect various applications. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to users who rely on it for their applications.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zapier/mcp-integration package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The affected versions are 3.0.1 and 3.0.3, which have been flagged by Amazon Inspector as containing this malicious code.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @zapier/mcp-integration

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can remove the @zapier/mcp-integration package from your project until a secure version is confirmed. This can be done using the command: npm uninstall @zapier/mcp-integration.

Conclusion

The discovery of malicious code in the @zapier/mcp-integration package highlights the importance of regularly monitoring and updating open-source dependencies. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications.

See every vulnerability recorded for @zapier/mcp-integration →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications using the affected package.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The affected versions are 3.0.1 and 3.0.3.

Yes, it is advisable to update to the latest version of the package to ensure that any malicious code is removed.

As a temporary measure, you should uninstall the package to prevent any potential security risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @zapier/mcp-integration

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback