@servicetitan/link-item@41.3.4

npm/@servicetitan/link-item 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 (523da38020b105aadf1df6651b13ae858b629bd0f3b241a78c5c0a86c4ffff6b) The package presents itself as a React link-item UI component (@servicetitan/link-item, homepage docs.st.dev) but its preinstall hook runs setup.mjs, which downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v<ver>/, extracts and chmod +x's it, and then execFileSyncs a sibling file math_init.js under that runtime. math_init.js is a ~711KB obfuscated JavaScript blob at the tarball root using a rotated string-array + integer-lookup cipher (WV8StW shift loop, n7gIxM constant array, hc1jfK9 decoder). math_init.js is not declared in package.json's `files` array (which lists only `dist` and `src`) and has no relation to a React UI component. The runtime and payload are unrelated to the package's advertised purpose; installing the package causes arbitrary code, hidden under an alternate JavaScript runtime, to execute on the installer's host at npm install time. The metadata cover story diverging from the shipped behavior is consistent with an impersonation or scope-hijack of the @servicetitan namespace. ## Source: ghsa-malware (95cd84d8de586763bbf47cbfbebb9317856c73d3edcaae675a65bf2eaeafd2f0) 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.