Malicious code in epic-sso (npm)
The npm package epic-sso was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
- Disclosed
- Last updated
- Blast radius
- All users of the epic-sso npm package
- Ecosystems
- Attack vectors
- Affected entities
- epic-ssonpm package containing malicious code
The npm package epic-sso was identified as containing malicious code. The discovery was made by Amazon Inspector and reported through the OpenSSF malicious packages database (MAL-2025-49192).\n\nThe malicious package was published on npm and could affect any user who installed or used epic-sso. The package has been flagged in the official OpenSSF malicious packages repository.\n\nUsers should immediately remove the epic-sso package from their projects and audit their systems for any compromise.
Indicators of compromise
- Packages
- epic-sso
Remediation
- Remove the epic-sso package from all projects immediately
- Audit systems for any signs of compromise or malicious activity
- Review npm package.lock or yarn.lock files to identify all affected dependencies
- Consider rotating any credentials or secrets that may have been exposed
- Monitor for any suspicious activity in systems that had epic-sso installed
Sources
- GitHub Advisory GHSA-cwhw-mm6w-rcj2 · GitHub Advisory Database
Cite this entry
"Malicious code in epic-sso (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 17, 2026; last updated August 17, 2026. https://supplychainattack.org/incident/malicious-code-in-epic-sso-npm-vaq3xe
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 pump-segments-sdk (npm)
The npm package pump-segments-sdk contained malicious code in a postinstall hook that exfiltrated sensitive system and npm configuration data to an attacker-controlled server. The package collected hostname, environment variables, system information, npm auth tokens, and attempted to read password hashes.
npmCompromised package - containedcritical
Malicious code in ts-rand-sdk (npm)
The npm package ts-rand-sdk contained malicious code disguised as a product catalog loader. When the advertised getTransactions() API was called, hidden obfuscated JavaScript was decoded and executed with full Node.js capabilities, enabling arbitrary filesystem, process, and network access on affected systems.
npmCompromised package - resolvedcritical
Malicious code in lodsh-cli (npm)
lodsh-cli, a typosquat of lodash-cli on npm, contained malicious code in its postinstall script that executed arbitrary remote code and exfiltrated system information. The package downloaded a Windows executable and sent platform data to a hardcoded IP address.
npmTyposquattingCompromised package - containedcritical
Malicious code in lodahsjs (npm)
The npm package lodahsjs is a typosquatting attack on 'lodash' that contains malicious code in its postinstall script. Upon installation, it exfiltrates system information to a C2 server and downloads and executes a Windows binary, with capability to bridge WSL environments to compromise the host Windows system.
npmCompromised packageTyposquatting