Which versions of eslint-config-jest are malicious?

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

How do I remediate eslint-config-jest if I installed it?

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

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

Yes — eslint-config-jest is associated with the GHSA-8j7j-85r9-v8hh, RLMA-2025-05357, RLUA-2025-05782 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-config-jest across my projects, lockfiles, and CI pipelines?

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

Malicious package

eslint-config-jestnpm

Advisory published Oct 13, 2025Updated Dec 2, 2025

eslint-config-jest is a confirmed malicious npm package (MAL-2025-48323) 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-config-jest (npm)

MAL-2025-48323

Immediate action

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

npm uninstall eslint-config-jest

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a8136cf5c3645f0d663343578a6f6592474f35014323fd59a5cd067962473bb6

96500c612314ce8c4adbb103999f9b62f3851b6dd7f57f16a7a172f7b9e8dd2d

1ae7b03f0623a19faf2b9cd5ecfd33bf47fca0fdbb7e7be03c0e02314f783ce1

Detection & response playbook

Malicious package

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

GHSA-8j7j-85r9-v8hhRLMA-2025-05357RLUA-2025-05782

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks eslint-config-jest-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