MAL-2026-11875

    Dashboard / Malicious Package / MAL-2026-11875

    MAL-2026-11875

    Published: 4 Aug 2026Last Modified: 5 Aug 2026Aliases: 
    GHSA-qvhm-jx8x-jc57

    Summary: Malicious code in @servicetitan/hammer-token (npm)

    Details: npm/@servicetitan/hammer-token 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. Source: amazon-inspector (494cce0872c93b1f9c45922b3f1aeeab7b8ac340d651f3df8ed5a1a11bf8efd6) @servicetitan/[email protected] ships a heavily obfuscated preinstall script (`setup.mjs`, `node setup.mjs` declared as the preinstall hook) that downloads the Bun runtime from `https://github.com/oven-sh/bun/releases/download/bun-v<version>/...zip` and then uses the downloaded Bun binary via `execFileSync` to run a sibling 727KB obfuscated file `math_init.js` at install time. `setup.mjs` uses `_0xNNNNNN` hex identifiers, string-lookup indirection objects (`YCZJE: function(a,b,c,d){return a(b,c,d);}`), and wrapper functions over `https.get` and `execFileSync` to hide the fetch and exec. `math_init.js` is a Bun-compiled bundle (header `// @bun @bun-cjs`) with a rotating string-array constant table (`WV8StW`), single-letter identifiers, and hex-encoded literals; it is not the advertised design-token functionality and can only be executed through the freshly downloaded alternate runtime. A separate module `src/utils/figma/get-token.js` also references `child_process`, `fs`, `http`, `process.env`, `process.platform`, and a `POST fetch(...)` alongside Figma endpoints, consistent with additional host/network-reaching code paths. A design-token package has no legitimate need to install a second language runtime and hand it opaque bytes at install time; the obfuscation, alternate-runtime fetch, and opaque bundle together form the alternate-runtime-dropper pattern executed automatically on `npm install`. Source: ghsa-malware (31992e8da4cff46fb38e4eee40d0b550fdaa30bd82fd1f8813ddeb3010bc5902) 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.

    Affected packages

    Package

    Name: @servicetitan/hammer-token

    Purl: pkg:npm/%40servicetitan/hammer-token

    Affected ranges

    Type: N/A

    Events:

    Introduced- None
    Fixed -None

    Affected versions

    3.1.1
    3.1.2
    3.1.3
    3.1.4
    3.1.5
    3.1.6
    3.1.7
    MAL-2026-11875 | CVE-DB