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

@servicetitan/standalone-tm-apinpm

@servicetitan/standalone-tm-api is a confirmed malicious npm package (MAL-2026-11921) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.1, 1.1.2, 1.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/standalone-tm-api (npm)

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

What this malware does

npm/@servicetitan/standalone-tm-api 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.

The npm package @servicetitan/[email protected] executes an alternate-runtime dropper on npm install. The preinstall lifecycle hook runs an obfuscated setup.mjs that downloads the Bun runtime from github.com/oven-sh/bun/releases/download/bun-v<version>/... into a temp directory, chmods it executable, and invokes it via execFileSync to run the bundled math_init.js. math_init.js is a 727 KB Bun-compiled bundle (header // @bun @bun-cjs, sha256 9fc2570b7cef51c1b8df116d144d11ff4096357be7d2c4c6367cfc2509cf1bcc) that is heavily obfuscated with hex-named identifiers and a rotating string-array (WV8StW); it is not exported from dist/index.js, not listed in package.json files, and is referenced only by the preinstall dropper. The advertised purpose of the package is a generated NSwag/axios API client that does not require Bun. Executing an obfuscated payload under a second runtime specifically evades Node-based review tooling and is the alternate-runtime-dropper pattern; the destination host (github.com/oven-sh/bun) is a legitimate runtime source, but the harm is the fetched runtime being used to run locally-shipped attacker-controlled obfuscated code rather than the package's own shipped Node code. The @servicetitan scope suggests scope-hijack or masquerade of a legitimate publisher.

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

Indicators of compromise (SHA-256)

883339a698be93ec95dbd3daa4dc65fef1ca507525d70d1f5160649242701bb2
671483648eeee0ecb5109d91751d9432b11822f2fa5c7ec2d264ff878976b11f
2b9db5df818515834163b51f3e0660778219c6a02f4b31acec5f92957ad431b2
3625a78b2bfa8ba5adbf03cabd7f127b02b70938e4b75f0fdc7a6e54fdcfad54
3728d3567bf8ecf9d11f092c2555134e2f1723e4dc2c32f651b7c912904cf6da
baac87d411a59628926614df9d42613c3164430f95da199a5bf8034b6af8d462
bf79589d279b828d74cc35433dc88fc04b8f9f9c708c3d23dc7e35f11f004b1b
a79272b148c776700a112cfe6c178e5a2bc9b67cd0004c9a6d1470f47bd7b43c

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

  2. If you installed it — respond

    @servicetitan/standalone-tm-api 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/standalone-tm-api 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/standalone-tm-api 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/standalone-tm-api on npm has been identified as a malicious package (versions 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-87qw-vv3p-gg3hIN-MAL-2026-012094IN-MAL-2026-012311IN-MAL-2026-012676IN-MAL-2026-012197IN-MAL-2026-012392IN-MAL-2026-012238IN-MAL-2026-012872

References

Credits

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

Detect & block this

O3 blocks @servicetitan/standalone-tm-api-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/standalone-tm-api (npm) malicious package — MAL-2026-11921 | O3 Security