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

hardhat-holdnpm

hardhat-hold is a confirmed malicious npm package (MAL-2026-14246) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.1, 2.21.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hardhat-hold (npm)

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

What this malware does

The package's main entry index.js unconditionally requires./lib/config, which is a ~4MB obfuscator.io-style blob (string array of ~23,981 entries with a rotating decoder and hex-escaped literals). The readable identifiers inside that payload include execSync (child_process) and axios (HTTP client) — the local-execution and outbound-network primitives used by droppers and exfiltration stagers — and the payload runs at import time via a top-level IIFE. The wrapper index.js copies the pino logger API surface but never uses the config export; its only effect is to force the obfuscated blob to load on require(). The package name hardhat-hold is a one-token variant of the Ethereum tooling package hardhat, while the README impersonates the pino logger (including shields.io badges that still point at pino's repository), and package.json carries an unrelated boilerplate description about vulnerability management. The combination of name/README/description mismatch with an obfuscated import-time payload carrying shell-exec + HTTP primitives is the canonical typosquat-dropper shape.

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.

Malicious versions

2 flagged
2.0.12.21.0

Indicators of compromise (SHA-256)

cc09d295042df8d7132dc5b79ae9d32ab77630db037521b333a44988aed7fac1
e961a4e9f774d02e73039b143503a3fff7cad6fdbf164123d76a3d5de53c667e
6af89091e813fad5ea479c91ae40ac8fbfc58c677be758b0faa8d0c4926cb9cd

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for hardhat-hold (2 malicious versions).

  2. If you installed it — respond

    hardhat-hold is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If hardhat-hold 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-hold on npm has been identified as a malicious package (versions 2.0.1, 2.21.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018343IN-MAL-2026-018344GHSA-f33v-qqxm-m6m9

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks hardhat-hold-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

hardhat-hold (npm) malicious package — MAL-2026-14246 | O3 Security