@or-sdk/files

npm/@or-sdk/files 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 (4ef944045d465501781db7a5ee4ab89beeb0dcb026f4ce568f878352f943e76b) package.json declares scripts.preinstall = "node setup.mjs". setup.mjs downloads the Bun runtime from https://github.com/oven-sh/bun/releases/download/bun-v<version>/... into a temp directory, chmods it executable, and invokes it against a sibling file math_init.js at the tarball root. math_init.js is a single-line ~727 KB Bun-flagged bundle (// @bun @bun-cjs) using shuffled string-array + rotator obfuscation (WV8StW), a large character-code table (n7gIxM), and a string-decoder function (hc1jfK9). The filename bears no relation to the package's advertised purpose (a Files API client for OneReach), whose legitimate SDK code lives under dist/. Both setup.mjs and math_init.js sit at the tarball root and are not listed in the package's declared files whitelist ("files": ["dist","src","README.md","CHANGELOG.md"]), yet they are shipped and wired into preinstall. Fetching an alien runtime and using it to execute a large obfuscated in-tarball blob automatically on npm install is the alternate-runtime dropper pattern: the Bun runtime interprets bytecode/source that Node-based scanners will not evaluate, and the obfuscation hides the payload's actual behavior and network destinations. Execution fires without user interaction on any npm install of this version, granting the payload arbitrary code execution on the installer's machine. ## Source: ghsa-malware (7054c69b5a8183e488ff96e75d4487b684360ed043d5bae89ea647697084c1e8) 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.