Which versions of hardhat2-config are malicious?

Every published version of hardhat2-config on npm is considered malicious. Remove the package entirely.

How do I remediate hardhat2-config if I installed it?

Remove hardhat2-config 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 hardhat2-config — how do I know if it already compromised me?

If hardhat2-config was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is hardhat2-config part of a known attack campaign?

Yes — hardhat2-config is associated with the GHSA-3cgj-gvv2-qrm4 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find hardhat2-config across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hardhat2-config (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hardhat2-config across your stack and pipelines.

Malicious package

hardhat2-confignpm

Malicious code in hardhat2-config (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1414

Immediate action

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

npm uninstall hardhat2-config

What this malware does

The package hardhat2-config was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

dcc4ecf526d7ea6da9ad012c177af156b24bd09ac322140e1390de5a3d20b5b6

c07f3569b1ea09e6b004d6249655bfae8ddcec6a95981a49adf26a2a32ebf435

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hardhat2-config (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hardhat2-config across your stack and pipelines.
If you installed it — respond
Remove hardhat2-config 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 hardhat2-config was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks hardhat2-config before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. hardhat2-config on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3cgj-gvv2-qrm4

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hardhat2-config-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