Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @onereach published 78 malicious packages. See the full campaign →
Malicious package

@onereach/billing-dtonpm

@onereach/billing-dto is a confirmed malicious npm package (MAL-2026-11589) that steals credentials and exfiltrates sensitive data (malicious versions 27.2.1, 27.2.2, 27.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/billing-dto (npm)

MAL-2026-11589
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @onereach/billing-dto

What this malware does

npm/@onereach/billing-dto 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 preinstall: node setup.mjs. setup.mjs is obfuscated with _0x-style identifiers and downloads the Bun runtime from the oven-sh/bun GitHub releases, extracts it to a temporary directory, marks it executable, and uses that dropped runtime to execute a sibling file math_init.js shipped at the package root. math_init.js is a 727KB heavily-obfuscated bundle (// @bun @bun-cjs header, string-array rotator WV8StW, decoder hc1jfK9, ~1000-entry mixed numeric/string constants array, hex-mangled identifiers) that cannot be inspected by Node-based tooling and only runs under the dropped Bun runtime. The package advertises itself as a DTO/enums types library and its declared main (dist/index.js) is a small pure enums module; neither the manifest nor any documentation references setup.mjs or math_init.js, and a types-only library has no legitimate need for an alternate language runtime or a large obfuscated bundle. The alternate-runtime-dropper shape (fetch a second runtime specifically to execute a large obfuscated sibling on npm install) combined with the DTO/payload purpose mismatch and the on-disk obfuscation is a supply-chain attack fingerprint.

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.

Malicious versions

3 flagged
27.2.127.2.227.2.3

Indicators of compromise (SHA-256)

669ca4e346719da873fc230ed5ccdc3c3a2213ca600df589230f1fb839f3d562
213407d7aee7322885aa430a28b140e6a3a976178bbe5a01e2bf88ad4e5334fb
1915077c590ac0915436e5889f0930761a55d0206a96781e632c91601426c152
a1c4598453693b8e0ddd4b89b976592541109fc16ec2787c41ea2dac86bdc447

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @onereach/billing-dto (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @onereach/billing-dto across your stack and pipelines.

  2. If you installed it — respond

    @onereach/billing-dto is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @onereach/billing-dto was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @onereach/billing-dto before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @onereach/billing-dto on npm has been identified as a malicious package (versions 27.2.1, 27.2.2, 27.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6m2r-w4cc-322cIN-MAL-2026-013491IN-MAL-2026-014055IN-MAL-2026-014190

References

Credits

  • Aikido Security · finder
  • Amazon Inspector · finder
  • SafeDep · finder
  • Socket Threat Research Team · finder

Detect & block this

O3 blocks @onereach/billing-dto-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@onereach/billing-dto (npm) malicious package — MAL-2026-11589 | O3 Security