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.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- unsafe-malicious-package
The npm package unsafe-malicious-package has been identified as containing malware. According to the GitHub Advisory (GHSA-4gj3-wx83-w2hr), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory warns that all secrets and keys stored on affected computers should be rotated immediately 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 package's execution, as the attacker may have gained full control of the system.\n\nUsers should treat any system that has run this package as potentially compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- unsafe-malicious-package
Remediation
- Immediately remove the unsafe-malicious-package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Assume full system compromise and perform forensic analysis
- Consider rebuilding affected systems from clean media
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Monitor for any lateral movement or persistence mechanisms installed by the malware
Sources
- GitHub Advisory GHSA-4gj3-wx83-w2hr · GitHub Advisory Database
Cite this entry
"Malware in unsafe-malicious-package." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-unsafe-malicious-package-1k86yr
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 - 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 - resolvedcritical
Malware in velocityfix
The npm package velocityfix contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package