MAL-2026-11756 Malicious code in @ornikar/graphql-config (npm)
- Package
- @ornikar/graphql-config
- Registry
- npm
What is MAL-2026-11756?
MAL-2026-11756 is a malicious package in @ornikar/graphql-config, published on 4 Aug 2026.
Official description
npm/@ornikar/graphql-config 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.
@ornikar/[email protected] declares a preinstall hook (node setup.mjs) that runs automatically on npm install. setup.mjs uses _0xNNNNNN-style identifier obfuscation and per-call string-lookup objects to hide its constants; when bun is not already on PATH it downloads a Bun runtime archive from github.com/oven-sh/bun/releases/download/bun-v<VER>/<platform>.zip, unpacks it to a temp directory, chmods the binary executable, and invokes it (execFileSync) to run the sibling file math_init.js. math_init.js is a 727KB Bun-compiled bundle (// @bun @bun-cjs) with hex-scrambled identifiers and no readable source. The advertised purpose of the package is GraphQL configuration/validation, which has no relationship to Bun or a compiled binary payload. The combination — install-time execution, alternate-runtime dropper that bypasses Node-based scanner visibility, obfuscation of both the loader and the payload, and a cover-story package name unrelated to what is executed — is the alternate-runtime install-time-RCE dropper pattern. The bytes executed under the fetched Bun runtime cannot be traced from Node tooling.
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-11756?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.
Sources
Also known as GHSA-pwmg-hhvx-94mr.