Which versions of epic-webpack-node-externals are malicious?

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

How do I remediate epic-webpack-node-externals if I installed it?

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

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

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

Malicious package

epic-webpack-node-externalsnpm

Advisory published Oct 30, 2025Updated Oct 1, 2026

epic-webpack-node-externals is a confirmed malicious npm package (MAL-2025-49221) 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-webpack-node-externals (npm)

MAL-2025-49221

Immediate action

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

npm uninstall epic-webpack-node-externals

What this malware does

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

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

102dc15d33d216994ec6848e16bbd6833cd72544b1d466826d43109f3405531e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for epic-webpack-node-externals (2 malicious versions).
If you installed it — respond
Remove epic-webpack-node-externals 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-webpack-node-externals 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-webpack-node-externals 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-webpack-node-externals-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