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
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package