Critical Malicious Code Vulnerability in @jaswanthlanka/mcp-proxy Package
Summary
MAL-2025-6139: Malicious code in @jaswanthlanka/mcp-proxy (npm). Affected versions are not published. 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 @jaswanthlanka/mcp-proxy package is an npm library designed for proxying requests in Node.js applications. It is intended to facilitate the handling of HTTP requests and responses, providing developers with a streamlined way to manage data flow in their applications. However, this package has been identified to contain embedded malicious code, posing significant security risks to any system utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the @jaswanthlanka/mcp-proxy package. This code can compromise the security of any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that once installed, the package can fully control the affected system, making it imperative for users to take immediate action to mitigate the risks associated with this vulnerability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @jaswanthlanka/mcp-proxyIf 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
There are no effective workarounds for this vulnerability other than removing the package and ensuring that all sensitive data is secured. It is essential to monitor your system for any signs of unauthorized access following the removal of the package.
Conclusion
The @jaswanthlanka/mcp-proxy package contains embedded malicious code that poses a severe security risk to any system using it. Immediate removal of the package and rotation of sensitive information is essential to mitigate potential damage. Users are encouraged to monitor their systems and consider alternative solutions for proxying requests.
See every vulnerability recorded for @jaswanthlanka/mcp-proxy →
FAQ
You should immediately remove the package and rotate any sensitive information stored on your system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.
You may need to find an alternative package or implement your own proxy solution to replace the functionality provided by @jaswanthlanka/mcp-proxy.
