@servicetitan/startup@38.1.4

npm/@servicetitan/startup 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 (c5729faed330128fc5be55e4b9cd0f165ec971886439efc8c175ea0103b19954) package.json declares `"preinstall": "node setup.mjs"`. setup.mjs is itself obfuscated (obfuscator.io-style hex-suffixed identifiers such as `_0x19328d`, per-function object-literal indirection of every string constant and function call) and, on `npm install`, downloads the Bun runtime from github.com/oven-sh/bun releases, extracts the `bun` binary to a temp directory, and invokes it against `math_init.js` (`execFileSync(bun, [path.join(D, 'math_init.js')], {stdio:'inherit'})`). math_init.js is a 727,680-byte heavily obfuscated bundle shipped at the tarball root; its header is `// @bun @bun-cjs` and its body is a large numeric/string constant array permuted by a rotate-shift decoder (`function WV8StW(...) {... MmgoCP.push(MmgoCP.shift());... }`), which is the obfuscator.io string-array pattern. math_init.js is not listed in package.json `files` (which enumerates `bin, dist, eslint, jest, patches, src, tsconfig`), so it ships outside the author's declared manifest, and the filename does not match the package's advertised Lerna/TypeScript/React CLI purpose. Bun is fetched specifically so the payload executes under an alternate runtime rather than Node, evading Node-based inspection. The combination — obfuscated preinstall wrapper, alternate-runtime fetch, undeclared obfuscated sibling bundle executed on every install — is install-time arbitrary code execution on the installer's host with attacker-controlled content that cannot be inspected from the tarball. ## Source: ghsa-malware (ca74b5aaefb9796cd90e6f89009a918bf78c8a9d83a24d11a6008308914cff51) 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.