@servicetitan/anvil-iconsnpm

npm/@servicetitan/anvil-icons 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 package declares a preinstall script (node setup.mjs) that downloads the Bun runtime from github.com/oven-sh/bun releases, unzips it to a temp directory, chmods it executable, and then invokes the sibling file math_init.js under that freshly-downloaded runtime via execFileSync(bunPath, [join(D, 'math_init.js')], {stdio:'inherit', cwd:D}). The setup.mjs entry point itself is obfuscated with obfuscator.io-style _0xNNNN identifier names and per-function inline string-lookup objects (e.g. SBBJg:"bun", dAZFw:"bun.exe", zjKAu:"bun-dl-") that conceal the download and execution logic. The invoked math_init.js is a ~720 KB single-line opaque bundle using a shuffled string-array cipher and rotator (function WV8StW(a,b,c){...} invoked with n7gIxM=[...], header // @bun @bun-cjs), so its behavior is not observable to Node-based supply-chain scanners because it executes under Bun. The library payload in dist/index.js is an unrelated plain Material icon list, so the install-time layer has been grafted onto an otherwise ordinary-looking icons module published under the @servicetitan/* scope with homepage https://v1.anvil.servicetitan.com. This is the alternate-runtime-dropper pattern: install a second language runtime solely to execute an obfuscated sibling payload during npm install, bypassing Node-based analysis.

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.