Is @or-sdk/base safe?

npm/@or-sdk/base 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 is itself obfuscator.io-style obfuscated (hex identifiers, dictionary-lookup dispatch) and, on install, downloads the Bun runtime archive from github.com/oven-sh/bun/releases/download/bun-v1.3.13/, extracts and chmod+x's the bun binary, then invokes it via execFileSync against a sibling file math_init.js. math_init.js is a 727KB single-line shuffled-string-array obfuscated blob (WV8StW rotator + n7gIxM array, // @bun @bun-cjs marker), has no source-tree counterpart in src/, and is undocumented in CHANGELOG. The advertised package purpose is an axios-based HTTP client SDK for onereach.io; prior versions up through 0.44.3 shipped only that SDK content with no Bun usage and no math_init payload. Version 0.44.5 adds the preinstall hook, setup.mjs, and math_init.js with no corresponding CHANGELOG entry. Executing an opaque 727KB payload under a freshly-downloaded alternate runtime at install time bypasses Node-based scanners and is the alternate-runtime-dropper pattern; the mismatch between the SDK's stated purpose and the smuggled payload, plus obfuscation of both the loader and the payload, indicates a compromised release. 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

0.44.4, 0.44.5, 0.44.6

Move to

0.45.3 newest 0.x 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/base@0.45.3

OSV recordreferencereferencereferencereferenceadvisoryreferencereferencereference