developmentstelemetry (npm): malicious package compromises any machine where installed (no CVE)
Severity: critical · Patch status: no-fix-needed · Since 2026-11-19
GitHub published a malware advisory (GHSA-v4vq-23qw-j3r8) for the npm package developmentstelemetry on 2026-11-19. Every version (= 0) is affected and no patched version exists; the package is classified as embedded malicious code (CWE-506). Any computer with the package installed or running should be considered fully compromised, with control potentially handed to an outside actor, so all secrets and keys on affected machines must be treated as stolen. Removal of the package does not guarantee removal of malicious software it may have installed. No exploitation details or victim counts are given, but any developer or CI environment that installed the package is at risk. There is no fix; remediation is removal plus credential rotation from a clean machine.
What to do
- Remove developmentstelemetry from all projects, lockfiles and CI pipelines
- Rotate all secrets, keys and credentials stored on or accessible from affected machines, from a clean computer
- Rebuild affected machines or containers from trusted images; audit for persistence
- Audit npm install logs and dependency trees for other suspicious or typosquatted packages
Sources
All live incidents on Threat Watch