Which versions of epic-node-blog are malicious?

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

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

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

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

Search your lockfiles and build artifacts for epic-node-blog (2 malicious versions).

Malicious package

epic-node-blognpm

Advisory published Oct 30, 2025Updated Sep 24, 2026

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

Malicious code in epic-node-blog (npm)

MAL-2025-49166

Immediate action

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

npm uninstall epic-node-blog

What this malware does

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

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

4207720525d69e9c09afb392295f1566d480abc128a98065be73bb7044e93291

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for epic-node-blog (2 malicious versions).
If you installed it — respond
Remove epic-node-blog 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-node-blog 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-node-blog on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0 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-node-blog-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