# MAL-2026-10076: Malicious code in ts-eslint-jest (npm)


- **Type:** Malicious package
- **Package:** `ts-eslint-jest` (npm)
- **Published:** 9 Jul 2026
- **Also known as:** GHSA-r8h6-7hvm-3xcp

## What is MAL-2026-10076?

MAL-2026-10076 is a malicious package in ts-eslint-jest, published on 9 Jul 2026. 

### Official description

The package ts-eslint-jest@1.0.0 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.

## What should I do about MAL-2026-10076?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10076 is a malicious package: ts-eslint-jest (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10076/ (Markdown: https://insights.sbomify.com/MAL-2026-10076/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10076

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10076/
Summaries are generated and may contain mistakes; the official description above is the record.