Malware in ts-escro
The npm package ts-escro was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with ts-escro installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ts-escronpm package containing malware
The npm package ts-escro was identified as containing malware. According to the GitHub Advisory (GHSA-5hm9-jj3m-6q76), 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 computer. While the package should be removed, there is no guarantee that removing the package will remove 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 compromised npm package with potential for complete system takeover.
Indicators of compromise
- Packages
- ts-escro
Remediation
- Immediately remove the ts-escro package from all systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Conduct a full security audit of any system that had ts-escro installed
- Review system logs for suspicious activity during the period the package was installed
- Consider the affected system(s) potentially fully compromised and plan for complete rebuild if critical infrastructure
- Monitor for any unauthorized access or data exfiltration
Sources
- GitHub Advisory GHSA-5hm9-jj3m-6q76 · GitHub Advisory Database
Cite this entry
"Malware in ts-escro." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malware-in-ts-escro-nbhbs6
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