a-sub-watcher (npm): malicious package compromises any machine where it is installed; no safe version exists
Severity: critical · Patch status: no-fix-needed · Since 2026-11-18
GitHub's advisory database published a malware advisory (GHSA-m5wx-ph7h-3vhf) for the npm package a-sub-watcher on 2026-11-18. Every published version (= 0) is classified as embedded malicious code (CWE-506), with no patched version available. GitHub's guidance states that any computer with the package installed or running should be considered fully compromised, implying the malware grants outside actors full control of the host. All secrets and keys stored on affected machines are at risk and must be rotated from a clean computer. Removal of the package alone is not guaranteed to eliminate the malicious software. Any developer, CI system, or end user that installed a-sub-watcher is affected; there is no safe version to upgrade to.
What to do
- Treat any machine with a-sub-watcher installed or running as fully compromised; isolate it
- Rotate all secrets, keys, tokens and credentials stored on or accessible from affected machines, from a clean computer
- Remove the package and rebuild/reimage affected systems, as removal may not eliminate all malicious software
- Audit dependency trees, lockfiles and CI caches for a-sub-watcher and block/reject the package
- Review logs and network traffic for signs of exfiltration or attacker access following installation
Sources
All live incidents on Threat Watch