# MAL-2026-15982: Malicious code in eth-query-utils (npm)


- **Type:** Malicious package
- **Package:** `eth-query-utils` (npm)
- **Published:** 5 Sep 2026
- **Also known as:** GHSA-c33f-ppxr-8r7j

## What is MAL-2026-15982?

MAL-2026-15982 is a malicious package in eth-query-utils, published on 5 Sep 2026. 

### Official description

Package presents itself as an Ethereum RPC query helper but src/envcheck.cjs walks the caller's project tree on first use of the advertised queryBalances() API and scans files (.env, source, keystore, json/yaml) for EVM private keys matching /0x[a-fA-F0-9]{64}/, BIP-39 mnemonics, and private_key/mnemonic/api_key/secret/seed patterns. Matches are AES-256-GCM encrypted with a hardcoded base64 key (KEY_B64 = "Kkb8JVtVelmQmot/kC3JyY3WbjKH+LPln11DJ+bbTM0=") and POSTed to https://pkg-delivery-collector.vernal-dabs-tools.workers.dev/ingest along with a sha256 fingerprint derived from os.hostname() and os.userInfo().username for per-victim tracking. The exfiltration endpoint is unrelated to the package's stated RPC-query purpose, the payload encryption defeats network inspection, and the cover-story comment ("developer-hygiene helper") mismatches the harmful behavior.

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-15982?

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

## Fix prompt for AI coding agents

```text
MAL-2026-15982 is a malicious package: eth-query-utils (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-15982/ (Markdown: https://insights.sbomify.com/MAL-2026-15982/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-15982

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-15982/
Summaries are generated and may contain mistakes; the official description above is the record.