⌘ + K

MAL-2026-11747

Dashboard / Malicious Package / MAL-2026-11747

MAL-2026-11747

Published: 4 Aug 2026Last Modified: 5 Aug 2026Aliases:

Summary: Malicious code in @ornikar/eslint-config-babel-use (npm)

Details: npm/@ornikar/eslint-config-babel-use is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 (the "Shai-Hulud: Here We Go Again" wave) — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed version(s) were trojanized and republished by the worm after it reached an npm publish token belonging to a maintainer in this namespace; the payload enumerates every package a stolen token controls and republishes each with the same hook, so many packages under this scope were poisoned in the same short window. Every poisoned release adds a preinstall hook (`"preinstall": "node setup.mjs"`) that runs on a bare `npm install`, before any project code. setup.mjs downloads a standalone Bun runtime and runs a byte-identical, heavily obfuscated ~728 KB second-stage credential stealer (shipped as Math_Symbol.js / math_init.js). It harvests GitHub, npm, AWS, GCP, Azure, HashiCorp Vault and Kubernetes credentials plus generic secrets and private keys (TruffleHog-style sweep), reads CI/CD secrets and identifies build runners, then republishes further packages the stolen token can reach. Rather than a fixed command-and-control host, it exfiltrates stolen findings to attacker-created GitHub repositories (descriptions reading "Shai-Hulud: Here We Go Again") and over DNS. Treat any environment that installed an affected version (with install scripts enabled) as compromised: rotate and revoke all reachable credentials (npm and GitHub tokens, cloud keys, Vault/Kubernetes secrets, and CI org/repo secrets). Part of the August 2026 npm worm that poisoned 400+ packages across many organizations. Source: amazon-inspector (175aef1f5216b69ae7495d6258a974f2626510b07a4e2bb44d0afe8e3cdf5649) The package declares a `preinstall` hook `node setup.mjs`. `setup.mjs` downloads the Bun runtime binary from `https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/` for the installer's platform/arch, extracts it to a temp directory, marks it executable, and invokes it against a bundled ~727KB file `math_init.js`. `math_init.js` is a heavily obfuscated bundle (obfuscator.io-style rotated string-array decoder, numeric opcode tables, hex-mangled identifiers, `// @bun @bun-cjs` header) whose contents cannot be inspected without executing the loader. The package's declared purpose is an eslint configuration; `index.js` contains a plain eslint config export consistent with prior legitimate versions, and the CHANGELOG stops at 13.2.0 with no mention of a native runtime, Bun, or `math_init.js`. An eslint-config has no legitimate need for a second language runtime, an obfuscated payload, or a preinstall script. The dropper runs automatically on `npm install` with the installer's privileges, and executing the payload under a freshly downloaded Bun binary evades Node-based inspection. The shape is consistent with a hijacked or namespace-takeover republish of a previously legitimate package. Source: ghsa-malware (83c5e09bbe6fd5f1d53bbb370e7f2624e7153aa8e81996ce1994eb3e9b138625) 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.

Affected packages

Package

Name: @ornikar/eslint-config-babel-use

Purl: pkg:npm/%40ornikar/eslint-config-babel-use

Affected ranges

Type: N/A

Events:

Introduced- None

Fixed -None

Affected versions

13.2.1

13.2.2

13.2.3

13.2.4

13.2.5

13.2.6

13.2.7

13.2.8

13.2.9

13.2.10

13.2.11

13.2.12