Which versions of eslint-lodash are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for eslint-lodash (version 1.0.0).

Malicious package

eslint-lodashnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

eslint-lodash is a confirmed malicious npm package (MAL-2025-191574) 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 eslint-lodash (npm)

MAL-2025-191574

Immediate action

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

npm uninstall eslint-lodash

What this malware does

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8a09cef0c7a982586647093724392b592cd51286bdeaf0f8547c170ee9e4f116

64e5339ebcf037bec59b58b4622230d6f22619a009685877e469b566e883248a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for eslint-lodash (version 1.0.0).
If you installed it — respond
Remove eslint-lodash 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 eslint-lodash 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. eslint-lodash 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-05785

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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