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

@servicetitan/titan-chat-ui-commonnpm

@servicetitan/titan-chat-ui-common is a confirmed malicious npm package (MAL-2026-11937) 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-chat-ui-common (npm)

MAL-2026-11937
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/titan-chat-ui-common

What this malware does

npm/@servicetitan/titan-chat-ui-common 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 package declares a preinstall hook (node setup.mjs) that downloads the Bun runtime from github.com/oven-sh/bun releases (v1.3.13), extracts it to a temporary directory, marks it executable, and then invokes it against a bundled sibling file math_init.js. math_init.js is a ~727KB file with obfuscator.io fingerprints — string-array rotation (a helper performing .push(.shift()) on a mixed-type constant table) and a per-string decoder built from a shuffled alphabet — with no plausible relation to the package's advertised chat-UI purpose. The setup script itself uses obfuscated identifiers (_0x488df8, etc.) to hide the dropper flow. Running the payload under Bun rather than Node bypasses Node-based supply-chain scanners, and the entire chain fires automatically on npm install before consumers can inspect the code. The package is published under the @servicetitan scope and its dist/ tree references servicetitan/titan-chatbot-client PRs, while the preinstall dropper and math_init.js appear grafted onto that otherwise-legitimate UI code — consistent with a scope-hijack or dependency-confusion upload rather than a first-party release.

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)

c9d8397be66009b373d58a4adacfd8e906ae0451652c5582effea4738d0c1d69
a0232e887c8649545cddbdee1473fe3b2a537040dbaf8e958fb05ba764ce3f04
bf1085385ad7a39fe8e839598406d7d64c0a90b3dd273852e091a3176688d00e
f0ddff96b0113e79107fb35980ad3f6f14ae8fdbb4608ee4d83e7a70fe2b7d29
ad74029cad7641d09eeeb6e2c4f9a66945b1ba4dc19c3a56cc695d22e704fe02
e7fd1192635d254b2d15d7555e49317f4216a6f55e36aa03f0c7a2140eaae035
26b5af54d62f38c76f2aa354f39d8107c81ecddc2a7f6742e3ecdecd0b23bfa4
63b353bae2efbdda020c8ae919aecbb260c2bec8f13229299a02e0bd8129565f

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-chat-ui-common (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-chat-ui-common across your stack and pipelines.

  2. If you installed it — respond

    @servicetitan/titan-chat-ui-common 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-chat-ui-common 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-chat-ui-common 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-chat-ui-common 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-j5gf-8wxx-crfvIN-MAL-2026-011447IN-MAL-2026-011461IN-MAL-2026-012085IN-MAL-2026-012632IN-MAL-2026-012486IN-MAL-2026-012842IN-MAL-2026-012793

References

Credits

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

Detect & block this

O3 blocks @servicetitan/titan-chat-ui-common-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-chat-ui-common (npm) malicious package — MAL-2026-11937 | O3 Security