@or-sdk/tables@0.28.6

npm/@or-sdk/tables 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. --- ## Source: amazon-inspector (aed35089f0b3561625fb68b453c85f8459f9ee38409ed9b635b107337ddc65a2) The package's declared preinstall hook (`node setup.mjs`) downloads the Bun runtime from GitHub releases (`https://github.com/oven-sh/bun/releases/download/bun-v<version>/<platform>.zip`), extracts it, sets it executable via `chmodSync(..., 493)`, and then invokes it via `execFileSync(bun, ['math_init.js'],...)` to execute a 727KB heavily obfuscated bundled sibling file (`math_init.js`). Both setup.mjs and math_init.js are deliberately obfuscated: setup.mjs uses obfuscator.io-style hex identifier mangling (`_0x488df8`) and string-map indirection for every literal (`WuGMv:"musl"`, `TdVzu:"/etc/os-release"`), and math_init.js begins with a `@bun @bun-cjs` compiled header and a shuffled string-array rotator (`function WV8StW(){ MmgoCP.push(MmgoCP.shift());... }`) over a large mixed literal array. The pattern — obfuscated fetch of an alternate JS runtime followed by execution of an obfuscated bundled payload under that runtime — matches the alternate-runtime dropper shape and evades Node-based inspection. A table-SDK client library has no legitimate reason to ship a runtime dropper. Installing this version results in arbitrary attacker-controlled code executing on the installer host at `npm install` time. ## Source: ghsa-malware (065ad300205f96f690c7fbd46802af46d32c08342a10fad7457ab23f4603d582) 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.