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/microfront-utilsnpm

@servicetitan/microfront-utils is a confirmed malicious npm package (MAL-2026-11904) that steals credentials and exfiltrates sensitive data (malicious versions 1.4.1, 1.4.2, 1.4.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/microfront-utils (npm)

MAL-2026-11904
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/microfront-utils

What this malware does

npm/@servicetitan/microfront-utils 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 declares a preinstall hook (node setup.mjs) that unconditionally runs on npm install. setup.mjs downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v<V>.zip, extracts and chmods it executable, then invokes it via execFileSync against a sibling file math_init.js. math_init.js is a 727KB single-line @bun @bun-cjs bundle with string-array rotation obfuscation (a shift/push rotator function, a numeric string-array constant, and a mapped-alphabet decoder), unrelated to the React micro-frontend utilities the package advertises. The visible dist/ tree contains small, unremarkable React helper files that act as cover while the actual install-time behavior is the opaque Bun-executed payload. The package is published under the @servicetitan scope but repository.url points to github.com/servicetitan/playground.git, which is not a repository under ServiceTitan's public GitHub organization — scope impersonation of a known enterprise vendor. Installing this package fetches an alternate language runtime specifically to execute an obfuscated bundle that Node-based tooling cannot inspect, and it fires automatically on npm install.

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

Indicators of compromise (SHA-256)

5789846c3cb10d35f57109a76107dd83677afe34afecbc85b207d97904776359
38db6df0e47bf04bda2a2e61c482b48f43def598e5e486a2f53a184da1472ed6
7dc04a823fdf7d48acbc73256719355df04e8ba6b648c7cf81b88ec6bc9e2705
11e315c2ac1a68a78523739793851e90e69bd7c33583085fefabb39ec84b3597
412643ac2ac11ff70b5987a9c572ae5b8a2e2890d879e48b6c9b461a493ad90f
5c91e64622fa9d078adf9a52cf5efe0dc8aaf1a6496b886e6c695bcb03699eab
705094d070706e7932883f09bea04679b51edd508038c7e5961aee79becfc6ca
158982c41169391292e867cca103bb8f7376e2493a88c80b2100e4be57469f1f

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

  2. If you installed it — respond

    @servicetitan/microfront-utils 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/microfront-utils 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/microfront-utils 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/microfront-utils on npm has been identified as a malicious package (versions 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5cxq-vprc-w6wgIN-MAL-2026-011444IN-MAL-2026-011993IN-MAL-2026-012643IN-MAL-2026-012373IN-MAL-2026-012503IN-MAL-2026-012720IN-MAL-2026-012810

References

Credits

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

Detect & block this

O3 blocks @servicetitan/microfront-utils-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/microfront-utils (npm) malicious package — MAL-2026-11904 | O3 Security