Which versions of epic-file-upload are malicious?

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

How do I remediate epic-file-upload if I installed it?

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

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

Search your lockfiles and build artifacts for epic-file-upload (2 malicious versions).

Malicious package

epic-file-uploadnpm

Advisory published Oct 30, 2025Updated Sep 24, 2026

epic-file-upload is a confirmed malicious npm package (MAL-2025-49144) 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-file-upload (npm)

MAL-2025-49144

Immediate action

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

npm uninstall epic-file-upload

What this malware does

The package epic-file-upload was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

8135524c3ac42c291081baced929d7455a0b2150d4d7ec96b1f5351ccd5d8b1e

Detection & response playbook

Malicious package

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