@servicetitan/cp-uinpm

npm/@servicetitan/cp-ui 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'. setup.mjs is identifier-obfuscated (obfuscator.io-style _0xXXXX names with wrapper-object string/call indirection) and, on npm install, downloads the Bun runtime from github.com/oven-sh/bun/releases/download/bun-v1.3.13/<platform>.zip, extracts and chmods the binary, then execFileSyncs it against a shipped 727KB single-line file math_init.js. math_init.js carries a '// @bun @bun-cjs' header, a large numeric constant array, and a string-array rotation decoder (function shifting/pushing an array of hex constants) — an opaque compiled Bun bundle. The package advertises itself as a React UI component library, which has no purpose-aligned reason to fetch a second language runtime or execute a compiled Bun bundle at install time. The combination — obfuscated preinstall script fetching an alternate runtime and using it to run an obfuscated in-tree payload automatically on npm install — is an install-time arbitrary-code-execution vector on the installer host, and the alien-runtime execution path bypasses Node/npm-focused scanners.

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.