Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in epic-common-node (npm)

The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
All users of the epic-common-node npm package
Ecosystems
Attack vectors
Affected entities
  • epic-common-nodenpm package

The npm package epic-common-node was discovered to contain malicious code. The malicious package was identified through Amazon Inspector scanning and reported by the OpenSSF malicious-packages project.\n\nThe vulnerability was assigned GitHub Security Advisory identifier GHSA-m36g-mhjr-ww2c and tracked in the OpenSSF malicious packages database as MAL-2025-49125. The discovery was published on August 17, 2026.\n\nAny system that installed or used the epic-common-node package may have been affected by the malicious code injection.

Indicators of compromise

Packages
  • epic-common-node

Remediation

  • Remove the epic-common-node package from all affected systems
  • Audit systems that previously installed epic-common-node for signs of compromise
  • Review package.json and lock files to identify all instances of epic-common-node usage
  • Replace epic-common-node with a legitimate alternative or verified safe version if available
  • Monitor for any suspicious activity on systems that may have executed code from this package

Sources

  1. GitHub Advisory GHSA-m36g-mhjr-ww2c · GitHub Advisory Database

Cite this entry

"Malicious code in epic-common-node (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-common-node-npm-1jmw1j

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. 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
  2. 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
  3. 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
  4. 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