Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@onereach/orest-vue-demi-vue2npm

@onereach/orest-vue-demi-vue2 is a confirmed malicious npm package (MAL-2026-11617) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.4, 0.0.5, 0.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @onereach/orest-vue-demi-vue2 (npm)

MAL-2026-11617
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @onereach/orest-vue-demi-vue2

What this malware does

npm/@onereach/orest-vue-demi-vue2 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 advertises itself as a trivial vue-demi re-export shim (dist/index.mjs is ~4KB of globalThis['VueDemi'] proxy exports), but its package.json declares a preinstall hook (node setup.mjs) that downloads a Bun runtime archive from github.com/oven-sh/bun releases into a temporary directory, extracts it, chmods the binary to 0o755, and invokes it via execFileSync to run a bundled sibling file math_init.js. math_init.js is a single ~728KB line prefixed // @bun @bun-cjs, obfuscated with a string-array shuffle routine (WV8StW pushes/shifts a large numeric/string literal array) and hex-named identifiers. The payload executes under a freshly downloaded alternate JS runtime at npm install time, sidestepping inspection of what the bundle actually does. A vue-demi shim has no functional need for an alternate runtime or a 728KB opaque bundle; the shim exports are a cover for install-time execution of attacker-controlled code. The @onereach/orest-vue-demi-vue2 name and the vue-demi surface further mimic a legitimate ecosystem package the installer might expect to be safe.

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

Indicators of compromise (SHA-256)

c467fa7e75507fac7d2bc6161b72a80efeb016139d3ec2ef1386ab39a314deee
60e937585ea3196f8c6b3b927716e6dfed15ddff88f5d9979118a7e5f66b0f33
707f4495a365d9400d367c8fd9c488c9031c0b7dfd555962cc92161bd5d8da47
fc4368799710a6555e92d757da2d9c09b66b0218f88e34aad3b4a96948150d5d

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/orest-vue-demi-vue2 (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/orest-vue-demi-vue2 across your stack and pipelines.

  2. If you installed it — respond

    @onereach/orest-vue-demi-vue2 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/orest-vue-demi-vue2 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/orest-vue-demi-vue2 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/orest-vue-demi-vue2 on npm has been identified as a malicious package (versions 0.0.4, 0.0.5, 0.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vwgj-f76c-wrj3IN-MAL-2026-014169IN-MAL-2026-014068IN-MAL-2026-013839

References

Credits

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

Detect & block this

O3 blocks @onereach/orest-vue-demi-vue2-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/orest-vue-demi-vue2 (npm) malicious package — MAL-2026-11617 | O3 Security