Malicious Code Detected in @mcp-use/mcp-use Package - Security Alert
Summary
MAL-2025-190869: Malicious code in @mcp-use/mcp-use (npm). Affects @mcp-use/mcp-use versions 1.0.1. 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/mcp-use package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers to enhance their projects with reusable code components. However, this package has been flagged for containing malicious code, which poses a significant security risk to applications that depend on it.
Vulnerability Detail
The vulnerability originates from the package @mcp-use/mcp-use, which has been identified to contain malicious code. This malicious code can potentially compromise the integrity of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The specific version affected is 1.0.1, and it was detected by Amazon Inspector, highlighting the importance of regular security assessments for open-source dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @mcp-use/mcp-useIf 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, consider removing the @mcp-use/mcp-use package from your project until a secure version is released. You can do this by executing: npm uninstall @mcp-use/mcp-use. Additionally, review your package-lock.json file to monitor for any other vulnerable packages.
Conclusion
The @mcp-use/mcp-use package has been identified as containing malicious code, posing a significant risk to applications that utilize it. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Regular monitoring of dependencies is essential for maintaining application security.
See every vulnerability recorded for @mcp-use/mcp-use →
FAQ
The malicious code can perform unauthorized actions within applications, potentially leading to data theft or system compromise.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risk.
It is advisable to regularly check for vulnerabilities, ideally with every new release or update of your dependencies, to ensure ongoing security.
You can find more information about the package on its npm page or GitHub repository, where you can also check for updates and security advisories.
