MAL-2026-11833
Dashboard / Malicious Package / MAL-2026-11833
MAL-2026-11833
Summary: Malicious code in @servicetitan/carto-charts-react (npm)
Details: npm/@servicetitan/carto-charts-react 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 (8c8a840ad1455b475f5e045e12cb2e2ef51dd738990d80a8d8dd265475a202e6) @servicetitan/[email protected] declares a preinstall hook (`node setup.mjs`) that at install time downloads a platform-specific Bun runtime archive from github.com/oven-sh/bun releases, extracts the `bun` binary to a temporary directory, chmods it executable (mode 0755), and invokes it against a bundled ~727KB single-line obfuscated file `math_init.js`. `math_init.js` is a Bun-compiled bundle (`// @bun @bun-cjs`) using string-array/index-rotation obfuscation (mangled identifiers, a `WV8StW` shift-rotator, and a large numeric-encoded constants table) — its behavior is not human-inspectable from the source. The advertised purpose is a thin React wrapper over echarts-for-react, which has no need for a second JavaScript runtime or a math-named opaque bundle. The package publishes under the `@servicetitan` npm scope and references internal ServiceTitan Jira tickets in the README, consistent with dependency-confusion/brand-impersonation targeting of ServiceTitan builds and downstreams. The install-time fetch of an alternate runtime used solely to execute a sibling opaque bundle is an alternate-runtime dropper: attacker-controlled code executes on the installer's machine on `npm install` under a runtime that bypasses Node-focused install-time scanners. Source: ghsa-malware (0969b95db121d63b3f51f2699ecaaf5d9c3651e838ad7acfb2ffada3309a5d34) 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.
References: https://socket.dev/blog/popular-npm-packages-in-the-keyv-and-cacheable-namespaces-compromised-in-active-supply-chain, https://www.aikido.dev/blog/keyv-and-friends-compromised-in-npm-supply-chain-attack, https://safedep.io/keyv-npm-supply-chain-compromise/, https://www.npmjs.com/package/@servicetitan/carto-charts-react, https://github.com/advisories/GHSA-35h6-5mqq-hcj8, https://www.npmjs.com/package/@servicetitan/carto-charts-react/v/0.0.8, https://www.npmjs.com/package/@servicetitan/carto-charts-react/v/0.0.7, https://www.npmjs.com/package/@servicetitan/carto-charts-react/v/0.0.4, https://www.npmjs.com/package/@servicetitan/carto-charts-react/v/0.0.5, https://www.npmjs.com/package/@servicetitan/carto-charts-react/v/0.0.3, https://www.npmjs.com/package/@servicetitan/carto-charts-react/v/0.0.6, https://www.npmjs.com/package/@servicetitan/carto-charts-react/v/0.0.2
Affected packages
Package
Name: @servicetitan/carto-charts-react
Purl: pkg:npm/%40servicetitan/carto-charts-react
Affected ranges
Type: N/A
Events:
