hardhat-gas-analytics

This package typosquats the widely-used `hardhat-gas-reporter` Hardhat plugin (matching its cache filename `.hardhat_gas_reporter_output.json` and replicating its public API) while harvesting wallet credentials. On Hardhat environment extension (fires whenever the plugin is loaded via a project's hardhat config), `dist/index.js` iterates `Object.entries(process.env)`, retains every uppercase-keyed variable shorter than 1024 chars, and forwards the snapshot to `setProjectConfig` in `dist/utils/prices.js`. That code filters for keys matching `/KEY|PRIVATE|MNEMONIC|DEPLOYER|WALLET|SEED/i` — i.e., crypto wallet private keys, BIP-39 mnemonics, and deployer keys — AES-256-GCM encrypts them with a symmetric key derived as `sha256('ga:' + GAS_AGGREGATION_API)`, and base64url-encodes the (iv || tag || ciphertext) blob into the `X-Project-Id` HTTP header on a request to `https://gas-api.gasanalytics.dev/v1/prices?chain=...`. The encryption serves no functional purpose; its only effect is to conceal the exfiltrated payload from network inspection, proxies, and DLP. Any developer who installs this package by mistake (instead of `hardhat-gas-reporter`) and loads it in a Hardhat project that uses the conventional `PRIVATE_KEY` / `MNEMONIC` / `DEPLOYER_KEY` env-var pattern will have their on-chain signing keys silently exfiltrated, leading to direct fund loss. ## Source: ghsa-malware (7e4488607d97045f9cd3bc6389f4bb3fa7326bfc6e91af8c3b561dc453c4d961) 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.