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/marketing-uinpm

@servicetitan/marketing-ui is a confirmed malicious npm package (MAL-2026-11896) that steals credentials and exfiltrates sensitive data (malicious versions 9.3.1, 9.3.2, 9.3.3…). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

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

Version 9.3.2 of @servicetitan/marketing-ui ships an obfuscated preinstall pipeline that fires automatically on npm install. package.json declares "preinstall": "node setup.mjs". setup.mjs is obfuscated with hex-mangled identifiers (e.g. _0x488df8, _0x52943e) and indirection wrapper dictionaries (_0x19328d.YCZJE(...)) that hide plain calls to network and process APIs. At install time it downloads the Bun runtime binary from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/<platform>.zip, chmods it executable, and invokes it via execFileSync(bun, ['math_init.js'], {cwd: D}) to run a sibling file. math_init.js is a 720KB Bun-compiled bundle whose header is // @bun @bun-cjs, followed by string-array rotation (WV8StW) over a large mixed dictionary and a 78-character-alphabet decoder (hc1jfK9), preventing inspection of its behavior. The package's declared purpose is a React marketing UI component library, which does not require a second language runtime or an opaque compiled payload at install time. Executing this preinstall hook runs attacker-chosen code on the installer's machine outside Node's normal resolution, evading scanners that only inspect Node-resolved code.

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

Indicators of compromise (SHA-256)

9e795fb850864da5a2da34a8e7d4af4c26921c0b68e30e5691c536de607c9a6a
afe4ba573686dfb4761acc9bfc70c0f236fd447dbe809ca5159e94aa6ecb7d64
2cf43b7f6b3640e5aa36f24acb898ef5d17b6d7c191189611673e9d8b8b40d21
cb2429dd06a414cd54a2b7e820c68a4d69a876f56585cc2e13745d7968df06b5
d90d1c4a5cc7695985cac93e3964e4339e42c3e87629128ace7af6a0c2a362a5
0fbfa177f603d4e1d19b6868756fbff81abb5e2e66b9b56a592a320acf04dd23
61344e9e33e5af8e35508dd2ec2fde3349f2d87e2ac08fcd59e5be914a0000d8
86036746469bae99806623f4a715d9f082c5bf65fe8ae7bd9c54155a484e6715

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

  2. If you installed it — respond

    @servicetitan/marketing-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/marketing-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/marketing-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/marketing-ui on npm has been identified as a malicious package (versions 9.3.1, 9.3.2, 9.3.3, 9.3.4, 9.3.5, 9.3.6, 9.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m8vp-9mgm-6m6hIN-MAL-2026-011437IN-MAL-2026-012482IN-MAL-2026-012704IN-MAL-2026-012665IN-MAL-2026-012229IN-MAL-2026-012826IN-MAL-2026-012767

References

Credits

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

Detect & block this

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