Malware in ts-lint-builders-v2.1
The npm package ts-lint-builders-v2.1 contained malware that provided full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ts-lint-builders-v2.1 · 2.1
The npm package ts-lint-builders-v2.1 was found to contain malware. According to the GitHub Advisory (GHSA-vjgf-xg3j-g9c5), 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 computer. While the malicious 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, given that the attacker may have gained full control of the system.\n\nAffected users should treat any system that installed or ran this package as potentially containing persistent malware and take appropriate incident response measures.
Indicators of compromise
- Packages
- ts-lint-builders-v2.1
Remediation
- Immediately remove the ts-lint-builders-v2.1 package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Treat any computer that installed or ran this package as fully compromised
- Perform forensic analysis and malware scanning on affected systems
- Review system logs and access logs for any unauthorized activity during the period the package was installed
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-vjgf-xg3j-g9c5 · GitHub Advisory Database
Cite this entry
"Malware in ts-lint-builders-v2.1." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-ts-lint-builders-v2-1-spopug
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