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/step-componentsnpm

@onereach/step-components is a confirmed malicious npm package (MAL-2026-11652) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.37, 0.1.38, 0.1.39). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/step-components (npm)

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

What this malware does

npm/@onereach/step-components 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 script node setup.mjs. On npm install, setup.mjs downloads a platform-specific Bun runtime binary from https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/..., extracts it, marks it executable, and invokes it via execFileSync to run a bundled sibling file math_init.js. math_init.js is a ~727 KB // @bun @bun-cjs bundle using rotated string-array obfuscation (function WV8StW(...) {... MmgoCP.push(MmgoCP.shift()); }) and opaque hex tokens. The package presents itself as a Vue components library, a purpose for which a downloaded alternate runtime is not required. Executing the payload under a freshly-downloaded runtime bypasses Node-based install-time scanning of the executed code. The combination of an alternate-runtime dropper at preinstall time and an obfuscated payload whose file name and content do not correspond to the advertised purpose indicates install-time execution of attacker-controlled code on any machine that installs this package.

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

Indicators of compromise (SHA-256)

6df5eb6548a947cb89ef2b007b7e250a8335365c0c5f2fc4401f40e7862fd69f
a24a7bf76c317ea0467cb9a483767171c2b2f4bb5184777715ceb18ce0e8cbe6
d3b19ffb47df64875eb598c2388d0584b38025214347a66cc245c190d1582bdf
dc12392b13af97e5b96e6b7626a1fc79fb488746908814d7f91504f69ceeb621

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

  2. If you installed it — respond

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

Campaign

GHSA-x3rq-c2qw-cvjxIN-MAL-2026-013858IN-MAL-2026-014051IN-MAL-2026-013743

References

Credits

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

Detect & block this

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