Which versions of eslint-validation-cli are malicious?

The following npm versions of eslint-validation-cli are flagged malicious: 2.12.1. Treat any of these as compromised.

How do I remediate eslint-validation-cli if I installed it?

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

If eslint-validation-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is eslint-validation-cli part of a known attack campaign?

Yes — eslint-validation-cli is associated with the RLMA-2025-04516, RLUA-2025-05789 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-validation-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-validation-cli (version 2.12.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-validation-cli across your stack and pipelines.

Malicious package

eslint-validation-clinpm

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

Malicious code in eslint-validation-cli (npm)

MAL-2025-41556

Immediate action

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

npm uninstall eslint-validation-cli

Malicious versions

1 flagged

2.12.1

Indicators of compromise (SHA-256)

a6064dd32c48af95dcb34d56c104bd64758385c9a6419708138ae57eec45a3c6

6191dc73b52cc740c420a0acaf0cef8cc35002d085d57aca5460c32b3cd7d79c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-validation-cli (version 2.12.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-validation-cli across your stack and pipelines.
If you installed it — respond
Remove eslint-validation-cli 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-validation-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks eslint-validation-cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. eslint-validation-cli on npm has been identified as a malicious package (version 2.12.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04516RLUA-2025-05789

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks eslint-validation-cli-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