Which versions of epxreso are malicious?

The following npm versions of epxreso are flagged malicious: 5.1.3, 5.2.0, 5.2.1, 5.2.2, 5.2.3, 5.3.0, 5.3.1, 5.3.2, 5.3.3, 5.3.4. Treat any of these as compromised.

How do I remediate epxreso if I installed it?

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

If epxreso 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.

Is epxreso part of a known attack campaign?

Yes — epxreso is associated with the RLMA-2025-04995, RLUA-2025-05779 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find epxreso across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for epxreso (10 malicious versions).

Malicious package

epxresonpm

Advisory published Sep 5, 2025Updated Dec 2, 2025

epxreso is a confirmed malicious npm package (MAL-2025-44144) that executes malicious code on install (malicious versions 5.1.3, 5.2.0, 5.2.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in epxreso (npm)

MAL-2025-44144

Immediate action

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

npm uninstall epxreso

What this malware does

The package epxreso was found to contain malicious code.

Malicious versions

10 flagged

5.1.35.2.05.2.15.2.25.2.35.3.05.3.15.3.25.3.35.3.4

Indicators of compromise (SHA-256)

f73768599aae2c1e665e21dc93cb2ab56e4b8c72d30589f26dde5a766e18351d

7b29c879b9d5dc2e5a9516c760e066edc23bfd72fcb35759e17b347f22e85359

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for epxreso (10 malicious versions).
If you installed it — respond
Remove epxreso 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 epxreso 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. epxreso on npm has been identified as a malicious package (versions 5.1.3, 5.2.0, 5.2.1, 5.2.2, 5.2.3, 5.3.0, 5.3.1, 5.3.2, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04995RLUA-2025-05779

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks epxreso-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