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-ui-componentsnpm

@onereach/idw-ui-components is a confirmed malicious npm package (MAL-2026-11605) 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-ui-components (npm)

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

What this malware does

npm/@onereach/idw-ui-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.

package.json declares scripts.preinstall = 'node setup.mjs'. setup.mjs is itself obfuscated with obfuscator.io-style hex identifiers (_0x... variables, per-function alias tables mapping method calls and string constants such as '--version', '/etc/os-release', 'Alpine'). It constructs a URL of the form https://github.com/oven-sh/bun/releases/download/bun-v<version>/<platform>.zip, downloads the Bun runtime binary, chmods it 0755, and then execFileSyncs the Bun binary against a bundled sibling file math_init.js in the package directory. math_init.js is a ~730 KB single-line file tagged '// @bun @bun-cjs' with mangled identifiers, a ~thousand-entry string/number constant table, and a rotation function (WV8StW) that shifts that table — a heavily obfuscated Bun-compiled payload. The package is advertised as a UI-components library and has no functional need for an alternate JavaScript runtime; the effect of npm install @onereach/idw-ui-components is to fetch a runtime specifically to execute a concealed payload that Node-based scanners do not inspect. Both the preinstall dropper and the executed payload are obfuscated, and the payload's name ('math_init') is unrelated to the stated UI purpose.

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)

1eace483be8eea721e54ca46b6c2e0a3a9a5b48bed630479af3ee5eaf483f2e2
9be74c4436955074dbb166655f843c3e348d29d636cfd44328cb0284390fdf5a
31a3e4ddc00fec14f6d8972757e768d6b7743225a6313f0a0048c1d90a4ba9b5
ffabc7c26b28b7c43ff7742b6349d5c8970f5058234191cbd8a5fafe5f6dc844

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

  2. If you installed it — respond

    @onereach/idw-ui-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/idw-ui-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/idw-ui-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/idw-ui-components 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-5hwg-34v3-gf8xIN-MAL-2026-013638IN-MAL-2026-014048IN-MAL-2026-014197

References

Credits

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

Detect & block this

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