MAL-2026-11811 Malicious code in @servicetitan/acquisition-functions (npm)

npm/@servicetitan/acquisition-functions 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.

This package's declared preinstall script (node setup.mjs) auto-executes on npm install. setup.mjs is itself obfuscated with hex-mangled identifiers and wrapper-call indirection (e.g., import _0x488df8 from "fs", YCZJE: function(fn,a,b,c){return fn(a,b,c)}) and performs the following sequence: download the Bun runtime from github.com/oven-sh/bun/releases/download/bun-v1.3.13/<platform>.zip into a temp directory, extract it, chmod it executable, then invoke that freshly downloaded Bun binary via execFileSync to run the sibling file math_init.js. math_init.js is a 727KB single-line // @bun @bun-cjs bundle whose entire body is string-array-rotation obfuscation (rotator function WV8StW cycling a large constants array, hex-mangled globals, no readable strings). The payload is executable only through the fetched alternate runtime and cannot be reviewed statically. This is the alternate-runtime dropper pattern: a Node lifecycle hook fetches a second language runtime specifically to execute an opaque, obfuscated, package-controlled payload with it, bypassing Node-based supply-chain scanners. The @servicetitan scope is a well-known company scope, and this shape is inconsistent with a legitimate ServiceTitan library — consistent with a scope compromise or lookalike publish. Installing this package grants arbitrary code execution on the installer's host at npm install time.

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.