Which versions of estree-util are malicious?

The following npm versions of estree-util are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate estree-util if I installed it?

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

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

Yes — estree-util is associated with the RLMA-2025-06348 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 estree-util across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for estree-util (version 1.0.0).

Malicious package

estree-utilnpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

estree-util is a confirmed malicious npm package (MAL-2025-192796) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in estree-util (npm)

MAL-2025-192796

Immediate action

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

npm uninstall estree-util

What this malware does

The package estree-util was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

03760b28a4c01c13433452186dacc42ed6de3f48fadd4c9b0ca5b85b5cafaf04

137bbad3650384f516e11cd21a91087a3521948ed4f6c1952af26ebb739f5e54

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06348

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks estree-util-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