@servicetitan/cp-react-hooksnpm

npm/@servicetitan/cp-react-hooks 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.

package.json declares preinstall: node setup.mjs, which fires automatically on npm install. setup.mjs is itself obfuscated (identifier names _0xNNNN, string-array rotation) and downloads the Bun runtime zip from the oven-sh/bun GitHub releases, extracts it, chmod+x's the bun binary in a temp directory, and invokes execFileSync(bunPath, [path.join(D, 'math_init.js')], {stdio:'inherit', cwd:D}). The file math_init.js is a 727KB single-line Bun-CJS module (header // @bun @bun-cjs) with a custom string-array + numeric-index decoder (WV8StW rotator over base64-like alphabet) and fully renamed identifiers. math_init.js is not listed in package.json's files array (which declares only dist and src), so it is an undeclared blob smuggled into the published tarball. Fetching a second language runtime specifically to execute an obfuscated, undeclared payload has no relationship to the package's advertised purpose (a React hooks library) and evades Node-based inspection. The package is published on the public npm registry under the @servicetitan/* scope, a namespace commonly used for that vendor's private packages, consistent with a dependency-confusion attempt against internal build systems that resolve the public registry ahead of an internal one.

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.