Malware in leo-sdk
Malware was discovered in the leo-sdk npm package. Systems with the package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with leo-sdk installed or running; full system compromise possible
- Ecosystems
- Attack vectors
- Affected entities
- leo-sdknpm package
A critical malware incident was identified in the leo-sdk npm package. According to the GitHub advisory (GHSA-m9cg-qm5p-9pvq), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain attack through package compromise in the npm ecosystem."
Indicators of compromise
- Packages
- leo-sdk
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the leo-sdk package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had leo-sdk installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Review and revoke any credentials or tokens that may have been exposed
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-m9cg-qm5p-9pvq · GitHub Advisory Database
Cite this entry
"Malware in leo-sdk." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-leo-sdk-7im1pu
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 chlklib
Malware was discovered in the npm package chlklib, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malware in alphazone
The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in chai-as-deployer
Malware was discovered in the npm package chai-as-deployer, 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 checkout-common-tokens
Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package