Malware in epic-internal-tools
Malware was discovered in the npm package epic-internal-tools. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- epic-internal-tools
The npm package epic-internal-tools was found to contain malware. According to the GitHub Advisory (GHSA-wx8q-h5p5-9hcf), any computer with this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers must 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, given that the outside entity may have gained full control of the system.\n\nThis is a critical supply chain incident affecting the npm ecosystem.
Indicators of compromise
- Packages
- epic-internal-tools
Remediation
- Immediately rotate all secrets and keys stored on computers that had epic-internal-tools installed, using a different uncompromised computer
- Remove the epic-internal-tools package from all affected systems
- Conduct a full forensic analysis of any system that had the package installed to identify additional malicious software
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-wx8q-h5p5-9hcf · GitHub Advisory Database
Cite this entry
"Malware in epic-internal-tools." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-epic-internal-tools-0s3gf5
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 fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit