Malware in leo-cli
The npm package leo-cli was compromised and distributed with malware. Systems with the package installed or executed should be considered fully compromised and require complete remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with leo-cli installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- leo-clinpm package containing malware
The npm package leo-cli was found to contain malware. According to the GitHub Advisory (GHSA-hmx8-mh72-wj54), any computer that has installed or run this package 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 compromise.\n\nThis represents a critical supply chain attack through package distribution, affecting all users who installed or executed leo-cli from the npm registry.
Indicators of compromise
- Packages
- leo-cli
Remediation
- Immediately isolate any computer that has installed or run leo-cli from the network
- Rotate all secrets, API keys, credentials, and authentication tokens from a different, uncompromised computer
- Remove the leo-cli package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the compromise is suspected to be extensive
- Monitor for any unauthorized access to accounts or services that may have been compromised
Sources
- GitHub Advisory GHSA-hmx8-mh72-wj54 · GitHub Advisory Database
Cite this entry
"Malware in leo-cli." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-leo-cli-6jr3jc
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