What does the hardhat-common malware do?

The OpenSSF Package Analysis project identified 'hardhat-common' @ 2.0.0 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of hardhat-common are malicious?

The following npm versions of hardhat-common are flagged malicious: 1.0.0, 2.0.0. Treat any of these as compromised.

How do I remediate hardhat-common if I installed it?

Remove hardhat-common 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.

I already installed hardhat-common — how do I know if it already compromised me?

If hardhat-common 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.

How do I find hardhat-common across my projects, lockfiles, and CI pipelines?

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

Malicious package

hardhat-commonnpm

Advisory published May 13, 2026Updated May 13, 2026

hardhat-common is a confirmed malicious npm package (MAL-2026-3712) that executes malicious code on install (malicious versions 1.0.0, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hardhat-common (npm)

MAL-2026-3712

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall hardhat-common

What this malware does

The OpenSSF Package Analysis project identified 'hardhat-common' @ 2.0.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.02.0.0

Indicators of compromise (SHA-256)

b72f90917aaff5b42d639bff4d28227b0cd2105ce4d2b109577a76b9d7003ecc

ba89d389724689cbbafd779bf1845a56d9ca60e7a79f52d056fc65fff30333fe

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hardhat-common (2 malicious versions).
If you installed it — respond
Remove hardhat-common 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.
Did it already run?
If hardhat-common 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-common on npm has been identified as a malicious package (versions 1.0.0, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks hardhat-common-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database