Which versions of epic-common are malicious?

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

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

Remove epic-common 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 — how do I know if it already compromised me?

If epic-common 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 across my projects, lockfiles, and CI pipelines?

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

Malicious package

epic-commonnpm

Advisory published Oct 30, 2025Updated Aug 17, 2026

epic-common is a confirmed malicious npm package (MAL-2025-49124) 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 (npm)

MAL-2025-49124

Immediate action

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

npm uninstall epic-common

What this malware does

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

Malicious versions

1 flagged

0.0.1-security

Indicators of compromise (SHA-256)

d0d1ee5aef53675a9fb367bfbb6e08505b9584394391d2d0c3d6af4529dab29f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for epic-common (version 0.0.1-security).
If you installed it — respond
Remove epic-common 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 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 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-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