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

@servicetitan/cp-mfe-devnpm

@servicetitan/cp-mfe-dev is a confirmed malicious npm package (MAL-2026-11845) that steals credentials and exfiltrates sensitive data (malicious versions 1.115.1, 1.115.2, 1.115.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/cp-mfe-dev (npm)

MAL-2026-11845
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/cp-mfe-dev

What this malware does

npm/@servicetitan/cp-mfe-dev 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 script that runs setup.mjs, which downloads the Bun runtime (bun-v1.3.13) from GitHub releases, unzips it into a temporary directory, marks it executable, and invokes it via execFileSync(bunBinary, [math_init.js]) against a sibling file shipped in the tarball. math_init.js is a 728KB // @bun @bun-cjs blob whose contents are a shuffled multi-thousand-entry string/opcode array permuted at runtime by a rotation function (WV8StW) — heavy dictionary/opcode obfuscation that is only meaningful when executed by the downloaded Bun binary and is opaque to Node-based inspection. Handing an obfuscated blob to a second language runtime at install time is the alternate-runtime dropper pattern; the package's advertised purpose (a ServiceTitan MFE dev helper library) has no functional need for a second runtime. The package name @servicetitan/cp-mfe-dev mimics ServiceTitan's private npm scope and its peerDependencies list additional @servicetitan/* packages, making the artifact usable as a dependency-confusion lure targeting organizations with an internal ServiceTitan scope. The shipped dist/ files are a thin SDK-shaped stub that serves as cover for the install-time dropper.

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

Indicators of compromise (SHA-256)

24492173684850c8fb0cdab1e5aaa1e383971d6b3e58ffb423863a4ab9471fc4
143687b509b1152fb895293fb4e76c5be6dc24c7c462d0ea40f596103ffed0be
35d2faafa1bc862453e4fd0327e2bf7b4a25834b786d8bc8c2b5568e280b1598
3745a6f32fa2aa2965f8cd60bf533fdd4b7c22f38a990be7395f99fcdb3dd212
4393c7ff478e0c12ed3434a4682c2f1c598d4d11f62b5668a54dead8f9ed913b
4d00d3f0911d207f9941a9fd2eca859593addf0ba053eb5145b12ae1bf504829
038e68d00a8c735960284631b9f344cca80c9e673204658bb8434c5ae68c6d39
52a7a5da9798872ec71785f8329b7279e2e88ad6df6925b974fd634933e47cd1

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/cp-mfe-dev (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/cp-mfe-dev across your stack and pipelines.

  2. If you installed it — respond

    @servicetitan/cp-mfe-dev 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/cp-mfe-dev 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/cp-mfe-dev 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/cp-mfe-dev on npm has been identified as a malicious package (versions 1.115.1, 1.115.2, 1.115.3, 1.115.4, 1.115.5, 1.115.6, 1.115.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cfwx-66m7-pwp8IN-MAL-2026-012694IN-MAL-2026-012421IN-MAL-2026-012362IN-MAL-2026-012551IN-MAL-2026-012496IN-MAL-2026-012636IN-MAL-2026-012838

References

Credits

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

Detect & block this

O3 blocks @servicetitan/cp-mfe-dev-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/cp-mfe-dev (npm) malicious package — MAL-2026-11845 | O3 Security