Critical Malicious Code Vulnerability in cp_amm Package
Summary
MAL-2026-74: Malicious code in cp_amm (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 cp_amm package is a Node.js library available through npm, designed for various functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their projects.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the cp_amm package. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected computer. The malicious nature of this code is classified under CWE-506, indicating that it is intentionally harmful. Users are advised to treat any system with this package installed as fully compromised, as removing the package may not eliminate all traces of the malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall cp_ammIf 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 cp_amm package and rotating any compromised secrets or keys.
Conclusion
The cp_amm package has been identified as containing malicious code that poses a severe security risk. Immediate action is required to remove the package and secure any compromised information. Regular monitoring of dependencies is crucial to prevent similar vulnerabilities in the future.
See every vulnerability recorded for cp_amm →
FAQ
Immediately uninstall the cp_amm package using 'npm uninstall cp_amm' and rotate any sensitive information stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
Leaving cp_amm installed can lead to unauthorized access to your system, data breaches, and potential exploitation by malicious actors.
While most npm packages are safe, it is essential to regularly audit and monitor your dependencies for vulnerabilities to maintain security.
