orion-overlord: Malicious npm package compromises hosts and exposes secrets
Severity: critical · Patch status: unpatched · Since 2026-11-20
The npm package orion-overlord is malicious, according to GitHub Advisory GHSA-rf8v-v97c-32r7. The advisory states that any computer with the package installed or running should be considered fully compromised, and that all secrets and keys stored on that computer should be rotated immediately from a different computer. The package has no patched versions and affects all versions (= 0). It has roughly 270 downloads per month. Removing the package is recommended, but because an outside entity may have gained full control of the host, removal alone may not eliminate all malicious software installed as a result. No specific attacker, campaign name, CVE, or in-the-wild exploitation details are provided.
What to do
- Treat any host that installed or ran orion-overlord as fully compromised; isolate it from networks and production credentials.
- From a different, trusted computer, immediately rotate all secrets, API keys, tokens, SSH keys, and credentials that were present or accessible on affected hosts.
- Remove the orion-overlord package and rebuild affected systems from trusted sources rather than relying on cleanup alone.
- Hunt for persistence, unauthorized access, and data exfiltration on affected hosts and related CI/CD or developer environments.
- Audit npm dependency trees and lockfiles for orion-overlord; block the package in registries and dependency policies.
- Review logs for package installation and any subsequent suspicious activity, and consider full reimaging of compromised machines.
Sources
All live incidents on Threat Watch