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

@servicetitan/standalone-core-feature-gatesnpm

@servicetitan/standalone-core-feature-gates is a confirmed malicious npm package (MAL-2026-11918) that steals credentials and exfiltrates sensitive data (malicious versions 1.11.4, 1.11.5, 1.11.6…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/standalone-core-feature-gates (npm)

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

What this malware does

npm/@servicetitan/standalone-core-feature-gates 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.

package.json declares a preinstall hook node setup.mjs. setup.mjs downloads the Bun runtime binary from the oven-sh/bun v1.3.13 release, extracts it to a temp directory, marks it executable, and then invokes the sibling file math_init.js under that freshly downloaded Bun runtime via execFileSync. math_init.js is a 727KB // @bun @bun-cjs bundle carrying obfuscator-style string-array rotation (function WV8StW(...) {... MmgoCP.push(MmgoCP.shift()) }), a large mixed numeric/string constant array, and hex-mangled identifiers. The package's advertised purpose is a React feature-gate library that has no need for a second language runtime or for a multi-hundred-KB obfuscated blob. Using an alternate runtime to execute the obfuscated bundle bypasses Node-based install-time inspection and runs attacker-controlled code on any machine that runs npm install against this version. Version 1.11.4 also introduces this behavior for the first time — CHANGELOG.md's last entry is v1.11.3, package.json author is empty, and prior versions contain neither the preinstall hook, nor setup.mjs, nor math_init.js — consistent with a compromised release under an existing 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
1.11.41.11.51.11.61.11.71.11.81.11.91.11.10

Indicators of compromise (SHA-256)

c2adbd5c91533b653064f3b40e16311e94f571d998ad8fdd726ddc8baf50e1c7
0f933664f1929aa3ce13fb32f4564b7517c70312b3436f766ff34afe79c9ad0c
21842bb26c689a0c4b56d51be19658c755d6222b5b2cfc3fedd0bdca01dfadf2
67b2043e71528a12c73c2cabe99f8523524397ee3ebee55758d0ac17557e6c19
83c7a5fc6f6f0f047c08752e92f69609d9d06fdbb6fef9f7d84136e8a2777998
f40e164343ab47e9c733660cafc68829068edc28fbcb490ac5a627d494b77e64
f649da2222f176034b675cb39c3dff4e1e4bbfa089060185c1e3792db21a0b40
fefec48481767d4224997ecf438ad3be437203769663cd2bde6c625199615ee9

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

  2. If you installed it — respond

    @servicetitan/standalone-core-feature-gates 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-core-feature-gates 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-core-feature-gates 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-core-feature-gates on npm has been identified as a malicious package (versions 1.11.4, 1.11.5, 1.11.6, 1.11.7, 1.11.8, 1.11.9, 1.11.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gm7c-3jq6-ch43IN-MAL-2026-012567IN-MAL-2026-012130IN-MAL-2026-012396IN-MAL-2026-012649IN-MAL-2026-012700IN-MAL-2026-012441IN-MAL-2026-012782

References

Credits

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

Detect & block this

O3 blocks @servicetitan/standalone-core-feature-gates-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-core-feature-gates (npm) malicious package — MAL-2026-11918 | O3 Security