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

@servicetitan/anvil-iconnpm

@servicetitan/anvil-icon is a confirmed malicious npm package (MAL-2026-11817) that steals credentials and exfiltrates sensitive data (malicious versions 0.5.1, 0.5.2, 0.5.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/anvil-icon (npm)

MAL-2026-11817
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/anvil-icon

What this malware does

npm/@servicetitan/anvil-icon 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 package declares itself as a Material Design icon SVG library but ships a preinstall script (setup.mjs, invoked via package.json scripts.preinstall) that downloads the Bun runtime binary from a GitHub release into a temporary directory, chmods it executable, and then uses it to run a sibling file math_init.js against the installer's host. math_init.js is a 727 KB blob whose header is // @bun @bun-cjs, obfuscated with a shuffled string-array plus alphabet-decoder pattern so its behavior cannot be resolved statically. setup.mjs itself is obfuscated with hex-style identifiers (_0x488df8, _0x19328d.YCZJE(...) wrappers around calls such as execFileSync('ldd',...)), matching the obfuscator.io style. Fetching a second language runtime and using it to execute an opaque bundled script at npm install time has no relationship to distributing icon SVGs; the alternate runtime bypasses Node-based inspection and the obfuscation of both the driver and the payload is consistent with deliberate evasion. Installing this package results in execution of attacker-staged, unreadable code on the installer's machine before any consumer code runs.

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

Indicators of compromise (SHA-256)

a8cc79f4cc10fbf1480118b148c8a0afd7a6e644fa6b888e09c96c233f36d182
1259127409f68eceac2608de88b6d69e369d8a0d27205b6df0c7b97d81ac7706
6f53e6258e90fd3bc5a893fe2c5a89677ade610739c27752f81d2d615516e998
8c0d2fcb0bd8a2ad974484a9c0ba473bca073f38c064325d2fd4424b84925bd0
8dc1692b094a11a8579fab84d7377fe65631b140909ec27559c13ac8675aa9c8
9389cb11b90a604d7133a25b6313f8374b309e6c8372a14730b27a977198a9d5
ca88baefc8f9fe1e4ee292e09d73561288e098a3478826bf191ca7d305f663ba

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/anvil-icon (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/anvil-icon across your stack and pipelines.

  2. If you installed it — respond

    @servicetitan/anvil-icon 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/anvil-icon 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/anvil-icon 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/anvil-icon on npm has been identified as a malicious package (versions 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.5.5, 0.5.6, 0.5.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3q3h-xxpq-cprgIN-MAL-2026-012266IN-MAL-2026-012440IN-MAL-2026-012153IN-MAL-2026-012294IN-MAL-2026-012509IN-MAL-2026-012675

References

Credits

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

Detect & block this

O3 blocks @servicetitan/anvil-icon-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