registry / @servicetitan/carto-charts-react / 0.0.5

@servicetitan/carto-charts-react@0.0.5

Carto web chart host: a declarative <Chart> over echarts-for-react with the SVG renderer, rendering the platform-neutral option specs and theme from @servicetitan/carto-charts-core.

AI Security Review

scanned 11d ago · by lpm-firewall-ai

npm preinstall executes an obfuscated secondary payload. The payload can fetch and eval remote content and handles tokens.

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 install

Impact

Arbitrary code execution and credential/token theft in the installer environment.

Mechanism

downloads/executes Bun, then runs obfuscated payload with remote eval

Attack narrative

On npm installation, package.json invokes setup.mjs. It runs math_init.js with Bun; if Bun is absent it downloads an executable from GitHub, extracts it to a temporary directory, and executes it. math_init.js is an obfuscated loader containing dynamic evaluation of fetched response text and code paths for token handling and child-process execution, enabling a remotely controlled payload during install.

Rationale

The install-time loader is unrelated to the declared chart package and creates a concrete remote-code-execution chain with credential-access capability.

Evidence

package.jsonsetup.mjsmath_init.jsdist/index.js

Network endpoints1

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

OSV Corroboration

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 (90690ccb7ad7ae70097d235658e82e5b87aa4bb75a04002a444fdfb34f5dc753) @servicetitan/carto-charts-react@0.0.8 ships an obfuscated preinstall script (setup.mjs) that downloads the Bun runtime from oven-sh's GitHub releases for the host platform, extracts it to a temp directory, chmod +x's the binary, and immediately executes a bundled 727KB obfuscated CJS payload (math_init.js) with that alternate runtime. Both setup.mjs and math_init.js are transformed with obfuscator.io-style techniques (shifted string arrays, hex-named identifiers, custom-alphabet decoders, per-function property maps that hide simple literals like "unzip", "--version", "ldd", and the GitHub URL). package.json declares "files":["dist"], yet setup.mjs and math_init.js are shipped at the tarball root outside the declared files surface. The alternate-runtime-dropper pattern (invoking a second, non-Node runtime at install time) bypasses Node-based install scanners; the payload's contents cannot be audited by the installer before execution. A React wrapper around echarts-for-react has no legitimate need to fetch a second language runtime or execute an obfuscated bundle on install. ## 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.

@servicetitan/carto-charts-react@0.0.5

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code