Malware in webpack-cache-cycle
Malware discovered in the npm package webpack-cache-cycle. Any system 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
- webpack-cache-cycle
The npm package webpack-cache-cycle has been identified as containing malware. According to the GitHub Advisory (GHSA-2p34-5qgm-wr3f), 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 package installation, as the attacker may have gained full control of the system.\n\nThis is a critical supply chain incident affecting the npm ecosystem.
Indicators of compromise
- Packages
- webpack-cache-cycle
Remediation
- Immediately isolate any system that has webpack-cache-cycle installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the webpack-cache-cycle package from all affected systems
- Perform a full security audit and malware scan on all affected systems
- Review system logs and access logs for signs of unauthorized activity during the period the package was installed
- Consider the affected systems as potentially fully compromised and plan for complete reimaging if critical systems are affected
Sources
- GitHub Advisory GHSA-2p34-5qgm-wr3f · GitHub Advisory Database
Cite this entry
"Malware in webpack-cache-cycle." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 15, 2026; last updated July 15, 2026. https://supplychainattack.org/incident/malware-in-webpack-cache-cycle-qjv1wy
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