npm package report

Is @onereach/billing-shared safe?

Versions 27.2.1, 27.2.2 and 27.2.3 of @onereach/billing-shared were compromised. Other versions are not flagged as malicious.

Do not install @onereach/billing-shared 27.2.1, 27.2.2 or 27.2.3

CRITICAL

Compromised releases. Added to CyberXYZ 2026-08-04, OSV malicious-package feed (Google / OpenSSF).

// what we observed

npm/@onereach/billing-shared 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. The package declares a preinstall hook (node setup.mjs) that runs automatically on npm install. setup.mjs is variable-name-obfuscated and constructs a URL of the form https://github.com/oven-sh/bun/releases/download/bun-v<ver>/<archive>.zip, downloads the Bun runtime, unzips it, chmods the binary 0o755, and then invokes execFileSync(bun_path, [<math_init.js>]). The sibling math_init.js is a single-line ~727KB opaque bundle starting with // @bun @bun-cjs, using a string-array rotation function and a multi-thousand-entry integer/char lookup table (canonical string-array-shuffle obfuscation). math_init.js is not referenced from the package's dist/ Node sources — it is reachable only via the preinstall Bun invocation, meaning its contents never appear in the Node module graph and are executed exclusively by the freshly-dropped alternate runtime. The advertised purpose of the package is CSV/enum billing helpers, which has no need for a bundled Bun runtime or a 727KB opaque payload. The combination of an install-time alternate-runtime drop, wrapper obfuscation, and an opaque obfuscated payload executed under that dropped runtime is a supply-chain dropper: npm install of this version runs attacker-supplied, intentionally hidden code on the installer's machine. 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.

// versions and what to do
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 @onereach/billing-shared@27.3.0

OSV recordreferencereferencereferencereferenceadvisoryreferencereferencereference

// reach

0 direct dependencies

none carry a known advisory

    1 packages depend on it

    an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.



    Checked 2026-10-31 at 00:02 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.