Malware in ts-eslinter
Malware was discovered in the ts-eslinter npm package. Systems with the package installed or running should be considered fully compromised. All secrets and keys must be rotated from a different computer, and the package should be removed.
- Disclosed
- Last updated
- Blast radius
- Any system with ts-eslinter installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- ts-eslinternpm package
A critical malware incident was identified in the ts-eslinter npm package. According to the GitHub advisory (GHSA-h269-vrf6-9f75), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should 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 compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system compromise and credential theft.
Indicators of compromise
- Packages
- ts-eslinter
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the ts-eslinter package from all affected systems
- Audit system logs for unauthorized access or activity during the period the package was installed
- Consider the affected computer(s) as potentially fully compromised and plan for forensic analysis or complete system rebuild
- Check for any other suspicious packages or modifications on affected systems
- Notify any services that may have had credentials stored on the affected computer
Sources
- GitHub Advisory GHSA-h269-vrf6-9f75 · GitHub Advisory Database
Cite this entry
"Malware in ts-eslinter." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-ts-eslinter-1fsqr2
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 svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package