Malware in npm-doc-dev
The npm package npm-doc-dev contains malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets/keys rotated immediately from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with npm-doc-dev installed
- Ecosystems
- Attack vectors
- Affected entities
- npm-doc-devMalicious package on npm registry
The npm package npm-doc-dev has been identified as containing malware. According to the GitHub Advisory (GHSA-m89x-q3jv-q5q2), installation or execution of this package results in full system compromise.
The advisory recommends that any computer with npm-doc-dev installed should be considered fully compromised. All secrets and cryptographic keys stored on affected systems should be rotated immediately from a different, uncompromised computer.
While the package should be removed, the advisory notes that because full control of the computer may have been given to an outside entity, there is no guarantee that package removal will eliminate all malicious software that may have been installed as a result of the initial compromise.
Users should treat this as a critical incident requiring immediate remediation and comprehensive system review.
Indicators of compromise
- Packages
- npm-doc-dev
Remediation
- Immediately remove npm-doc-dev from all systems
- Rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Perform a comprehensive security audit of any system that had npm-doc-dev installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
- Audit npm dependencies in all projects to ensure npm-doc-dev is not present
Sources
- GitHub Advisory GHSA-m89x-q3jv-q5q2 · GitHub Advisory Database
Cite this entry
"Malware in npm-doc-dev." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-npm-doc-dev-i7bax4
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malware in ulebkit
The npm package ulebkit contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in sui-move-graphql
Malware was discovered in the npm package sui-move-graphql. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.
npmCompromised package - containedcritical
Malicious code in runtime-health (npm)
The npm package runtime-health version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - activecritical
Malware in @ai-vertical/ai-agent
Malware was discovered in the npm package @ai-vertical/ai-agent. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
npmAI agents & skillsCompromised package