Malware in ts-eslint-jest
Malware discovered in the npm package ts-eslint-jest. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ts-eslint-jest
The npm package ts-eslint-jest has been identified as containing malware. According to the GitHub advisory, any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer. The package should be removed, though full removal of all malicious software cannot be guaranteed due to the potential for complete system compromise.\n\nThe advisory was published on 2026-07-10 via GitHub's security advisory system.
Indicators of compromise
- Packages
- ts-eslint-jest
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the ts-eslint-jest package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Review system logs for any unauthorized access or activity
- Consider full system reimaging if complete compromise is suspected
Sources
- GitHub Advisory GHSA-r8h6-7hvm-3xcp · GitHub Advisory Database
Cite this entry
"Malware in ts-eslint-jest." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-ts-eslint-jest-1y8sw5
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