MAL-2026-11873 Malicious code in @servicetitan/hammer-icon (npm)
- Package
- @servicetitan/hammer-icon
- Registry
- npm
What is MAL-2026-11873?
MAL-2026-11873 is a malicious package in @servicetitan/hammer-icon, published on 4 Aug 2026.
Official description
npm/@servicetitan/hammer-icon 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 npm package @servicetitan/[email protected] advertises itself as a Material Design SVG icon set but ships two files that are not declared in package.json's files whitelist: setup.mjs and math_init.js. package.json registers "preinstall": "node setup.mjs", so setup.mjs runs automatically on npm install. setup.mjs checks whether bun is available on PATH; if not, it downloads a pinned Bun runtime (v1.3.13) from https://github.com/oven-sh/bun/releases/download/bun-v${V}/${platform}.zip, extracts it to a tmpdir, chmods it executable, and invokes it via execFileSync to run the sibling file math_init.js. math_init.js is a 727KB bundle prefixed with // @bun @bun-cjs and protected by string-array rotation obfuscation (function WV8StW rotating array n7gIxM), with no relationship to SVG icon rendering. An icon package has no legitimate reason to pull a second language runtime at install time in order to execute an obfuscated bundle that its own files manifest does not acknowledge. The scope name @servicetitan/* matches a real organization but the tarball contents are inconsistent with a first-party icon publish, indicating typosquat impersonation or scope compromise. Installing this package auto-executes attacker-controlled code on the installer's machine via a runtime fetched at install time.
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.
What should I do about MAL-2026-11873?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.
Sources
Also known as GHSA-wvxj-x32x-6p99.