What does the enclose-eslint malware do?

The package enclose-eslint was found to contain malicious code. The OpenSSF Package Analysis project identified 'enclose-eslint' @ 99.99.2 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of enclose-eslint are malicious?

The following npm versions of enclose-eslint are flagged malicious: 99.99.2. Treat any of these as compromised.

How do I remediate enclose-eslint if I installed it?

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

If enclose-eslint 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 enclose-eslint across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for enclose-eslint (version 99.99.2).

Malicious package

enclose-eslintnpm

Advisory published Dec 6, 2025Updated Dec 10, 2025

enclose-eslint is a confirmed malicious npm package (MAL-2025-192352) that executes malicious code on install (malicious version 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in enclose-eslint (npm)

MAL-2025-192352

Immediate action

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

npm uninstall enclose-eslint

What this malware does

The package enclose-eslint was found to contain malicious code.

The OpenSSF Package Analysis project identified 'enclose-eslint' @ 99.99.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.99.2

Indicators of compromise (SHA-256)

9e0be37b60a02ac1ede967e7e3db110f924fa0e3b578e286968a17cad31a3534

6f7fc1a375a04989c1b52036b89fefe7fbba475b3fe7ec9917335cfe3a9746bc

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks enclose-eslint-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