Which versions of eslint-jest are malicious?

The following npm versions of eslint-jest are flagged malicious: 4.0.4, 4.0.5, 4.0.6. Treat any of these as compromised.

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

eslint-jest is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed eslint-jest — how do I know if it already compromised me?

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

Yes — eslint-jest is associated with the GHSA-m3v6-5prj-x7rp, IN-MAL-2026-009691, IN-MAL-2026-009693, IN-MAL-2026-009692 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-jest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eslint-jest (3 malicious versions).

Malicious package

eslint-jestnpm

Advisory published Jul 10, 2026Updated Jul 10, 2026

eslint-jest is a confirmed malicious npm package (MAL-2026-10142) that steals credentials and exfiltrates sensitive data (malicious versions 4.0.4, 4.0.5, 4.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-jest (npm)

MAL-2026-10142

Immediate action

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

npm uninstall eslint-jest

What this malware does

The package presents itself as an ESLint-inside-Jest runner but the documented linkProject/lintFiles/createJestRunner API is not implemented. The actual exports are harvest-and-upload primitives. lib/collect.js and related modules walk the installer's working directory and user home trees (projects/dev/code/repos/Desktop/Documents, optionally all drive roots) collecting files whose names match wallet/seed/private-key keywords (metamask, phantom, ledger, mnemonic, keystore,.env,.pem,.p12, etc.). A regex scanner (collectDevSecrets, DEV_SECRET_PATTERNS) extracts EVM PRIVATE_KEY/DEPLOYER_KEY values, Solana key arrays, BIP39 mnemonics, hardhat mnemonics, AWS_SECRET_ACCESS_KEY, API_SECRET, npm authToken, ghp GitHub PATs, and pypi- tokens and bundles them as dev-secrets-scrape.txt. gatherShellHistory reads.bash_history,.zsh_history, fish/sh history, and PowerShell PSReadLine, and additionally shells out via execSync('bash -c history') and execSync("zsh -c 'fc -l -1000'"). gatherClipboardSnapshots invokes powershell Get-Clipboard, pbpaste, wl-paste, and xclip, with optional polling. All collected artifacts are multipart-POSTed to https://trabalhos-flax.vercel.app/api/v1. Auxiliary code base64-decodes string constants (including 8.8.8.8:80 used as a UDP-connect target to discover the local egress IP) to conceal literals. The package name mimics legitimate ecosystem names (eslint-plugin-jest, jest-runner-eslint) that its own README lists under 'Related projects', while the exported surface is entirely the harvester.

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

3 flagged

4.0.44.0.54.0.6

Indicators of compromise (SHA-256)

8131394ae9c99a6353e0b06148add947773e8a65aa2f635020bf2c43028c6b7b

c910c4c43a8c1d7cd945b6f00b8693f707dcebe00f5d5dbcd20bd4e2ffe666af

10ff068c9897c001dd426bf796cb29f676766d30f58fbceaad21e2a7d7a96804

8908ac72050dded53e2e163c528a446b7a4fd7a37a4874e14f95b08265f043c4

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for eslint-jest (3 malicious versions).
If you installed it — respond
eslint-jest is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If eslint-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-jest on npm has been identified as a malicious package (versions 4.0.4, 4.0.5, 4.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m3v6-5prj-x7rpIN-MAL-2026-009691IN-MAL-2026-009693IN-MAL-2026-009692

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eslint-jest-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database