CertiK Finds PolinRider-Linked Malware in Hardhat Configuration
The loader could run during routine tests or builds and expose credentials available to Node.js. CertiK did not confirm credential theft.

CertiK found a concealed malware loader in a smart contract project's Hardhat configuration that could run during routine test or build commands and expose credentials available to the development process. The firm published its findings Nov. 17.
The code was hidden beyond the visible part of the configuration file by a long stretch of whitespace. Hardhat loads the file as JavaScript, so ordinary project commands can execute code attached to the configuration. The loader could run through routine development commands without a contract deployment or an on-chain exploit.
Ethereum transaction data helped the loader find a remote server address. It then downloaded and decoded scripts from that server; the transactions pointed to the infrastructure rather than carrying the scripts themselves. Another transaction could redirect the loader to a different server without a repository change. The code could run inside the existing Node.js process or launch a detached Node.js process.
The configuration loaded environment variables before the concealed script, potentially giving remotely supplied code access to deployment keys and other credentials available to the Node.js process. CertiK tied the loader to the PolinRider campaign through a shared Ethereum resolver address and matching payload retrieval paths.
The project was not identified, and no estimate was given for repositories, developers or machines that may have been exposed. Host or network evidence would be needed to determine whether later payloads ran or credentials were stolen. “The recovered code establishes the malicious execution mechanism,” CertiK said.
The finding differs from an earlier warning about the sol-live GitHub project targeting crypto wallet data. SlowMist said that project hid a malicious command in VS Code workspace settings and required developers to start a configured terminal. The Hardhat loader, by contrast, could run during routine tests or builds.