Malware in tsetnpmackage
Malware was distributed via the npm package tsetnpmackage, providing full system compromise to 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 the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- tsetnpmackage
The npm package tsetnpmackage contained malware that compromised any system where it was installed or executed. According to the GitHub advisory, computers with this package should be considered fully compromised.\n\nThe advisory recommends that all secrets and cryptographic keys stored on affected computers be rotated immediately from a different, uncompromised system. 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 the attacker may have gained full control of the system.\n\nUsers should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- tsetnpmackage
Remediation
- Immediately rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Remove the tsetnpmackage package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had this package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review and revoke any credentials or tokens that may have been exposed on compromised systems
Sources
- GitHub Advisory GHSA-2rj9-jmvj-4cr8 · GitHub Advisory Database
Cite this entry
"Malware in tsetnpmackage." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 30, 2026; last updated July 30, 2026. https://supplychainattack.org/incident/malware-in-tsetnpmackage-1vhrq1
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 spectral-wraith
Malware was discovered in the npm package spectral-wraith. 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 - activecritical
Malware in @spectraltest/loglevel
Malware discovered in the npm package @spectraltest/loglevel. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in wastu
The npm package wastu was found to contain malware that grants full system compromise to attackers. Any system with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malware in ag-grid-boost
Malware was discovered in the npm package ag-grid-boost. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package