Malware in npmjs-doc-builder
The npm package npmjs-doc-builder was found to contain malware. Any computer with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with npmjs-doc-builder installed or running
- Ecosystems
- Attack vectors
- Affected entities
- npmjs-doc-buildernpm package containing malware
The npm package npmjs-doc-builder was identified as containing malware. According to the GitHub Advisory (GHSA-jhx4-8pjp-h27w), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. The package should be removed, though full removal of all malicious software cannot be guaranteed given the potential for complete system compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across all systems that installed or executed the affected package.
Indicators of compromise
- Packages
- npmjs-doc-builder
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the npmjs-doc-builder package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had this package installed or running
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is suspected
- Monitor for any indicators of compromise or persistence mechanisms left by the malware
Sources
- GitHub Advisory GHSA-jhx4-8pjp-h27w · GitHub Advisory Database
Cite this entry
"Malware in npmjs-doc-builder." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 16, 2026; last updated June 16, 2026. https://supplychainattack.org/incident/malware-in-npmjs-doc-builder-qjzdjh
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package