Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @servicetitan published 141 malicious packages. See the full campaign →
Malicious package

@servicetitan/assist-uinpm

@servicetitan/assist-ui is a confirmed malicious npm package (MAL-2026-11830) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.1, 2.1.2, 2.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/assist-ui (npm)

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

What this malware does

npm/@servicetitan/assist-ui 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.

@servicetitan/[email protected] is published as a React component library (main=./lib/index.js exporting ServiceTitan Atlas UI Components), but its package.json declares scripts.preinstall=node setup.mjs. setup.mjs downloads a Bun runtime binary from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/, extracts it to a temporary directory, chmods it 0o755, and invokes it via execFileSync against a bundled sibling file math_init.js. math_init.js is a 727KB single-line Bun-cjs bundle (header // @bun @bun-cjs) with obfuscator.io fingerprints: a rotating string/constant array named n7gIxM, an array-shuffle helper WV8StW using push/shift, and hex-named identifiers. Readable strings are reduced to opaque char-code arrays, hiding the payload's network destinations, filesystem targets, and credential-access logic from static inspection. The Bun runtime download and math_init.js execution are unrelated to the advertised React component library and are not referenced from the library entry point. Executing an obfuscated bundle via a freshly downloaded alternate runtime automatically on npm install is the alternate-runtime dropper pattern and runs regardless of whether a consumer ever imports the UI components. Consistent with a hijacked-publish or malicious release of the ServiceTitan scope.

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
2.1.12.1.22.1.32.1.42.1.52.1.62.1.7

Indicators of compromise (SHA-256)

b61a306abfeebe498d2e6ac61e40ff44bcc4dd33513dd04287ed397035619e1f
7f49a90ff50f5ed5570aa93f5fa55bae4bb1be9e98166b35872e36a84f6709f5
faa7178240d9ad99df9b0033eff78bd83090788949198aae6ad7333bf686ce32
919ffb84c51db7d867573573c0b30a1524a5ba39b65c0ac56a044671ae9eb631
8b6b2ba6527157cd921825533672194b27ef47f9b8dfbb9b5d7628d00f832e58
d160e3c5d81fca8c665f7a69bbb49bf0c7c3fd949cb2675d767cdd09f9a753aa
4eba5d9aaf977f5f02fc284661a734e98e55f98db5343a66ca996467dc4f5647
a398e47b88e95ce68f959e98884550d2d8a840ec00939d8d9c8fafe6f3278d27

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

  2. If you installed it — respond

    @servicetitan/assist-ui 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/assist-ui 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/assist-ui 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/assist-ui on npm has been identified as a malicious package (versions 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c7vw-mh2h-h6m7IN-MAL-2026-011468IN-MAL-2026-011407IN-MAL-2026-011995IN-MAL-2026-012161IN-MAL-2026-012236IN-MAL-2026-012777IN-MAL-2026-012818

References

Credits

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

Detect & block this

O3 blocks @servicetitan/assist-ui-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/assist-ui (npm) malicious package — MAL-2026-11830 | O3 Security