Malware in leo-logger
Malware was discovered in the npm package leo-logger, resulting in full system compromise for any installation. The package should be removed and all secrets and keys rotated from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with leo-logger installed or running
- Ecosystems
- Attack vectors
- Affected entities
- leo-logger
The npm package leo-logger was found to contain malware. According to the GitHub Advisory (GHSA-5ggh-qwv4-wpwg), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. 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.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem.
Indicators of compromise
- Packages
- leo-logger
Remediation
- Remove the leo-logger package immediately from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Assume full system compromise and conduct forensic analysis
- Review system logs for unauthorized access or activity
- Consider rebuilding affected systems from clean media if possible
- Monitor for any signs of persistent malware or backdoors
Sources
- GitHub Advisory GHSA-5ggh-qwv4-wpwg · GitHub Advisory Database
Cite this entry
"Malware in leo-logger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-leo-logger-omnnxb
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in gx-npm-ui
Malware was discovered in the npm package gx-npm-ui, 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 - containedcritical
Malware in @vpms/design-system
Malware was discovered in the npm package @vpms/design-system. 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 - activecritical
Malware in unsafe-malicious-package
Malware discovered in the npm package unsafe-malicious-package. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in ts-ankle
The npm package ts-ankle 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.
npmCompromised package