jest-test (npm): malicious package fully compromises machines that install it; no safe version exists
Severity: critical · Patch status: no-fix-needed · Since 2026-11-18
GitHub published a malware advisory (GHSA-4g5f-v2qx-j2qp, CWE-506 Embedded Malicious Code) for the npm package jest-test on 2026-11-18. Every published version (= 0) is malicious and there are no patched versions, so any installation grants an outside party full control of the machine. Any computer with the package installed or running must be considered fully compromised, with secrets and keys at risk of exfiltration. The package is low-volume (~458 downloads/month, 1 dependent repo) but the compromise is total for affected hosts. Removal of the package alone cannot be assumed to remove the malicious software. No fix exists; remediation is host-level incident response and credential rotation.
What to do
- Treat any machine with jest-test installed as fully compromised; isolate and forensically review it
- Rotate all secrets, keys, and credentials stored on or accessible from affected machines, from a clean computer
- Remove jest-test and rebuild affected systems from trusted images
- Audit dependency trees and CI pipelines for jest-test or typosquat variants and block the package
- Review logs and network traffic for signs of exfiltration or attacker access
Sources
All live incidents on Threat Watch