MAL-2026-11570

npm/@nebula.js/nucleus 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 MathSymbol.js / mathinit.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.

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (07892a043a429b9674f7321df91e410f10c5252980be77db5e3014d51eae0f61)

This version of @nebula.js/nucleus adds a preinstall hook (scripts.preinstall: node setup.mjs) that is not present in the legitimate qlik-oss/nebula.js upstream. setup.mjs downloads the Bun standalone runtime from the oven-sh/bun GitHub releases (URL built as https://github.com/oven-sh/bun/releases/download/bun-v<version>/<archive>.zip), extracts it to a temporary directory, marks it executable, and invokes it against a shipped sibling file math_init.js via execFileSync(bunPath, ['math_init.js'], { cwd: D }). math_init.js is a 727 KB, three-line file using obfuscator.io-style array-shift string decoding with hex-named identifiers (e.g. function WV8StW(...) {... MmgoCP.push(MmgoCP.shift())... }) — its contents are not readable without decoding. package.json reuses the legitimate publisher's identity (author: QlikTech International AB, repository: qlik-oss/nebula.js) as cover, but the preinstall hook, setup.mjs, and math_init.js do not exist in the upstream package. Installing the package on default npm install executes the obfuscated payload under a freshly downloaded alternate runtime before any consumer code runs, bypassing Node-based install-time scanners.

Source: ghsa-malware (6365391cddb7e9aa55a0219cda224e56a7cb171fa8a2584dacbc264a072428f2)

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.