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

@servicetitan/contentful-proxynpm

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

Malicious code in @servicetitan/contentful-proxy (npm)

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

What this malware does

npm/@servicetitan/contentful-proxy 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 a preinstall hook ("preinstall": "node setup.mjs") that runs at npm install time. setup.mjs downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v<version>/<arch>.zip, extracts it to a temp directory, marks the binary executable, and invokes it via execFileSync(bunPath, [path.join(D, 'math_init.js')], { cwd: D }). The sibling file math_init.js is a 727KB heavily obfuscated JavaScript blob marked // @bun @bun-cjs, containing a large hex-indexed opcode/string array (n7gIxM=[0x0,0x1,0x8,...]), a rotating array-shuffle dispatcher (WV8StW), a decoder function hc1jfK9, and no source map, license header, or human-readable identifiers. The Bun runtime is fetched specifically so this payload is executed outside Node's evaluation surface. Nothing about a Contentful proxy client requires the Bun runtime or a 727KB obfuscated math_init.js; the file's name is unrelated to the package's advertised purpose. The dist/ tree contains benign auto-generated NSwag Contentful client stubs, indicating the dropper was injected on top of an otherwise legitimate baseline (consistent with a scope/account compromise or malicious version bump).

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

Indicators of compromise (SHA-256)

18f1e6ac57ae795a8a1e0d5730ca961650051a4a1217f67f8180428ed7e65a44
4ca07a12ff78f43f8b176919730fab7b1cb155f78d62a4f53d11f6e0ce548186
58024f6c37cfb6fccc9f958f3c489fe4bf28a359bd83ff7f4c9773fb2dd291bf
326c312dcec8961fc7c7da83f57bd0fe287a9aebfbfe357c4b1667a01df1fc59
5af78c041e01a8a712cf6a9e4df5d97ef9a051299be35b1f93ad41c27804aa9d
6ec98b629325f44c7fc52817bf458368e40d9e4ce258d728e2c5c128c4debfc2
e1c4f39c4f2eae1cfc530bc23ad9031a933bc9722baaf441a92cdeddc7005af0
54a8359cb589db751571a43bcc9379363132f385817b0024902e5f9786b6c9c2

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

  2. If you installed it — respond

    @servicetitan/contentful-proxy 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-proxy 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-proxy 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-proxy on npm has been identified as a malicious package (versions 1.1.12, 1.1.13, 1.1.14, 1.1.15, 1.1.16, 1.1.17, 1.1.18 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r9xm-2rwj-6g35IN-MAL-2026-011420IN-MAL-2026-011455IN-MAL-2026-012067IN-MAL-2026-012084IN-MAL-2026-012077IN-MAL-2026-012443IN-MAL-2026-012751

References

Credits

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

Detect & block this

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