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

@servicetitan/standalone-uinpm

@servicetitan/standalone-ui is a confirmed malicious npm package (MAL-2026-11922) that steals credentials and exfiltrates sensitive data (malicious versions 2.2.4, 2.2.5, 2.2.6…). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

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

The package's npm preinstall hook runs node setup.mjs, which downloads the Bun standalone runtime from GitHub releases (https://github.com/oven-sh/bun/releases/download/bun-v<version>/...), unpacks it to a temporary directory, marks it executable, and then invokes it via execFileSync(bunPath, [path.join(D, 'math_init.js')],...) against a sibling file math_init.js. math_init.js is a 727KB single-line Bun-CJS bundle (header // @bun @bun-cjs) with a shuffled string-array decoder (function WV8StW(...) {...MmgoCP.push(MmgoCP.shift()); return MmgoCP }), hex-suffixed variable names, and no readable identifiers. Fetching an alternate language runtime at install time solely to execute an opaque, heavily obfuscated bundle is not the behavior of a React component library and matches the alternate-runtime dropper pattern — the Bun execution deliberately routes the payload outside Node's visibility. The manifest declares name: "@servicetitan/standalone-ui" under the public @servicetitan scope with an empty author field and a description referencing ServiceTitan's internal standalone-fe repo, consistent with a dependency-confusion package intended to be resolved in place of an internal ServiceTitan artifact. Installing this package causes attacker-controlled code to execute automatically on the installer's machine.

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.2.42.2.52.2.62.2.72.2.82.2.92.2.10

Indicators of compromise (SHA-256)

12df098840bfe644740eca50de8d113779156f4cbd707431aa8c76c7f926eaf3
02ced750bc8a9c749ea5ff0bdefa01132b02265d818763a3409b3f9af4f5f83c
c4f4c9bf3014f36fe4b2058359fd205e5723859cfc7ad768ad7040518df96982
ccf3dc5a74cce0009a4399d06bc051d86126832c621179cbaa8ae47afbf256f7
077f7a4cffb14777cf8c43d29c60b78a4d9047a988df3665f9393bb651b06bd2
0a5ba7af268a8c248d0cab7eb66dbc245c309b882ee2895b1afdbe7a632bdc12
95397301aa3d444487381c710650be7421d648e4318ce1b2108eb0218f06669c
c0ee3af2c6b86fd0b02badea0d9afbf623e190ded06b923ad443d60f061260a0

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

  2. If you installed it — respond

    @servicetitan/standalone-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/standalone-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/standalone-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/standalone-ui on npm has been identified as a malicious package (versions 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 2.2.9, 2.2.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-92gh-p3pf-6vm6IN-MAL-2026-011996IN-MAL-2026-012402IN-MAL-2026-012447IN-MAL-2026-012240IN-MAL-2026-012651IN-MAL-2026-012322IN-MAL-2026-012768

References

Credits

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

Detect & block this

O3 blocks @servicetitan/standalone-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