Malicious npm package 'unjailed' — full system compromise; no safe version exists
Severity: critical · Patch status: no-fix-needed · Since 2026-11-02
GitHub's malware advisory database (GHSA-89v8-j949-j3h5) flags the npm package 'unjailed' as containing embedded malicious code (CWE-506). All versions (= 0) are affected and no patched version exists. Any machine with the package installed or running must be considered fully compromised, with control potentially handed to an outside entity — enabling secret and key theft and persistence beyond simple package removal. The package sees roughly 8,000 downloads per month, so developer machines and CI environments that pulled it are at risk. Removal of the package alone is not guaranteed to remove all malicious software it installed. There is no fix; remediation is incident response, not upgrading.
What to do
- Rotate all secrets, keys, and credentials stored on any machine where unjailed was installed, using a clean machine
- Rebuild affected machines and CI runners from trusted images rather than just uninstalling the package
- Audit systems and logs for signs of compromise and persistence mechanisms
- Check dependency trees and lockfiles for unjailed and block it in package registries/proxies
Sources
All live incidents on Threat Watch
