Malware in ts-enum-helper
Malware was discovered in the npm package ts-enum-helper. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a separate computer.
- Disclosed
- Last updated
- Blast radius
- Any system with ts-enum-helper installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- ts-enum-helpernpm package
A critical malware incident was identified in the npm package ts-enum-helper. According to the GitHub Advisory (GHSA-7q63-6v9w-j7mf), any computer with 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, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a supply chain compromise of the npm ecosystem affecting all users of ts-enum-helper.
Indicators of compromise
- Packages
- ts-enum-helper
Remediation
- Immediately rotate all secrets, API keys, and credentials from a separate, uncompromised computer
- Remove the ts-enum-helper package from all affected systems
- Perform a full security audit and malware scan of any computer that had ts-enum-helper installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-7q63-6v9w-j7mf · GitHub Advisory Database
Cite this entry
"Malware in ts-enum-helper." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malware-in-ts-enum-helper-s1ggzq
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 chlklib
Malware was discovered in the npm package chlklib, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malware in alphazone
The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in chai-as-deployer
Malware was discovered in the npm package chai-as-deployer, 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 - containedcritical
Malware in checkout-common-tokens
Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package