registry / @servicetitan/eslint-config / 38.1.4

@servicetitan/eslint-config@38.1.4

Core ESLint rule sets for ServiceTitan web projects

AI Security Review

scanned 11d ago · by lpm-firewall-ai

Installing the package invokes an obfuscated payload through preinstall. The payload can obtain and execute a runtime, collect credentials, and send data to remote services.

Static reason

One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source

Trigger

npm install/preinstall

Impact

Credential theft and arbitrary remote code execution during dependency installation.

Mechanism

downloaded runtime executes obfuscated credential-harvesting payload with remote eval

Attack narrative

The preinstall hook runs setup.mjs, which either invokes Bun or downloads it from GitHub and executes math_init.js. That obfuscated payload contains network fetches whose response is passed to eval, gathers token-bearing credential sources, and uploads collected information. This is unrelated to ESLint configuration and executes without user action during installation.

Rationale

This is a concrete install-time execution and credential-exfiltration chain, not a scanner-only inference.

Evidence

package.jsonsetup.mjsmath_init.js

Network endpoints1

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

OSV Corroboration

OpenSSF/OSV

npm/@servicetitan/eslint-config 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 (213c12d2b5869659044f11206a7184ef75fd3be6f15f9e1f66e3f2e4525d7924) The package's preinstall hook runs setup.mjs, which is itself obfuscated with identifier mangling (_0xNNNNNN names) and string-array indirection hiding constants like '--version', 'node', 'bun', and the download URL. When no system Bun is available, setup.mjs downloads a Bun binary from https://github.com/oven-sh/bun/releases/download/bun-v<version>/... into a temp directory, chmods it executable, and execFileSyncs it against math_init.js — a ~727KB Bun-CJS bundle shipped in the tarball. math_init.js is heavily obfuscated with a shuffled string/number array (n7gIxM) and a rotation function (WV8StW) that reconstructs identifiers and strings at runtime, with hex-name mangling throughout. The declared purpose of the package is an ESLint configuration ruleset, which has no legitimate need for a second language runtime or an obfuscated multi-hundred-kilobyte init script. Fetching an alternate runtime specifically to execute an opaque sibling blob at install time is a dropper pattern that runs on npm install and bypasses Node-only static inspection of the executed code. ## Source: ghsa-malware (c23f877ad5f8763a28c7d4d2735164b8fb3f6650cf0d1a040c57cb81dce2ff4f) 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/eslint-config@38.1.4

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code