Which versions of hardhat-gas-profiler-plugin are malicious?

The following npm versions of hardhat-gas-profiler-plugin are flagged malicious: 1.7.86. Treat any of these as compromised.

How do I remediate hardhat-gas-profiler-plugin if I installed it?

hardhat-gas-profiler-plugin establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed hardhat-gas-profiler-plugin — how do I know if it already compromised me?

If hardhat-gas-profiler-plugin 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 hardhat-gas-profiler-plugin part of a known attack campaign?

Yes — hardhat-gas-profiler-plugin is associated with the GHSA-w4rg-p3x5-fv42, IN-MAL-2026-003321 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 hardhat-gas-profiler-plugin 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 hardhat-gas-profiler-plugin (version 1.7.86). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hardhat-gas-profiler-plugin across your stack and pipelines.

Malicious package

hardhat-gas-profiler-pluginnpm

Malicious code in hardhat-gas-profiler-plugin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4244

Immediate action

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

npm uninstall hardhat-gas-profiler-plugin

What this malware does

Package impersonates the Hardhat plugin ecosystem (real Hardhat plugins are published under @nomicfoundation/*; the referenced github.com/hardhat/... repo is not owned by the Hardhat org). The package's index.js is a no-op stub that only requires hardhat and provides no real plugin functionality. At install time, package.json declares a postinstall hook that runs an inline node -e invoking https.get against rqnyz-2605-7280-7--2000-c51.run.pinggy-free.link/npm/-/binary/telemetry — an anonymous Pinggy reverse-tunnel hostname not affiliated with any publisher. Errors are swallowed via try/catch to keep the install silent. The beacon leaks installer source IP, install timing, and User-Agent to the tunnel operator and serves as a reachability/recon callback for follow-up targeting. Combined with placeholder author metadata (Web3 Developer Tools <[email protected]>) and the typosquat name, this is an attacker-shell package, not a real Hardhat plugin.

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

1 flagged

1.7.86

Indicators of compromise (SHA-256)

0659fba11bafbc32d157d3904df5d8c29e0f135def7730f8fe5575f8daba0316

c21e0ec3571fccc81c8e047835e84f75b6f0d95e2e4ee7e3d11537b99eab8115

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hardhat-gas-profiler-plugin (version 1.7.86). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hardhat-gas-profiler-plugin across your stack and pipelines.
If you installed it — respond
hardhat-gas-profiler-plugin establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If hardhat-gas-profiler-plugin 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 hardhat-gas-profiler-plugin 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. hardhat-gas-profiler-plugin on npm has been identified as a malicious package (version 1.7.86 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w4rg-p3x5-fv42IN-MAL-2026-003321

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hardhat-gas-profiler-plugin-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring