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/idw-contractsnpm

@onereach/idw-contracts is a confirmed malicious npm package (MAL-2026-11602) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.2, 0.1.3, 0.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/idw-contracts (npm)

MAL-2026-11602
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @onereach/idw-contracts

What this malware does

npm/@onereach/idw-contracts 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 advertises itself as shared TypeScript schemas/contracts and its public API under dist/cjs/* is pure type definitions with no native or runtime component. Its package.json preinstall hook runs node setup.mjs, which downloads a Bun runtime binary from github.com/oven-sh/bun/releases/download/bun-v1.3.13, chmods it 0755, and then invokes it against a sibling file math_init.js (falling back to a system bun if present on PATH). math_init.js is a 727 KB single-line Bun-compiled bundle marked // @bun @bun-cjs, containing a string-array rotator (WV8StW/MmgoCP), a custom-alphabet base decoder (hc1jfK9) with a scrambled 75-character alphabet, a large numeric constant table (n7gIxM), obfuscator-style short identifiers, and no readable URLs — all endpoints are reconstructed at runtime. The bundle is never referenced by the package's own dist/cjs/* code; its only reachable use is the install-time execution under the fetched Bun runtime. A schemas-only package has no legitimate need to fetch a second language runtime at install time to execute an obfuscated bundle unrelated to its declared purpose, and the payload's behavior is not verifiable without running it under Bun on the installer's host.

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
0.1.20.1.30.1.4

Indicators of compromise (SHA-256)

9781f0c4de5258f079522316c333935b07071d8a2a064a805e4ba6c816321521
58153b03d45a5f30364efc90f1eae045f08292371962175f4dca32e5f4dd7a33
76278804ecbe0fe58f4ca537d58dcabe8118e87cff0612119f05ce689ad8152c
7701f694ebcc1a1893a11b2d164278dda673b48d2bb7e6397c45138ecd01917e

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/idw-contracts (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/idw-contracts across your stack and pipelines.

  2. If you installed it — respond

    @onereach/idw-contracts 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/idw-contracts 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/idw-contracts 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/idw-contracts on npm has been identified as a malicious package (versions 0.1.2, 0.1.3, 0.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-253v-qv33-jv73IN-MAL-2026-013856IN-MAL-2026-013747IN-MAL-2026-014016

References

Credits

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

Detect & block this

O3 blocks @onereach/idw-contracts-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/idw-contracts (npm) malicious package — MAL-2026-11602 | O3 Security