MAL-2026-11859

Dashboard / Malicious Package / MAL-2026-11859

MAL-2026-11859

Summary: Malicious code in @servicetitan/error-boundary (npm)

Details: npm/@servicetitan/error-boundary 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 (51aa927e92fea11d8b478668352f358469b291fbb789fe883aef86b6861e24e3) The package declares scripts.preinstall = "node setup.mjs". setup.mjs is itself obfuscated (obfuscator.io-style hex identifiers such as _0x488df8/_0x52943e/_0x548d91 for fs/https/zlib, per-function property dictionaries containing strings like "ldd", "--version", "/etc/os-release", "Alpine", "musl", "bun-linux-x64-musl-baseline", "unzip", "powershell"). It constructs a URL of the form https://github.com/oven-sh/bun/releases/download/bun-v<version>/... and downloads the Bun runtime, then execFileSyncs that runtime against a bundled sibling file math_init.js with stdio inherited. math_init.js is a 727KB single-line bundle carrying obfuscator.io fingerprints (`// @bun @bun-cjs` header, shuffled numeric/string dictionary array, hex-named globals MmgoCP/etDiOOB/JqTtnbZ, and a rotation function WV8StW). The advertised purpose of the package is a React error boundary, which has no legitimate need to fetch an alternate JavaScript runtime and execute an unrelated obfuscated bundle at install time. Fetching a runtime from its official project domain to run the package's OWN shipped code would be aggressive-but-legitimate; here the code being executed is an obfuscated payload whose filename (math_init.js) is unrelated to the package's function, delivered via an alien runtime specifically so Node-level tooling does not observe what runs. This fires automatically on npm install and executes with the installer's user privileges. Source: ghsa-malware (8cee7f3883ab4f2b2d7344b038f2a1e00b98461ce8d06eed561854f795fe7037) 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.

References: https://socket.dev/blog/popular-npm-packages-in-the-keyv-and-cacheable-namespaces-compromised-in-active-supply-chain, https://www.aikido.dev/blog/keyv-and-friends-compromised-in-npm-supply-chain-attack, https://safedep.io/keyv-npm-supply-chain-compromise/, https://www.npmjs.com/package/@servicetitan/error-boundary, https://github.com/advisories/GHSA-39x7-jmcp-g9x8, https://www.npmjs.com/package/@servicetitan/error-boundary/v/38.1.7, https://www.npmjs.com/package/@servicetitan/error-boundary/v/38.1.4, https://www.npmjs.com/package/@servicetitan/error-boundary/v/38.1.6, https://www.npmjs.com/package/@servicetitan/error-boundary/v/38.1.1, https://www.npmjs.com/package/@servicetitan/error-boundary/v/38.1.2, https://www.npmjs.com/package/@servicetitan/error-boundary/v/38.1.5, https://www.npmjs.com/package/@servicetitan/error-boundary/v/38.1.3