Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@servicetitan/titan-chatbot-apinpm

@servicetitan/titan-chatbot-api is a confirmed malicious npm package (MAL-2026-11939) that steals credentials and exfiltrates sensitive data (malicious versions 9.0.1, 9.0.2, 9.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-11939
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/titan-chatbot-api

What this malware does

npm/@servicetitan/titan-chatbot-api 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 published tarball contains two files not present in the src/ tree: setup.mjs and math_init.js. package.json declares "preinstall": "node setup.mjs", so on every npm install the dropper runs automatically. setup.mjs (itself obfuscated with _0xNNNN identifiers) downloads a Bun runtime archive from github.com/oven-sh/bun releases (version 1.3.13), extracts the bun binary to a temp directory, chmod +x's it, and invokes it against the sibling file math_init.js in the package directory. math_init.js is a 727KB obfuscated blob consisting of a rotated string array plus an alphabet-substitution decoder (hc1jfK9) with hex-named globals; no source form exists in src/. Executing the payload with an alien runtime (Bun rather than Node) evades Node-based static analysis and instrumentation. The package's declared purpose is a ServiceTitan chatbot API client, which has no legitimate need for a second language runtime or an opaque native payload at install time. Combined static and dynamic analysis of native-client.js also shows POST calls and a ping primitive at line 1243. The presence-in-tarball / absence-in-source pattern for both dropper files is consistent with a compromised publish injecting attack files outside the normal build pipeline.

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.

Malicious versions

7 flagged
9.0.19.0.29.0.39.0.49.0.59.0.69.0.7

Indicators of compromise (SHA-256)

25410adfd400df441f76dc298a82a281dac3ac6bf24964ed37ec9d635267a032
d49fc8b6453f655393e53ba3e584ef2ff9209d695cc65b2260ad8f85db362a21
7537f7717081da6816dbcdd06af4811c33d59feb840351733d78f2ca72d927ad
a7ebf6d345e953995ad537d87b12b741fd9a6167b5a4a20d5ae3c0e736b85d1a
477b3fb72c38f0c42bfe196b949de1029a99a0286785758926eb9c4be962df4b
1ea891d87027fd142a0f708c0d9ba24473953975dfb89a7ac28f46995b290c82
5b273dabb4639948e6796dcf1858709b769dc4433ba84bf5f23eb9003fb00ba7
f0f8040e34fcd05b801b2cf9fb84c63cbd18eac03b02da052dbe6fe715b09feb

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @servicetitan/titan-chatbot-api (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @servicetitan/titan-chatbot-api across your stack and pipelines.

  2. If you installed it — respond

    @servicetitan/titan-chatbot-api is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @servicetitan/titan-chatbot-api was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @servicetitan/titan-chatbot-api before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @servicetitan/titan-chatbot-api on npm has been identified as a malicious package (versions 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gmqr-c5jv-7qx5IN-MAL-2026-011449IN-MAL-2026-012044IN-MAL-2026-011975IN-MAL-2026-012047IN-MAL-2026-012560IN-MAL-2026-012254IN-MAL-2026-012705

References

Credits

  • Aikido Security · finder
  • Amazon Inspector · finder
  • SafeDep · finder
  • Socket Threat Research Team · finder

Detect & block this

O3 blocks @servicetitan/titan-chatbot-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@servicetitan/titan-chatbot-api (npm) malicious package — MAL-2026-11939 | O3 Security