Which versions of escaux are malicious?

The following npm versions of escaux are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate escaux if I installed it?

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

If escaux 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 escaux part of a known attack campaign?

Yes — escaux is associated with the RLMA-2026-01294 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 escaux across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for escaux (version 999.0.0).

Malicious package

escauxnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

escaux is a confirmed malicious npm package (MAL-2026-1728) that executes malicious code on install (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in escaux (npm)

MAL-2026-1728

Immediate action

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

npm uninstall escaux

What this malware does

The package escaux was found to contain malicious code.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

df19c668b3bca8f742ba2ce05bac0d284ea3086972e6f979f9581d601a7fdaaf

91d446ba76e486ebe4a395fe7329ff3b48c1c6b1a7974c083c2438f6764308c2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for escaux (version 999.0.0).
If you installed it — respond
Remove escaux 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 escaux 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. escaux on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01294

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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