@servicetitan/startup-mfe-compat@0.5.3

npm/@servicetitan/startup-mfe-compat 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 (a990da55989112ca7c07ed86336a1a22e0697e29ba32f601e8f754143109e93f) package.json declares scripts.preinstall = `node setup.mjs`. setup.mjs is obfuscated (obfuscator.io-style _0x identifiers with per-function string dictionaries) and, on `npm install`, downloads a Bun runtime archive from oven-sh's GitHub releases, extracts the `bun` binary to a temp directory, chmods it 0o755, and then invokes execFileSync on the sibling file math_init.js under that Bun runtime. math_init.js is a ~727KB single-line obfuscated blob (obfuscator.io string-array/array-rotate dispatcher, `// @bun @bun-cjs` header, numeric/string dictionaries) that is not referenced by the package's declared main (dist/index.js) or bin entry — it is reachable only from the preinstall dropper. The advertised functionality (micro-frontend compatibility helpers using log/chalk/semver) is unrelated to both the setup.mjs runtime download and the math_init.js payload. Fetching a second language runtime and executing an opaque bundled payload under it at lifecycle time is an evasion pattern against Node-only inspection and produces arbitrary code execution on the installer's machine at `npm install` time. Shape is consistent with a compromised or hijacked release under the @servicetitan scope. ## Source: ghsa-malware (b94dcab498205478369e38a8ee799239bc901c83359ce09661ee8e0098a538d4) 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.