Malware in tslint-conf
The npm package tslint-conf was found to contain malware, potentially giving attackers full control of affected systems. Any computer with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- tslint-confnpm package containing malware
The npm package tslint-conf was identified as containing malware. According to the GitHub Advisory (GHSA-wchw-4whx-qhq5), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers 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 initial compromise.\n\nThis represents a critical supply chain attack through a malicious npm package that could grant attackers complete control over affected systems.
Indicators of compromise
- Packages
- tslint-conf
Remediation
- Immediately remove the tslint-conf package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Audit system logs for suspicious activity during the period the package was installed
- Consider the affected system(s) fully compromised and plan for complete rebuild if critical infrastructure
- Check for any other suspicious packages or modifications to the system
- Review npm package dependencies to ensure no other malicious packages are present
Sources
- GitHub Advisory GHSA-wchw-4whx-qhq5 · GitHub Advisory Database
Cite this entry
"Malware in tslint-conf." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 9, 2026; last updated July 9, 2026. https://supplychainattack.org/incident/malware-in-tslint-conf-1nesqf
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 myclaude-code
Malware was discovered in the npm package myclaude-code. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
npmCompromised package - resolvedcritical
Malware in clavue
The npm package clavue contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in airkey-mfa-react
Malware was discovered in the npm package airkey-mfa-react. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.
npmCompromised package - resolvedcritical
Malware in fusion-client
The npm package fusion-client contained malware that provided full system compromise to attackers. Any computer with the package installed should be considered fully compromised and all secrets and keys rotated from a different machine.
npmCompromised package