MAL-2026-11618 Malicious code in @onereach/orest-vue-demi-vue3 (npm)

Malicious package Published
Package
@onereach/orest-vue-demi-vue3
Registry
npm

What is MAL-2026-11618?

MAL-2026-11618 is a malicious package in @onereach/orest-vue-demi-vue3, published on 4 Aug 2026.

Official description

npm/@onereach/orest-vue-demi-vue3 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 Vue3 vue-demi re-export shim (dist/index.mjs contains only globalThis['VueDemi'] re-exports), but its package.json declares a preinstall hook node setup.mjs. setup.mjs checks whether bun is on PATH, and if not, downloads the Bun v1.3.13 runtime archive from GitHub, extracts the binary to a temporary directory, chmods it executable, and invokes it via execFileSync against a bundled sibling file math_init.js. math_init.js is a ~727KB obfuscator.io-style bundle (rotated string-array n7gIxM, rotation function WV8StW, hex-suffixed identifiers, // @bun @bun-cjs header) whose contents and purpose are not documented anywhere in the package and bear no relation to a Vue3 shim. Executing the payload under a freshly downloaded alternate runtime means Node-based supply-chain and dependency-scanning tooling that hooks Node lifecycle scripts never observes the code that actually runs. The advertised library surface is a decoy; the executed code is opaque and runs on every npm install.

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.

What should I do about MAL-2026-11618?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

Sources

Also known as GHSA-whj3-mhfj-38rh.

Is MAL-2026-11618 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free