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

@servicetitan/feature-spotlightnpm

@servicetitan/feature-spotlight is a confirmed malicious npm package (MAL-2026-11867) that steals credentials and exfiltrates sensitive data (malicious versions 3.9.1, 3.9.2, 3.9.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/feature-spotlight (npm)

MAL-2026-11867
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @servicetitan/feature-spotlight

What this malware does

npm/@servicetitan/feature-spotlight 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.

Version 3.9.5 of this package declares a preinstall hook (node setup.mjs) that fires automatically on npm install. setup.mjs downloads the Bun runtime from GitHub releases (https://github.com/oven-sh/bun/releases/download/bun-v<version>/<platform>.zip), unpacks it to a temp directory, marks it executable, and invokes it against a sibling file math_init.js (execFileSync(bunPath, ['math_init.js'], {cwd: D})). math_init.js is a single-line 727KB heavily obfuscated JavaScript blob (hex-named identifiers, string-array rotator WV8StW shifting a large numeric/string constant table) with no exports consumable by the package. The advertised purpose of the package is a small React feature-spotlight UI helper; the shipped dist/index.js is only 168 bytes. Executing a 727KB opaque payload through a separately downloaded alternate runtime has no relation to that purpose, and the choice of Bun (rather than the already-present Node interpreter) bypasses Node-based static analysis of the payload. The behavioral shape — legitimate scope, tiny declared library, install-time fetch of an alien runtime to execute an obfuscated sibling payload — matches version-specific injection into an otherwise legitimate npm scope.

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
3.9.13.9.23.9.33.9.43.9.53.9.63.9.7

Indicators of compromise (SHA-256)

f55f32c34612150b92148db1bd894fde4673f9e5c233c6baa79d6a7b7948d6c5
f9fe80e5718d5ea9b8e4eb9b7b372e0ee5ab194cb74cd84e9b73957c4a31b49e
2fd0300976ced9c2b089453ba25d34cd3d9f9feb2917dd83be7c3ef27879c763
6a350ac0170bdb1b99929cd0a691290dfffe6d8e75fefeab1372f8bfabb1e6ce
b16a4ac80e30e4d071ea6e2da40f00641c6191272490a14b5f4cc225d04b060e
fc929d6c249936f782e50c49a7f1ff920c8e34814071c2e261fbeb6811cdc0a3
1a6addadc9e8f30243088581990a8692410b58e72c51a714a2283fa40e33fbc8
924d675cd44556cb5449e63d231b2cc4de23aa7417c6b03cb36b73466416d832

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

  2. If you installed it — respond

    @servicetitan/feature-spotlight 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/feature-spotlight 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/feature-spotlight 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/feature-spotlight on npm has been identified as a malicious package (versions 3.9.1, 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-83cv-cpcx-f26vIN-MAL-2026-012028IN-MAL-2026-012388IN-MAL-2026-012521IN-MAL-2026-012219IN-MAL-2026-012148IN-MAL-2026-012364IN-MAL-2026-012728

References

Credits

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

Detect & block this

O3 blocks @servicetitan/feature-spotlight-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/feature-spotlight (npm) malicious package — MAL-2026-11867 | O3 Security