Malicious code in npm-doc-dev (npm)
The npm-doc-dev package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removing the package alone does not guarantee removal of all malicious software or restoration of system integrity.
AI Analysis
Technical Summary
The npm-doc-dev package versions 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, and 1.1.1 contain malicious code that fully compromises the host computer. Installation or execution of this package can lead to complete system compromise, including potential unauthorized access to secrets and keys stored on the device. Due to the severity of the compromise, simply uninstalling the package may not remove all malicious components or backdoors introduced by the attacker.
Potential Impact
Any system with the affected versions of npm-doc-dev installed or running should be considered fully compromised. Attackers may have gained full control over the system, risking exposure or theft of sensitive data such as secrets and cryptographic keys. The integrity and confidentiality of the affected system cannot be assured without thorough remediation.
Mitigation Recommendations
Remove the malicious npm-doc-dev package immediately. Rotate all secrets and keys stored on the compromised system from a separate, trusted computer. Because full system compromise is likely, consider rebuilding the affected system from a known good backup or reinstalling the operating system to ensure complete removal of malicious software. No official patch or fix is indicated; remediation relies on removal and secret rotation.
Malicious code in npm-doc-dev (npm)
Description
The npm-doc-dev package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removing the package alone does not guarantee removal of all malicious software or restoration of system integrity.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The npm-doc-dev package versions 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, and 1.1.1 contain malicious code that fully compromises the host computer. Installation or execution of this package can lead to complete system compromise, including potential unauthorized access to secrets and keys stored on the device. Due to the severity of the compromise, simply uninstalling the package may not remove all malicious components or backdoors introduced by the attacker.
Potential Impact
Any system with the affected versions of npm-doc-dev installed or running should be considered fully compromised. Attackers may have gained full control over the system, risking exposure or theft of sensitive data such as secrets and cryptographic keys. The integrity and confidentiality of the affected system cannot be assured without thorough remediation.
Mitigation Recommendations
Remove the malicious npm-doc-dev package immediately. Rotate all secrets and keys stored on the compromised system from a separate, trusted computer. Because full system compromise is likely, consider rebuilding the affected system from a known good backup or reinstalling the operating system to ensure complete removal of malicious software. No official patch or fix is indicated; remediation relies on removal and secret rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6857
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-m89x-q3jv-q5q2"]
- Ecosystems
- ["npm"]
Threat ID: 6a4c343227e9c797195fa7f4
Added to database: 07/06/2026, 23:03:14 UTC
Last enriched: 09/12/2026, 20:31:47 UTC
Last updated: 09/13/2026, 00:54:34 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.