Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @servicetitan published 141 malicious packages. See the full campaign →
Malicious package

@servicetitan/carto-charts-reactnpm

@servicetitan/carto-charts-react is a confirmed malicious npm package (MAL-2026-11833) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.2, 0.0.3, 0.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/carto-charts-react (npm)

MAL-2026-11833
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/carto-charts-react

What this malware does

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.

@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.

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.

Malicious versions

7 flagged
0.0.20.0.30.0.40.0.50.0.60.0.70.0.8

Indicators of compromise (SHA-256)

0969b95db121d63b3f51f2699ecaaf5d9c3651e838ad7acfb2ffada3309a5d34
90690ccb7ad7ae70097d235658e82e5b87aa4bb75a04002a444fdfb34f5dc753
d8bc5b9256f86aac8c6ce47f98d2295abd868f797cea7c16a8268e437755af43
c47ff17cdbd24f0e3107f8ed3291b2f455c57b402159ffc3112b6aec9238eba6
8c8a840ad1455b475f5e045e12cb2e2ef51dd738990d80a8d8dd265475a202e6
a8df1377893427c7e21f870b0f70ad15cac23e8287958dc3a1acbcb8638c4440
4bc3f8206b6abd548678210fb2a20cf8886e6f6ec4d1ad5ca65dd4cdd1804b41
6a67c3f6619dbaf0875574c94c5b2fcce0cdbc9a8fa5ceb31093b70af28ca6b0

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @servicetitan/carto-charts-react (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @servicetitan/carto-charts-react across your stack and pipelines.

  2. If you installed it — respond

    @servicetitan/carto-charts-react is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @servicetitan/carto-charts-react was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @servicetitan/carto-charts-react before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @servicetitan/carto-charts-react on npm has been identified as a malicious package (versions 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-35h6-5mqq-hcj8IN-MAL-2026-011402IN-MAL-2026-012014IN-MAL-2026-012012IN-MAL-2026-012635IN-MAL-2026-012374IN-MAL-2026-012554IN-MAL-2026-012864

References

Credits

  • Aikido Security · finder
  • Amazon Inspector · finder
  • SafeDep · finder
  • Socket Threat Research Team · finder

Detect & block this

O3 blocks @servicetitan/carto-charts-react-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@servicetitan/carto-charts-react (npm) malicious package — MAL-2026-11833 | O3 Security