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

hardhat-kexnpm

Advisory published Updated

hardhat-kex is a confirmed malicious npm package (MAL-2026-17559) that executes malicious code on install (malicious version 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hardhat-kex (npm)

MAL-2026-17559
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall hardhat-kex

What this malware does

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.

Malicious versions

1 flagged
2.0.1

Indicators of compromise (SHA-256)

b8fa212654344b734814cee2291c9b9b91ecbc353bde5e83740624ee5f263c69

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for hardhat-kex (version 2.0.1).

  2. If you installed it — respond

    Remove hardhat-kex from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If hardhat-kex was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hardhat-kex on npm has been identified as a malicious package (version 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021008

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks hardhat-kex-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

hardhat-kex (npm) malicious package — MAL-2026-17559 | O3 Security