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
- resolvedcritical
Malicious code in epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - containedcritical
Malicious code in epic-common (npm)
The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - containedcritical
Malware in leb128x
The npm package leb128x was found to contain malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - containedcritical
Malicious code in checkout-desktop-total (npm)
The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.
npmCompromised package