Malware in normalize-plus
Malware was discovered in the npm package normalize-plus, 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.
- Disclosed
- Last updated
- Blast radius
- Any system with normalize-plus installed or running
- Ecosystems
- Attack vectors
- Affected entities
- normalize-plus
The npm package normalize-plus was found to contain malware. According to the GitHub Advisory (GHSA-fr34-v6cp-fc49), any computer that has this package installed or running should be considered fully compromised.
Affected users are advised to rotate all secrets and keys stored on compromised computers immediately from a different, unaffected 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.
The advisory was published on 2026-06-24 via GitHub's security advisory system.
Indicators of compromise
- Packages
- normalize-plus
Remediation
- Immediately rotate all secrets, API keys, and credentials stored on any system that had normalize-plus installed, using a different unaffected computer
- Remove the normalize-plus package from all systems
- Perform a full security audit and malware scan on any affected systems
- Consider the affected systems as potentially fully compromised and plan for complete reimaging if critical infrastructure
- Review access logs and audit trails for any unauthorized activity during the period the package was installed
Sources
- GitHub Advisory GHSA-fr34-v6cp-fc49 · GitHub Advisory Database
Cite this entry
"Malware in normalize-plus." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 24, 2026; last updated June 24, 2026. https://supplychainattack.org/incident/malware-in-normalize-plus-11ckw9
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, 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 - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. 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