Malicious Code Detected in @mcp-use/cli Package - Security Alert
Summary
MAL-2025-190867: Malicious code in @mcp-use/cli (npm). Affects @mcp-use/cli versions 2.2.6. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @mcp-use/cli package is a command-line interface tool designed for various utility functions within the npm ecosystem. It is commonly used by developers to streamline their workflows. However, recent findings have revealed that this package is compromised, posing significant security risks to users who rely on it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @mcp-use/cli package, specifically version 2.2.6. This code can potentially lead to unauthorized access, data breaches, or other harmful actions on systems utilizing this package. The malicious code was identified by Amazon Inspector, highlighting the importance of vigilance when using third-party packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @mcp-use/cli
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 measure, you can remove the @mcp-use/cli package from your project until a secure version is confirmed. Use the following command to uninstall it: npm uninstall @mcp-use/cli.
Conclusion
The discovery of malicious code in the @mcp-use/cli package underscores the importance of maintaining security in software development. Users should take immediate action to update or remove the affected package to safeguard their applications.
See every vulnerability recorded for @mcp-use/cli →
FAQ
The @mcp-use/cli package is a command-line interface tool used in the npm ecosystem for various utility functions.
The malicious code was detected by Amazon Inspector, a security tool that scans for vulnerabilities in software packages.
The risks include unauthorized access to systems, potential data breaches, and other harmful actions that could compromise security.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If immediate updates are not possible, consider removing the package temporarily until a secure version is available.