{"answers":{"affected":"1 open source package ship an affected version, including @servicetitan/hammer-token.","exploited":"There is no known exploitation of MAL-2026-11875 in the wild and no public exploit code.","fix":"Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.","what":"MAL-2026-11875 is a malicious package in @servicetitan/hammer-token, published on 4 Aug 2026."},"fix_prompt":"MAL-2026-11875 is a malicious package: @servicetitan/hammer-token (npm). Every version was published to cause harm.\n\nTask:\n1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.\n2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.\n3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.\n4. If the package is not used anywhere, say so and change nothing.\n\nReference: https://insights.sbomify.com/MAL-2026-11875/ (Markdown: https://insights.sbomify.com/MAL-2026-11875/index.md)","id":"MAL-2026-11875","markdown":"https://insights.sbomify.com/MAL-2026-11875/index.md","name":"MAL-2026-11875","record":{"aliases":["GHSA-qvhm-jx8x-jc57"],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.\n\n@servicetitan/hammer-token@3.1.3 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\u003cversion\u003e/...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`.\n\nAny 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.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Malicious code in @servicetitan/hammer-token (npm)","id":"MAL-2026-11875","indexable":true,"kev":null,"kind":"malicious","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":[],"last_affected":[],"package":"@servicetitan/hammer-token","purl":"pkg:npm/%40servicetitan/hammer-token","source":"MAL-2026-11875"}],"products":null,"published":"2026-08-04","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"OpenSSF Malicious Packages","prefix":"MAL"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/MAL-2026-11875/"}