🛡️ MAL-2026-11940 — titan-chatbot-client

Malicious code in @servicetitan/titan-chatbot-client (npm)

npm/@servicetitan/titan-chatbot-client 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

Package @servicetitan/titan-chatbot-client@2.1.7 declares scripts.preinstall = "node setup.mjs". setup.mjs is itself obfuscated (mangled _0xNNNN identifiers, string-lookup objects) and, on npm install, constructs the URL https://github.com/oven-sh/bun/releases/download/bun-v<ver>/<platform>.zip, downloads the Bun runtime as a ZIP to a temp directory, extracts and chmods it executable (mode 493 / 0o755), then execFileSyncs that freshly-downloaded alien runtime against the sibling file math_init.js. math_init.js is a 727680-byte, three-line // @bun @bun-cjs bundle whose contents are a rotated numeric string-array (function WV8StW) and a custom charset decoder (hc1jfK9) — opaque to a Node-only static/dynamic scanner. The filename math_init.js does not correspond to any advertised functionality (the package is described as a chat UI client). The combination — obfuscated preinstall loader, install-time fetch of a second JavaScript interpreter, and execution of an obfuscated 727KB payload through that non-Node runtime specifically to bypass Node-based inspection — matches the alternate-runtime dropper pattern. Fetching Bun from its official oven-sh GitHub release is not itself the concern; the concern is that Bun is being used solely to execute an unrelated obfuscated payload shipped in the tarball, on every installer's machine, automatically during npm install.

Source: ghsa-malware

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.