OpenSSF/OSV advisory MAL-2026-11926 confirms this npm version as malicious. npm/@servicetitan/startup-utils 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...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @servicetitan/startup-utils (npm)
Details
npm/@servicetitan/startup-utils 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 (fa3a8a51a64a18e1404f402cfd5da19ee8da7607dca9386818d4c5306319da65) package.json declares scripts.preinstall='node setup.mjs'. setup.mjs downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v<version>/<archive>.zip, extracts it, chmods the binary 0o755, and execFileSyncs it against sibling file math_init.js. math_init.js is a 727 KB single-line Bun-compiled CJS bundle marked '// @bun @bun-cjs' with hex-obfuscated identifiers (_0xNNNN-style) and a shuffled string-array rotator (WV8StW/n7gIxM), invoked only via the freshly downloaded Bun binary. The advertised library surface in dist/index.js exports only small helpers (get-version-mismatches, is-compatible) and never references math_init.js. Fetching an alternate language runtime at install to execute an obfuscated 727 KB payload that is unrelated to the declared utility API is the alternate-runtime dropper pattern: it executes attacker-controlled code on every installer's machine and evades Node-only scanners. The @servicetitan scope framing plus a bolted-on preinstall dropper is consistent with a scope hijack / malicious publish rather than a legitimate release.
## Source: ghsa-malware (8be9c32f7cbfef9ff98bb393ad203c87523eadb86dece38bd454d6e9b7e9f5df) 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.