⌘ + K

MAL-2026-11754

Dashboard / Malicious Package / MAL-2026-11754

MAL-2026-11754

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

Summary: Malicious code in @ornikar/eslint-plugin-neverthrow (npm)

Details: npm/@ornikar/eslint-plugin-neverthrow 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 (fa9a7028d5d013a020a2596e3a6cefa7f347e3a2adf181f140dabe7476a8b01f) The package's declared purpose is an ESLint rule for the neverthrow library, but the tarball wires a preinstall hook (`node setup.mjs`) that downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/ into a temp directory, chmods it executable, and invokes it against a shipped 727 KB single-line obfuscated CJS bundle `math_init.js` (header `// @bun @bun-cjs`, packed string/number array with a shuffled dispatcher). If `bun` is already on PATH it is used directly. Both `setup.mjs` and `math_init.js` are heavily obfuscated (obfuscator.io-style identifier mangling `_0x488df8`, per-call string-property dictionaries, rotator functions), preventing static inspection of the payload's behavior. An ESLint plugin has no legitimate need for an alternate language runtime or a large opaque install-time payload; the delivery mechanism itself — fetching a second runtime at install to execute a shipped obfuscated blob under it — evades Node-based static analysis and executes attacker-controlled code on the installer's machine as a side effect of `npm install`. The `@ornikar` scope publication with a legitimate-looking `main: dist/src/index.js` alongside the unrelated dropper is consistent with a scope hijack or malicious release under an established name. Source: ghsa-malware (624410b3684b3319c5f06cac04538a03eb59617c3d15b2dc37dd2285114a461a) 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-plugin-neverthrow

Purl: pkg:npm/%40ornikar/eslint-plugin-neverthrow

Affected ranges

Type: N/A

Events:

Introduced- None

Fixed -None

Affected versions

1.3.1

1.3.2

1.3.3

1.3.4

1.3.5

1.3.6

1.3.7

1.3.8

1.3.9

1.3.10

1.3.11

1.3.12