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

@servicetitan/microfront-testsnpm

@servicetitan/microfront-tests is a confirmed malicious npm package (MAL-2026-11903) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.11, 0.0.12, 0.0.13…). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

npm/@servicetitan/microfront-tests 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] ships a preinstall hook (package.json scripts.preinstall = "node setup.mjs") that, on every npm install, downloads the Bun runtime from GitHub releases into a temporary directory, chmods it executable, and uses it to execute a 727KB bundled JavaScript file (math_init.js) at the tarball root. math_init.js is a @bun @bun-cjs bundle with obfuscator-style shuffled string/opcode arrays and hex-mangled identifiers; setup.mjs itself uses _0x-prefixed obfuscated identifiers. The filename (math_init) and the payload's purpose are unrelated to the package's advertised functionality: the dist/ entry point is a small test helper that only re-exports ts-mockito and a couple of container/utils modules. The advertised @servicetitan scope is a well-known enterprise publisher, but the shipped payload is decoupled from the advertised public surface — consistent with a compromised or malicious publish smuggling a dropper into a test-helper package. Invocation via a freshly downloaded alternate runtime evades Node-oriented scanners and hands arbitrary code execution to whatever math_init.js contains, on any host that runs npm install on this version.

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
0.0.110.0.120.0.130.0.140.0.150.0.160.0.17

Indicators of compromise (SHA-256)

e5b54d614586f4478b82e5186e47cc7ce506a464fc6a73c5f0c3ec48b92f9355
8984f0d8d94ecf78a9496d9ad404b9928b0e82e7692495afc870121fbd7d7d1f
9ab2d763bfff3ae47f495cbb53f35804177312376fe5c0dc5953d0de002a360a
add06e0ef9b2ac476f15580b0b412dddb1fae2621cc17fcdd1d83e9a6cf5f4cd
7b8474e5d7c0a282e339401b37f6bde27a47c125be1b91cb9bf5ae5cdb30effc
7dd7168f7c7ef9c298593c0f22f9788f33b30f60206db95faf7bef5f778c97e2
47eecd862c17d7dfc6fb4dbcbb673b17a71d8c8cdb3aed7ad11c3c2e323e18d2
489d0bf9d4083cee26a4b400e33647177bdf8db21c929853723bf910421ba545

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

  2. If you installed it — respond

    @servicetitan/microfront-tests 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-tests 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-tests 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-tests on npm has been identified as a malicious package (versions 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15, 0.0.16, 0.0.17 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rrcm-p7cw-gx96IN-MAL-2026-012446IN-MAL-2026-012666IN-MAL-2026-012129IN-MAL-2026-012590IN-MAL-2026-012245IN-MAL-2026-012781IN-MAL-2026-012734

References

Credits

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

Detect & block this

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