Malware in ozone-sdk
Malware was discovered in the npm package ozone-sdk, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with ozone-sdk installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ozone-sdk
A critical malware incident was identified in the npm package ozone-sdk. According to the GitHub Advisory (GHSA-3qc2-qc6w-c8xm), 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, given that the attacker may have gained full control of the system.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem.
Indicators of compromise
- Packages
- ozone-sdk
Remediation
- Remove the ozone-sdk 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 modifications
- Consider rebuilding affected systems from clean media if possible
- Audit any systems that may have been accessed using credentials stored on compromised machines
Sources
- GitHub Advisory GHSA-3qc2-qc6w-c8xm · GitHub Advisory Database
Cite this entry
"Malware in ozone-sdk." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 11, 2026; last updated June 11, 2026. https://supplychainattack.org/incident/malware-in-ozone-sdk-xxe2gb
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 polymarket-risk-manager
Malware was discovered in the npm package polymarket-risk-manager, potentially providing full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malicious code in toll_free (npm)
The npm package toll_free version 1.0.1 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malicious code in @finxsecdemo/utils (npm)
The npm package @finxsecdemo/utils version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.
npmCompromised package - containedcritical
Malware in poly-kelly
Malware was discovered in the npm package poly-kelly. The package grants full system compromise to attackers and should be considered a critical threat to any system where it is installed or running.
npmCompromised package