MAL-2026-17559 Malicious code in hardhat-kex (npm)
Malicious package
Published
MAL-2026-17559 is a malicious package: hardhat-kex (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-17559/ (Markdown: https://insights.sbomify.com/MAL-2026-17559/index.md)
- Package
- hardhat-kex
- Registry
- npm
What is MAL-2026-17559?
MAL-2026-17559 is a malicious package in hardhat-kex, published on 5 Oct 2026.
Official description
The npm package [email protected] ships an obfuscated 4.5MB single-line bundle at lib/config.js (obfuscator.io-style string-array with a 26,234-entry table and numeric-dispatch wrapper, containing exec strings). The package main index.js unconditionally executes this bundle on require via
const config = require('./lib/config'); the return value is never used, so the sole effect of importing the package is to run the obfuscated code. The surface API exported by index.js is an unrelated stub Express middleware that calls next(). The tarball additionally ships verbatim files from the pino logging library (lib/proto.js, levels.js, transport.js, worker.js, redaction.js, docs/, index.d.ts, README.md) despite the package being named for the Hardhat/Ethereum ecosystem and describing itself as a vulnerability-management tool; none of the pino sources are reachable through the exported API. The name/description/API mismatch combined with bundled pino cover-story files is a decoy pattern designed to make the tarball appear legitimate while the obfuscated loader is the only code that actually runs. Any project adding hardhat-kex as a dependency will execute the opaque payload on import.What should I do about MAL-2026-17559?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.