@servicetitan/onboarding-uinpm

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

The tarball contains a preinstall hook (node setup.mjs) that, on npm install, downloads the Bun runtime v1.3.13 from GitHub, extracts it to a temporary directory, marks it executable, and invokes it against a sibling math_init.js shipped at the tarball root. math_init.js is a 727KB single-line, heavily obfuscated JavaScript file (obfuscator.io shape: numeric/string constant array, string-array rotator WV8StW, decoder hc1jfK9 over a shuffled alphabet; sha256 9fc2570b7cef51c1b8df116d144d11ff4096357be7d2c4c6367cfc2509cf1bcc). setup.mjs itself contains _0xNNNN obfuscator artifacts. Neither setup.mjs nor math_init.js is referenced by any file under dist/, and the declared purpose of the package is a React/MobX UI component library (design-system peers, forms, Pusher, contentful) — a UI library has no legitimate need to fetch a second language runtime at install time and execute an obfuscated blob under it. Executing the payload under Bun (rather than Node) also evades Node-oriented auditing. The runtime fetch is from an official Bun release URL, but the executed content is the shipped obfuscated blob, not Bun itself — the dropper is the fetch-and-exec of that opaque blob under a freshly-installed alternate runtime, triggered automatically by npm install.

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.