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/si-step-choosernpm

@onereach/si-step-chooser is a confirmed malicious npm package (MAL-2026-11645) that steals credentials and exfiltrates sensitive data (malicious versions 0.4.4, 0.4.5, 0.4.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/si-step-chooser (npm)

MAL-2026-11645
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @onereach/si-step-chooser

What this malware does

npm/@onereach/si-step-chooser 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.

@onereach/[email protected] is published as a Vue step-chooser UI component (module: lib/component.js) but ships a preinstall lifecycle hook that runs an alien-runtime dropper. package.json declares scripts.preinstall = 'node setup.mjs'. setup.mjs is obfuscated (identifiers like _0x...) and, at install time, downloads a platform-specific Bun 1.3.13 binary zip from github.com/oven-sh/bun/releases, extracts the Bun executable to a tempdir, chmods it 0755, and execFileSync's it against a sibling file math_init.js located in the package directory. math_init.js is a 727KB Bun-compiled bundle (// @bun @bun-cjs header) obfuscated with a custom string-array rotation (WV8StW shift routine) and a large charmap literal decoded at runtime by hc1jfK9. The filename 'math_init.js' has no relationship to the advertised Vue component purpose. The net effect is that npm install of this package fetches a second runtime and executes opaque author-controlled bytes on the installer's machine, bypassing Node-based inspection. The behavior is inconsistent with the package's declared purpose, and the payload's contents cannot be inspected without executing them under Bun.

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.4.40.4.50.4.6

Indicators of compromise (SHA-256)

3a874b1628ec21f3bbe69d2052b932a5b15ff179e5ee281abe235e594f30ca0f
11602b355714414de4bfe0a671b4a48a851d849e74f0af5130dcd46c7098ebd5
27919078dbe1f6fe2cda413a0d8777f0c95b8f99549ed092bb40c49cf0dc8c05
2da1c35b42bb535cc6cb57154384f76d99b23411e651e12b738ec697a6bbc54f

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/si-step-chooser (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/si-step-chooser across your stack and pipelines.

  2. If you installed it — respond

    @onereach/si-step-chooser 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/si-step-chooser 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/si-step-chooser 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/si-step-chooser on npm has been identified as a malicious package (versions 0.4.4, 0.4.5, 0.4.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3qj3-xwcr-573vIN-MAL-2026-013778IN-MAL-2026-014096IN-MAL-2026-013989

References

Credits

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

Detect & block this

O3 blocks @onereach/si-step-chooser-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/si-step-chooser (npm) malicious package — MAL-2026-11645 | O3 Security