Which versions of ts-eslint-jest are malicious?

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

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

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

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

Yes — ts-eslint-jest is associated with the IN-MAL-2026-009189, GHSA-r8h6-7hvm-3xcp 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 ts-eslint-jest 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 ts-eslint-jest (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-eslint-jest across your stack and pipelines.

Malicious package

ts-eslint-jestnpm

ts-eslint-jest is a confirmed malicious npm package (MAL-2026-10076) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-eslint-jest (npm)

MAL-2026-10076

Immediate action

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

npm uninstall ts-eslint-jest

What this malware does

The package [email protected] presents as a TypeScript/ESLint/Jest helper but ships lib/collect.js, which imports child_process and invokes execSync('bash...') at line 205 and execSync('zsh...') at line 221. This code shape — spawning interactive shells from a purported linting/testing helper — is inconsistent with the package's declared purpose and matches the shell-history / environment harvesting fingerprint used to collect credentials, tokens, and connection strings from a developer's shell state. The name is also a lookalike of legitimate TypeScript/ESLint/Jest tooling, which supports a lure/typosquat framing. Automated tracing of collect.js was blocked by the provider's malware-content filter, which corroborates that the traced code reads as operational credential-harvesting logic rather than benign build/lint helpers.

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)

8e1ffed26d2d64bf9076210504de22b87e27a065821dedbc708fb05f7c47db74

81ea1325df356dbcfeb455b0c18cb09dbb9cdac542fe91c7aafff35a0d63a025

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-eslint-jest (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-eslint-jest across your stack and pipelines.
If you installed it — respond
ts-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 ts-eslint-jest 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 ts-eslint-jest 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. ts-eslint-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

IN-MAL-2026-009189GHSA-r8h6-7hvm-3xcp

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ts-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