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

@servicetitan/marketing-global-routenpm

@servicetitan/marketing-global-route is a confirmed malicious npm package (MAL-2026-11893) that steals credentials and exfiltrates sensitive data (malicious versions 1.14.1, 1.14.2, 1.14.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/marketing-global-route (npm)

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

What this malware does

npm/@servicetitan/marketing-global-route 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] declares a preinstall hook (node setup.mjs) that, at npm install time, downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/ and uses it to execute a bundled 728 KB math_init.js payload. Both setup.mjs and math_init.js are heavily obfuscated: setup.mjs uses hex-named identifiers and per-function string-lookup objects to hide execFileSync/https.get/chmod calls, and math_init.js is a Bun-CJS bundle with a rotated numeric/string array whose runtime behavior is not statically readable. The package is advertised as a small route-config library (Marketing route package for global navigations); nothing about that purpose requires a second language runtime or the execution of an opaque obfuscated bundle at install time. Package.json also has empty author metadata and no repository or homepage fields despite publishing under the @servicetitan/ corporate scope, consistent with a scope-squat or account-takeover release rather than a genuine ServiceTitan library. Installing this version causes arbitrary attacker-controlled code to execute on the installer's machine via an alternate runtime chosen specifically to evade Node-based scanners.

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
1.14.11.14.21.14.31.14.41.14.51.14.61.14.7

Indicators of compromise (SHA-256)

11e068076226997a43907090d9a970a2cd30e2283d2740e4c9f2c74e8aa03d87
3454ff46c0154fcef73b4600befa72cdb5541c93f20d9aad9ff583e5e1bf2406
45dc505244e5ffbecb336b9006d5accfb5749bf94544f7d06dd5c5e5fa8c3275
bab14816ae663a3f7e3436a179bf3ced960490a642d930589cc0541f19b74105
1be2ea2e434e01599acc069e79fad622aa9a5ed7025cd72bb40d6331b1b50fed
9f33340bb76038f3b29e6f9d7adf6041a614fca64ad4fcb812e490fcaec1b739
ac932cc945cd0f98ceb931801d068c6beb72d7ef45819a63947502cf7e2c5eed
bb6c3ce3cb611bf04e27879aa40cc1b20de9d4887078780ffa5c0198f8baf257

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-global-route (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-global-route across your stack and pipelines.

  2. If you installed it — respond

    @servicetitan/marketing-global-route 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-global-route 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-global-route 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-global-route on npm has been identified as a malicious package (versions 1.14.1, 1.14.2, 1.14.3, 1.14.4, 1.14.5, 1.14.6, 1.14.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rf64-3f84-8frqIN-MAL-2026-012080IN-MAL-2026-012013IN-MAL-2026-012074IN-MAL-2026-012404IN-MAL-2026-012379IN-MAL-2026-012185IN-MAL-2026-012726

References

Credits

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

Detect & block this

O3 blocks @servicetitan/marketing-global-route-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