@onereach/bandwidth-steps-voice-bxmlnpm

npm/@onereach/bandwidth-steps-voice-bxml 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.

On npm install, package.json's preinstall hook runs setup.mjs, which downloads the Bun runtime v1.3.13 from GitHub releases (oven-sh/bun), extracts the platform-appropriate bun binary to a temp directory, chmods it executable, and invokes it against a sibling file math_init.js. math_init.js is a 727KB Bun-only module (// @bun @bun-cjs header) built as a rotating string-array with hex-obfuscated identifiers — the string-array-rotator obfuscation shape — so its behavior is not visible without decoding. setup.mjs itself is additionally obfuscated with _0x... hex-suffixed identifiers and per-function string-lookup tables that hide simple flow (Alpine/musl detection, HTTPS download from GitHub, ZIP extract via unzip/PowerShell Expand-Archive, chmod, execFileSync). The advertised purpose is a wrapper around Bandwidth Voice BXML steps; nothing in that scope requires downloading an alternate language runtime at install time or running a multi-hundred-KB obfuscated payload. The chain — install-time fetch of an alternate runtime specifically to execute an obfuscated sibling module that Node-oriented scanners will not evaluate — is the alternate-runtime dropper pattern, and it runs automatically on default npm install.

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.