Critical Malicious Code Vulnerability in npm-doc-build Package
Summary
MAL-2026-1360: Malicious code in npm-doc-build (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 npm-doc-build package is a tool used in the Node.js ecosystem for generating documentation from source code. It is designed to streamline the documentation process for developers, making it easier to maintain and share project documentation. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the npm-doc-build package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. Once installed, the package grants full control to an external entity, making it imperative for users to consider their systems fully compromised. The malicious nature of this code is classified under CWE-506, indicating that it contains embedded malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall npm-doc-buildIf 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 securing your system. It is essential to monitor your environment for any signs of compromise.
Conclusion
The npm-doc-build package has been identified as containing malicious code that compromises system security. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring and security practices are essential to prevent future vulnerabilities.
See every vulnerability recorded for npm-doc-build →
FAQ
You should immediately uninstall the npm-doc-build package and rotate any sensitive information stored on your system.
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.
Keeping this package installed poses significant risks, including unauthorized access to sensitive data and potential system compromise.
If your system has been compromised, it is advisable to perform a thorough security audit, remove the malicious package, and restore your system from a secure backup.
While removing the package is essential, it does not guarantee complete security. A full security assessment is recommended to ensure no other vulnerabilities exist.
