Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @servicetitan published 141 malicious packages. See the full campaign →
Malicious package

@servicetitan/contentfulnpm

@servicetitan/contentful is a confirmed malicious npm package (MAL-2026-11841) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.3, 0.0.4, 0.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @servicetitan/contentful (npm)

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

What this malware does

npm/@servicetitan/contentful 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 declares preinstall=node setup.mjs, which downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/...zip and then invokes it via execFileSync(bun, [path.join(D, 'math_init.js')],...) to run a 727KB obfuscated bundle shipped at the package root. math_init.js is a Bun-compiled CJS artifact (// @bun @bun-cjs) whose executable content is stored in a rotated numeric/string array (n7gIxM) decoded by a custom-alphabet decoder (hc1jfK9), with randomized identifiers throughout. The file is not listed in package.json files (which only declares dist and src), and its cover name math_init.js is unrelated to the package's declared Contentful/React helper purpose. The setup.mjs wrapper itself is variable-name obfuscated. The package publishes under the @servicetitan/ scope and its declared description references Contentful, but the behavior does not match a first-party ServiceTitan library, consistent with brand-namespace impersonation. On npm install, the preinstall hook runs the fetched Bun binary against the obfuscated bundle with the installer's user privileges, executing attacker-controlled code whose semantics cannot be inspected without decoding the payload.

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

Indicators of compromise (SHA-256)

970759baa725f39721d75a58c04a090a74ea4ebf5eb71f1aaf95f40018a9f912
6a9eb94eaebdd79ffb59d0bef45030ba071c5564dc008cd8d618d5b4163a2685
f5614de1665523c04b9e6e9639277450b6c3763d86ac2c0e434cf7d690b13eb7
8cff942b44e13878aa6e74a071995a057ca8a4197686a578789c4fbc97cc3a5d
a5d672f9bd9fbc974d3fc0a28f978bfb67249c1e2965be6901277a42f9cd9705
f39a84389f2b78b80b226ff5dadb80206c181ec71f48fda14554663841d74b14
5d758373138635af5318cbabcdd12606c3b6599b5c1fa60e13ebe614fcff40c9
e46648913bcdcf0f18b06d8ea2ffe771d9a2a355f98243d2e46f2cc71a9c66ab

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

  2. If you installed it — respond

    @servicetitan/contentful 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/contentful 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/contentful 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/contentful on npm has been identified as a malicious package (versions 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qqwx-wf44-jv7fIN-MAL-2026-011441IN-MAL-2026-011490IN-MAL-2026-012667IN-MAL-2026-012147IN-MAL-2026-012143IN-MAL-2026-012248IN-MAL-2026-012707

References

Credits

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

Detect & block this

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