Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

epic-asset-uploadernpm

Malicious code in epic-asset-uploader (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-594
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall epic-asset-uploader

What this malware does

The package epic-asset-uploader was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'epic-asset-uploader' @ 99.9.9 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
99.9.9

Indicators of compromise (SHA-256)

6ef8b10f898d33d494e7397a91986f81d45041adc1e334aa81624e9260d0568e
cc2cb990940a69aa54175e17a56f993e9c380e4eb2bbe8fc9f6e86c09b252464
b1c5552ca01cf67d1055ce7ea7cd0a17e37d3a47e212b8ca7e4eb566fc020d6f

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for epic-asset-uploader (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging epic-asset-uploader across your stack and pipelines.

  2. If you installed it — respond

    Remove epic-asset-uploader 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.

  3. Did it already run?

    If epic-asset-uploader was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks epic-asset-uploader before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. epic-asset-uploader on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ph6h-g4vx-mhcw

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks epic-asset-uploader-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.

epic-asset-uploader (npm) malicious package — MAL-2026-594 | O3 Security