Malware in eslint-jest
Malware discovered in the eslint-jest npm package. Systems with this package installed or running should be considered fully compromised. All secrets and keys must be rotated from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with eslint-jest installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- eslint-jestnpm package
The eslint-jest npm package has been identified as containing malware. According to the GitHub Advisory (GHSA-m3v6-5prj-x7rp), 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 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 compromise.\n\nThis represents a critical supply chain attack affecting the npm ecosystem, with potential for widespread impact given the package's likely use in development environments.
Indicators of compromise
- Packages
- eslint-jest
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the eslint-jest package from all affected systems
- Audit system logs for unauthorized access or activity during the period the package was installed
- Scan affected systems for additional malware or persistence mechanisms
- Review and revoke any credentials or tokens that may have been exposed
- Consider full system reimaging if compromise is suspected
Sources
- GitHub Advisory GHSA-m3v6-5prj-x7rp · GitHub Advisory Database
Cite this entry
"Malware in eslint-jest." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-eslint-jest-181tf1
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