Is @or-sdk/billing-internal safe?

npm/@or-sdk/billing-internal 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. @or-sdk/billing-internal@27.2.3 declares a preinstall lifecycle script (node setup.mjs) that downloads the Bun runtime archive from github.com/oven-sh/bun/releases/download/bun-v1.3.13/, extracts it to a temporary directory, chmods the extracted binary to 0o755, and invokes it via execFileSync against the package-local math_init.js. math_init.js is a 727KB single-line file marked '// @bun @bun-cjs' with string-array rotation (function WV8StW rotates array n7gIxM), hex-encoded numeric tokens, hex-mangled identifiers, and a decoder alphabet — obfuscation shape whose contents are unreadable by Node-based scanners. The obfuscated payload is executed automatically on npm install under an alternate runtime fetched at install time, so the code that runs on installer machines is not the JavaScript that appears in the package's declared source. The package advertises itself as a TypeScript billing SDK; downloading a second language runtime at preinstall to execute an unrelated bundled file is inconsistent with that purpose and matches the alternate-runtime-dropper pattern for supply-chain attacks. 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.

Reported by Amazon Inspector and GitHub Advisory Database via OSV.

Malicious

27.2.1, 27.2.2, 27.2.3

Move to

27.3.0 newest 27.x release, no known advisory

31.1.0 current release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install @or-sdk/billing-internal@27.3.0

OSV recordreferencereferencereferencereferenceadvisoryreferencereferencereference