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

@servicetitan/anvil2-ext-atlasnpm

@servicetitan/anvil2-ext-atlas is a confirmed malicious npm package (MAL-2026-11824) that steals credentials and exfiltrates sensitive data (malicious versions 4.0.2, 4.0.3, 4.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/anvil2-ext-atlas (npm)

MAL-2026-11824
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/anvil2-ext-atlas

What this malware does

npm/@servicetitan/anvil2-ext-atlas 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 ("preinstall": "node setup.mjs") that automatically runs on npm install. setup.mjs is obfuscated and, when bun is not already on PATH, downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/, chmods it executable in a temp directory, and uses that freshly downloaded runtime to execFileSync a sibling file math_init.js. math_init.js is a ~727 KB single-line // @bun @bun-cjs blob using obfuscator.io-style constructs (rotated string array with a WV8StW shifter, hex-mangled identifiers, custom-alphabet string decoder) and is not referenced by the library's dist/index.js entry point. The package is advertised as a ServiceTitan Anvil React UI extension and ships legitimate-looking React component code in dist/, but bundles an install-time payload unrelated to that stated purpose; package.json author, description, and keywords are empty. Invoking the payload through a second runtime that is downloaded on demand is the alternate-runtime-dropper pattern used to evade Node-focused scanning; the obfuscated bytes run with the installer's user privileges the moment the package is installed.

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
4.0.24.0.34.0.44.0.54.0.64.0.74.0.8

Indicators of compromise (SHA-256)

9059fe145d0aba75fe0ede22430a994d45eb51ad0c6ad6c4e5c5fcc02102f38c
1e61ef7efcf41cd93972d0b2e000eac70ff9c4d43802f986d1dfb533e1ca1759
3be54c4ff9e8cde477049ab64eec31809dc7a9514dd64b5672c50570001c76b6
859a5665b9e7c7b4a7800e1e3b5702e6160dc38d3fa0c2eabdc38bce238b965b
a14c3cf42dd4434743c6b27445ef70b8c07d44af4c5b152270e2d313fb6ded06
ae27d4fa59ec176b94f00449732ac1a069ee0f3db0c6ff128c194eb08eb2905c

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/anvil2-ext-atlas (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/anvil2-ext-atlas across your stack and pipelines.

  2. If you installed it — respond

    @servicetitan/anvil2-ext-atlas 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/anvil2-ext-atlas 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/anvil2-ext-atlas 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/anvil2-ext-atlas on npm has been identified as a malicious package (versions 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 4.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wrp9-26r3-whwfIN-MAL-2026-012023IN-MAL-2026-012559IN-MAL-2026-012430IN-MAL-2026-012615IN-MAL-2026-012489

References

Credits

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

Detect & block this

O3 blocks @servicetitan/anvil2-ext-atlas-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