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-checkbox-groupnpm

@onereach/si-checkbox-group is a confirmed malicious npm package (MAL-2026-11631) that steals credentials and exfiltrates sensitive data (malicious versions 0.3.5, 0.3.6, 0.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/si-checkbox-group (npm)

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

What this malware does

npm/@onereach/si-checkbox-group 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 a Vue checkbox UI component but ships a preinstall script (node setup.mjs) that downloads the Bun runtime from GitHub releases and uses it to execute a bundled 727KB obfuscated JavaScript file (math_init.js) on the installer's host at install time. Both the launcher (setup.mjs) and the payload are heavily obfuscated: setup.mjs uses obfuscator.io-style _0x-prefixed identifier mangling with per-scope constant-proxy objects; math_init.js uses a rotating string-array cipher (WV8StW push/shift over a ~500-element mixed literal/hex array). Executing the payload under a freshly-downloaded alternate runtime (Bun) rather than Node evades Node-based tooling and sandboxing. A UI checkbox library has no legitimate need for a Bun runtime, a bootstrap named math_init, or install-time obfuscated code execution — the combination is the alternate-runtime-dropper attack shape, granting the publisher arbitrary code execution on every installer's machine at npm install time.

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

Indicators of compromise (SHA-256)

e31b08e78350440e933c54b5db8266a2919d24805a3cce6bb1c46df3be58c381
7750d5989279dca78a8b56abeb860e56c1add948299eba92690d9c20fe2011a1
aee3f7c6d52f6a1cbc5ef0be22462b84ea9b9973d0c6c0916d02dae669432ea7
eb0fb8e01976666c5ff0dcc552508ca32ae002a0ba4e0c7758e9740c22e1ba62

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-checkbox-group (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-checkbox-group across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

GHSA-3x9h-hw66-mp96IN-MAL-2026-014060IN-MAL-2026-013836IN-MAL-2026-013748

References

Credits

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

Detect & block this

O3 blocks @onereach/si-checkbox-group-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-checkbox-group (npm) malicious package — MAL-2026-11631 | O3 Security