registry / @servicetitan/uikit-docs / 22.11.4

@servicetitan/uikit-docs@22.11.4

AI Security Review

scanned 11d ago · by lpm-firewall-ai

Install-time code downloads an executable runtime and runs an obfuscated payload. The payload dynamically evaluates remote content and handles developer credentials.

Static reason

One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

npm preinstall

Impact

Arbitrary code execution and possible developer-token exfiltration.

Mechanism

downloaded runtime executes obfuscated credential-harvesting remote-code loader

Attack narrative

On installation, the preinstall hook runs setup.mjs. It obtains Bun from GitHub when absent and uses it to execute the bundled obfuscated math_init.js. That payload includes dynamic evaluation of fetched response text, process execution, and GitHub/npm credential-token handling, creating an unconsented install-time remote-code and credential-theft chain.

Rationale

The lifecycle execution, downloaded interpreter, obfuscated payload, remote eval, and credential logic form a concrete malicious chain unrelated to documentation delivery.

Evidence

package.jsonsetup.mjsmath_init.js/etc/os-releasesystem temporary directory

Network endpoints1

github.com/oven-sh/bun/releases/download/bun-v

OSV Corroboration

npm/@servicetitan/uikit-docs 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 (d5eee6247514340dc4d028c15e7083b707064f40ea28981e899c6fd21936d082) The package's package.json declares scripts.preinstall = 'node setup.mjs'. setup.mjs is an obfuscator.io-style script (opaque _0xNNNN identifiers, per-scope string-map dispatchers wrapping trivial calls) whose actual behavior is to download the Bun runtime from github.com/oven-sh/bun/releases (bun-v1.3.13, arch-specific zip), extract it (using unzip on Unix or Expand-Archive/powershell on Windows, with an /etc/os-release Alpine check), chmod the binary to 0755, then execFileSync the Bun binary against a sibling file math_init.js at install time. math_init.js is a 727KB Bun-compiled bundle (header '// @bun @bun-cjs') using string-array rotation obfuscation (WV8StW rotates the n7gIxM array), and is not listed in package.json files (which only exposes 'docs'), so it is shipped in the tarball but hidden from the declared file manifest. The advertised purpose is a documentation bundle for a UI kit; downloading a second JavaScript runtime at install time and using it to execute an undeclared, heavily obfuscated sibling bundle has no relation to that purpose and matches the alternate-runtime-dropper pattern, where the alien runtime is used to bypass Node-based static analysis of the executed payload. The package is published under the @servicetitan scope and points to github.com/servicetitan/uikit.git, but the contents are inconsistent with a legitimate first-party docs artifact, indicating scope impersonation. ## Source: ghsa-malware (ad44d5f46d9f5372d3966a26bf70d34bfd11d7f54cf05a53b66b7481cbbe2723) 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.

@servicetitan/uikit-docs@22.11.4

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code