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

@servicetitan/hammer-iconnpm

@servicetitan/hammer-icon is a confirmed malicious npm package (MAL-2026-11873) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.1, 1.2.2, 1.2.3…). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

npm/@servicetitan/hammer-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 npm package @servicetitan/[email protected] advertises itself as a Material Design SVG icon set but ships two files that are not declared in package.json's files whitelist: setup.mjs and math_init.js. package.json registers "preinstall": "node setup.mjs", so setup.mjs runs automatically on npm install. setup.mjs checks whether bun is available on PATH; if not, it downloads a pinned Bun runtime (v1.3.13) from https://github.com/oven-sh/bun/releases/download/bun-v${V}/${platform}.zip, extracts it to a tmpdir, chmods it executable, and invokes it via execFileSync to run the sibling file math_init.js. math_init.js is a 727KB bundle prefixed with // @bun @bun-cjs and protected by string-array rotation obfuscation (function WV8StW rotating array n7gIxM), with no relationship to SVG icon rendering. An icon package has no legitimate reason to pull a second language runtime at install time in order to execute an obfuscated bundle that its own files manifest does not acknowledge. The scope name @servicetitan/* matches a real organization but the tarball contents are inconsistent with a first-party icon publish, indicating typosquat impersonation or scope compromise. Installing this package auto-executes attacker-controlled code on the installer's machine via a runtime fetched at install time.

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

Indicators of compromise (SHA-256)

00a0f094e67f733cae1184e1b32a61fc70dbad5e3e18244500a0859242be3c29
c9b32b3e526ebfe342dfc69a8bfc273ae2f46cd815764de74d6c813d955a6ac3
51c651950fba98ab60ee965c71403b4eb16cee166ef3977e33562aae1770ae29
5413dbb8065da086ecdfb9913fb6916b3c1ed0f291ceb8286a0c8947fd50b381
66e0896ff27200904178c3a44993da592f985ba84cbdde088f75e8b9be19c240
6da54c1c1105cebb365d740b38345e5f07374cdba5071d4a12c6fe4e132031bf
963e8d375ef911612385e832d95ebcca5e090b4eaa0c43862e1bc4672dadb17e
fd9226666c55109aac2524a110c44fa90ab20ba7cbbb5151a9cc134befe0fff2

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

  2. If you installed it — respond

    @servicetitan/hammer-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/hammer-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/hammer-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/hammer-icon on npm has been identified as a malicious package (versions 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wvxj-x32x-6p99IN-MAL-2026-012070IN-MAL-2026-012395IN-MAL-2026-012426IN-MAL-2026-012543IN-MAL-2026-012186IN-MAL-2026-012370IN-MAL-2026-012709

References

Credits

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

Detect & block this

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

@servicetitan/hammer-icon (npm) malicious package — MAL-2026-11873 | O3 Security