Malware in leo-auth
The npm package leo-auth was found to contain malware. Any system with the package installed or running should be considered fully compromised. All secrets and keys must be rotated from a different computer, and the package should be removed.
- Disclosed
- Last updated
- Blast radius
- Any system with leo-auth installed or running
- Ecosystems
- Attack vectors
- Affected entities
- leo-authnpm package containing malware
The npm package leo-auth was identified as containing malware. According to the GitHub advisory (GHSA-x8r4-xjr9-2hhm), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the outside entity may have gained full control of the system.\n\nUsers should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- leo-auth
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the leo-auth package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had leo-auth installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if complete compromise is suspected
- Notify any services or systems that may have been accessed using credentials stored on compromised machines
Sources
- GitHub Advisory GHSA-x8r4-xjr9-2hhm · GitHub Advisory Database
Cite this entry
"Malware in leo-auth." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-leo-auth-1grove
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package