Advisory

MAL-2026-11901

Also known as: GHSA-hq6q-gw89-9h5q

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in @servicetitan/microfront (npm)

Details

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

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (97537a696bdeffd5627821fef013a1c380e09dceb4213d32fecc5cf9caf228c1)
The package advertises itself as a React MicroFrontEnd integration library under the @servicetitan npm scope, but its package.json declares "preinstall": "node setup.mjs", and setup.mjs is itself obfuscated with obfuscator.io-style _0xNNNN identifiers and dictionary decoders. On npm install, setup.mjs checks for a system bun binary and, when absent, downloads a Bun runtime zip from https://github.com/oven-sh/bun/releases/download/bun-v<version>/..., extracts it to a temp directory, chmods it executable, and then runs execFileSync(<bun>, [math_init.js], {stdio:'inherit'}). math_init.js is a ~727 KB heavily obfuscated file carrying obfuscator.io fingerprints — a large mixed numeric/string array (n7gIxM=[...]), an array-rotation function, a string decoder, and opaque renamed identifiers — and begins with a // @bun @bun-cjs header, meaning it is only executable under the fetched Bun runtime and bypasses Node-based inspection. The payload's filename and contents are unrelated to any MicroFrontEnd functionality. The repository URL github.com/servicetitan/playground.git does not correspond to a genuine ServiceTitan production package, consistent with scope impersonation targeting ServiceTitan-adjacent developers. Installing the package runs attacker-controlled obfuscated code on the installer's machine.

Source: ghsa-malware (9849beffad51b9d6199e2193a03c863f16c1ee9a27ef6bf62cabfda2d22e2919)
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.

Severity

Not rated by the source.

Dates

Published
2026-08-04 15:42 UTC
Modified
2026-08-05 06:35 UTC

Affected packages and fixes

@servicetitan/microfront

npm · All systems

Affected

  • Versions: 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences