MAL-2026-11932

npm/@servicetitan/testing-library 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.

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

## Source: amazon-inspector (495d3db2c96037ccaef45121389cec8bc738200fa2a88f659263fad1824c9f0b) The package declares `scripts.preinstall = "node setup.mjs"`, which runs automatically on `npm install`. `setup.mjs` (itself variable-name-obfuscated with identifiers such as `_0x488df8`) downloads a Bun runtime zip from `https://github.com/oven-sh/bun/releases/download/bun-v<version>/...zip`, extracts and chmod +x's the Bun binary into a temp directory, then invokes `execFileSync(bunBinary, ['math_init.js'])`. The executed `math_init.js` is a ~727 KB single-line file (sha256 9fc2570b7cef51c1b8df116d144d11ff4096357be7d2c4c6367cfc2509cf1bcc) built from a several-thousand-entry constant table `n7gIxM=[...]` decoded through a rotating string-array function `WV8StW` — heavy obfuscation designed to evade static review. The package's advertised purpose is a React testing helper library, and its `dist/` tree contains benign-looking testing helpers as cover; the entire malicious surface sits in the install hook and the sibling opaque payload, which have no relationship to the advertised functionality. Downloading an alternate JavaScript runtime at install time specifically to execute a shipped opaque blob under it is the alternate-runtime-dropper pattern used to bypass Node-based supply-chain scanners, and it grants arbitrary code execution on any machine that runs `npm install` for a project depending on this version.

## Source: ghsa-malware (83708c370d363e31c58321cf80227d080cd274b5ad7ebde4259af77c31305f3b) 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.