Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@servicetitan/moneyout-api-clientnpm

@servicetitan/moneyout-api-client is a confirmed malicious npm package (MAL-2026-11906) that steals credentials and exfiltrates sensitive data (malicious versions 1.29.1, 1.29.2, 1.29.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/moneyout-api-client (npm)

MAL-2026-11906
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/moneyout-api-client

What this malware does

npm/@servicetitan/moneyout-api-client 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.

Package published under the @servicetitan scope claims to be an auto-generated TypeScript API client for MoneyOut, but ships a preinstall dropper unrelated to that purpose. package.json declares "preinstall": "node setup.mjs"; setup.mjs downloads the Bun runtime from github.com/oven-sh/bun/releases into a temp directory, chmods it executable, and execFileSyncs the sibling file math_init.js under that freshly-downloaded runtime. math_init.js is a 727 KB single-line file using string-array/index-lookup obfuscation (constant table with a custom decoder and rotator) whose contents cannot be inspected statically. Executing an obfuscated blob via an alternate runtime at install time bypasses scanners that only inspect Node-resolved code and runs attacker-chosen code on every installer with the developer's user privileges. An auto-generated API client has no legitimate need for a Bun download or an obfuscated init blob, indicating scope impersonation or maintainer compromise.

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
1.29.11.29.21.29.31.29.41.29.51.29.61.29.7

Indicators of compromise (SHA-256)

64c27655c7e3129983f27b12c0d9b667001f65b8120e6dec02dd12d0b6124aec
9651625fdbbb73fca1c9f6bf3b21a7d02d085b9c3a3a4b546c76327bd2876e2f

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/moneyout-api-client (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/moneyout-api-client across your stack and pipelines.

  2. If you installed it — respond

    @servicetitan/moneyout-api-client 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/moneyout-api-client 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/moneyout-api-client 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/moneyout-api-client on npm has been identified as a malicious package (versions 1.29.1, 1.29.2, 1.29.3, 1.29.4, 1.29.5, 1.29.6, 1.29.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9jv6-vrwm-wvjrIN-MAL-2026-011472

References

Credits

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

Detect & block this

O3 blocks @servicetitan/moneyout-api-client-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