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

@servicetitan/design-systemnpm

@servicetitan/design-system is a confirmed malicious npm package (MAL-2026-11852) that steals credentials and exfiltrates sensitive data (malicious versions 14.5.4, 14.5.5, 14.5.6…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/design-system (npm)

MAL-2026-11852
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/design-system

What this malware does

npm/@servicetitan/design-system 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 preinstall hook runs node setup.mjs, an obfuscated loader (obfuscator.io-style _0xNNNN identifiers with string-lookup indirection) that platform-detects, downloads the Bun runtime zip from https://github.com/oven-sh/bun/releases/download/bun-v<version>/<platform>.zip, extracts the bun binary to a temp directory, marks it executable, and invokes it against a sibling file math_init.js. math_init.js is a 727 KB heavily obfuscated JavaScript blob (// @bun @bun-cjs header, rotated string array n7gIxM, rotating decoder WV8StW) whose contents cannot be read statically. Neither setup.mjs nor math_init.js is listed in the manifest's files whitelist (["dist", "readme.md"]) — they ship as undeclared root-level tarball blobs and execute on npm install with the developer's privileges. The package presents itself as @servicetitan/design-system, a React UI component library whose declared homepage is https://v1.anvil.servicetitan.com; a UI component library has no need to fetch an alternate JavaScript runtime and execute a 700+ KB opaque payload under it. The combination — obfuscated loader, alt-runtime fetch used to evade Node-based scanners, obfuscated payload smuggled outside the declared file list, and name impersonation of a legitimate scoped ServiceTitan package — is characteristic of a malicious republish that runs attacker-controlled code on the installer's host at install time.

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
14.5.414.5.514.5.614.5.714.5.814.5.914.5.10

Indicators of compromise (SHA-256)

e74ee06b998ea34ae2e79c8bcc54fc05c2cf0405d431fae63d7536725d1e22ee
65b9973b1f7ebcfdf05932780b0a74ab2e0c5a7d5518335e8b9fa23eb3a023ac
379e609dcf970aac092c37cb1a26d23edcdfae935fb9500e91d97384d4c0cd0d
80c2193bdab5d1574395ab3691fb97c482c0b59e2767dad1b603a40af6774ebe
969bf19d5c05db8120e572b9769072adb0d00b11ae4027d4742dca178fb5910f

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

  2. If you installed it — respond

    @servicetitan/design-system 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/design-system 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/design-system 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/design-system on npm has been identified as a malicious package (versions 14.5.4, 14.5.5, 14.5.6, 14.5.7, 14.5.8, 14.5.9, 14.5.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cjgc-69g5-x5qvIN-MAL-2026-011410IN-MAL-2026-011989IN-MAL-2026-011521IN-MAL-2026-011992

References

Credits

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

Detect & block this

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