Malicious code in identitysecuretokenserv (npm)
The npm package identitysecuretokenserv version 10.0.0 was found to contain malicious code that communicates with domains associated with malicious activity and executes commands associated with malicious behavior. The package was identified as malicious by both Amazon Inspector and the OpenSSF Package Analysis project.
- Disclosed
- Last updated
- Blast radius
- All users of identitysecuretokenserv npm package version 10.0.0 and potentially other versions
- Ecosystems
- Attack vectors
- Affected entities
- identitysecuretokenserv · 10.0.0
The npm package identitysecuretokenserv was identified as containing malicious code by multiple security sources. Amazon Inspector and the OpenSSF Package Analysis project both flagged version 10.0.0 as malicious.\n\nAccording to the OpenSSF Package Analysis findings, the package exhibits two key malicious behaviors: it communicates with a domain associated with malicious activity, and it executes one or more commands associated with malicious behavior. This indicates active post-installation compromise capabilities.\n\nThe package was published on GitHub's advisory system (GHSA-rqm7-j2qp-74f2) and credited to the OpenSSF malicious packages database. The incident was disclosed on 2026-07-27.
Indicators of compromise
- Packages
- identitysecuretokenserv@10.0.0
Remediation
- Immediately remove identitysecuretokenserv from all projects and dependencies
- Audit all systems where identitysecuretokenserv version 10.0.0 was installed for signs of compromise
- Review network logs for connections to the malicious domain(s) identified by OpenSSF
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Check npm audit and dependency trees for any transitive dependencies on this package
- Monitor for any suspicious command execution or network activity on systems that installed this package
Sources
- GitHub Advisory GHSA-rqm7-j2qp-74f2 · GitHub Advisory Database
Cite this entry
"Malicious code in identitysecuretokenserv (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 28, 2026. https://supplychainattack.org/incident/malicious-code-in-identitysecuretokenserv-npm-xxx6lu
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 fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit