Which versions of epic-common-node are malicious?

The following npm versions of epic-common-node are flagged malicious: 0.0.1-security. Treat any of these as compromised.

How do I remediate epic-common-node if I installed it?

Remove epic-common-node from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed epic-common-node — how do I know if it already compromised me?

If epic-common-node was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find epic-common-node across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for epic-common-node (version 0.0.1-security).

Malicious package

epic-common-nodenpm

Advisory published Oct 30, 2025Updated Aug 17, 2026

epic-common-node is a confirmed malicious npm package (MAL-2025-49125) that executes malicious code on install (malicious version 0.0.1-security). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in epic-common-node (npm)

MAL-2025-49125

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall epic-common-node

What this malware does

The package epic-common-node was found to contain malicious code.

Malicious versions

1 flagged

0.0.1-security

Indicators of compromise (SHA-256)

b8e76e853a5ddeb0b5baed9270a0858d1df0976691cfd336b223e8208c241371

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for epic-common-node (version 0.0.1-security).
If you installed it — respond
Remove epic-common-node from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If epic-common-node was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. epic-common-node on npm has been identified as a malicious package (version 0.0.1-security flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks epic-common-node-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database