Malware in identitysecuretokenserv
Malware discovered in the npm package identitysecuretokenserv. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- identitysecuretokenserv
The npm package identitysecuretokenserv has been identified as containing malware. According to the GitHub Advisory (GHSA-2g7g-rqj2-26hv), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory warns that all secrets and keys stored on affected computers should 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 package installation, as the attacker may have gained full control of the system.\n\nUsers should treat any system that has run this package as potentially compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- identitysecuretokenserv
Remediation
- Immediately isolate any system with identitysecuretokenserv installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the identitysecuretokenserv package from all systems
- Conduct a full security audit and malware scan of affected systems
- Review system logs and access logs for signs of unauthorized activity
- Consider full system reimaging if compromise is confirmed
Sources
- GitHub Advisory GHSA-2g7g-rqj2-26hv · GitHub Advisory Database
Cite this entry
"Malware in identitysecuretokenserv." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 24, 2026; last updated August 24, 2026. https://supplychainattack.org/incident/malware-in-identitysecuretokenserv-n7alef
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in sm-session (npm)
The npm package sm-session (version 99.0.1) contains malicious preinstall and postinstall lifecycle scripts that beacon to a hardcoded IP address (16.192.173.5) over plain HTTP, exfiltrating installer host information. This is a dependency-confusion reconnaissance attack designed to identify which environments resolve the package name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in sm-apikey-model (npm)
The npm package sm-apikey-model versions 99.0.0 and 99.0.1 contain malicious preinstall and postinstall lifecycle scripts that exfiltrate installation telemetry to a hardcoded IP endpoint. The package exhibits characteristics of a dependency-confusion reconnaissance probe.
npmCompromised packageDependency confusion - containedcritical
Malicious code in message-compiler (npm)
The npm package message-compiler is a typosquat of @intlify/message-compiler containing malicious code that exfiltrates installer environment variables, public IP, and hostname via preinstall script execution.
npmTyposquattingCompromised package - activecritical
Malicious code in sm-billing-form (npm)
Malicious npm package sm-billing-form (versions 99.0.0 and 99.0.1) contains preinstall and postinstall lifecycle scripts that execute curl commands to a hardcoded IP address (16.192.173.5) over cleartext HTTP, exfiltrating install environment details. The high version number and behavior pattern indicate a dependency-confusion attack targeting internal packages of the same name.
npmCompromised packageDependency confusion