# MAL-2026-4244: Malicious code in hardhat-gas-profiler-plugin (npm)


- **Type:** Malicious package
- **Package:** `hardhat-gas-profiler-plugin` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-w4rg-p3x5-fv42

## What is MAL-2026-4244?

MAL-2026-4244 is a malicious package in hardhat-gas-profiler-plugin, published on 20 May 2026. 

### Official description

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 <dev@hardhat-tools.dev>`) 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.

## What should I do about MAL-2026-4244?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4244 is a malicious package: hardhat-gas-profiler-plugin (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4244/ (Markdown: https://insights.sbomify.com/MAL-2026-4244/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4244

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4244/
Summaries are generated and may contain mistakes; the official description above is the record.