Malware in log-upgrade
The npm package log-upgrade contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- log-upgrade
The npm package log-upgrade was found to contain malware. According to the GitHub Security Advisory (GHSA-xf9v-w8wv-g9r4), any computer that has 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, 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\nUsers should treat any system that ran this package as potentially containing persistent malware and take appropriate incident response measures."
Indicators of compromise
- Packages
- log-upgrade
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the log-upgrade package from all affected systems
- Conduct a full security audit and malware scan of any system that had this package installed or running
- Consider the affected system(s) as potentially compromised and plan for full reimaging or replacement if critical infrastructure
- Review access logs and monitor for any unauthorized activity on systems that had this package installed
Sources
- GitHub Advisory GHSA-xf9v-w8wv-g9r4 · GitHub Advisory Database
Cite this entry
"Malware in log-upgrade." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-log-upgrade-1o38k2
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