Which versions of epic-consent-dialog are malicious?

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

How do I remediate epic-consent-dialog if I installed it?

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

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

Search your lockfiles and build artifacts for epic-consent-dialog (2 malicious versions).

Malicious package

epic-consent-dialognpm

Advisory published Oct 30, 2025Updated Sep 23, 2026

epic-consent-dialog is a confirmed malicious npm package (MAL-2025-49127) 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-consent-dialog (npm)

MAL-2025-49127

Immediate action

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

npm uninstall epic-consent-dialog

What this malware does

The package epic-consent-dialog was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

0ab01762eb52cfb3e852d9ab46d5f8216fb6ef716a47c97f247a4a99f68abaca

Detection & response playbook

Malicious package

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