CertiK Finds Hidden Hardhat Malware Targeting Crypto Developers’ Keys

CertiK Finds Hidden Hardhat Malware Targeting Crypto Developers’ Keys


Key Highlights

CertiK has identified malware linked to the PolinRider campaign hidden inside a Hardhat configuration file during a smart contract audit. The concealed JavaScript loader could run when developers execute routine commands to test or build their projects, potentially exposing their development environments and credentials to remotely downloaded code.

In a November 17 post on X, the blockchain security firm said the malicious code was embedded in the tooling developers used to configure and run their projects, rather than in the smart contracts themselves.

CertiK said it reconstructed the loader’s execution chain and outlined containment measures. Its findings show that the malicious code could run through the development workflow without requiring a contract deployment.

Malware hidden beyond the visible configuration

According to CertiK, the malicious code was concealed in a Hardhat configuration file, with a long stretch of whitespace pushing the script beyond the visible editor area.

The file appeared to contain an ordinary configuration, including compiler options, network settings, and a closing brace. However, the malicious code continued on the same line, making it difficult to notice during a conventional review.

The hidden continuation revealed | Source: CertiK

CertiK’s screenshots showed how the hidden script became visible when the file was viewed through a horizontal scrollbar or examined in a code diff.

Hardhat loads its configuration as JavaScript, meaning code placed after the visible module.exports configuration can still execute when the file is loaded. The concealed script therefore did not require a contract deployment or an on-chain exploit to activate.

Loader used Ethereum to locate remote servers

CertiK’s investigation found that the loader was designed to retrieve, decode, and execute additional JavaScript from remote servers.

The script used Ethereum as a directory for its download infrastructure. Transactions associated with a designated wallet contained encoded addresses that the loader used to locate remote payloads. The operator could update these addresses through subsequent transactions without modifying the infected repository.

The loader included alternative RPC endpoints and a fallback lookup mechanism to retrieve the server information. After locating a server, it downloaded encoded scripts and decoded them locally.

CertiK said one stage could execute within the existing Node.js process, while another could launch a hidden, detached Node.js process. The detached process could continue running even after the original development command had ended.

The script also suppressed errors, making its activity less visible during normal development operations.

Deployment keys and developer credentials could be exposed

CertiK found that the configuration loaded environment variables before executing the concealed script. This could give the downloaded code access to deployment keys, other credentials stored in the environment, and files accessible to the affected process under its permissions.

CertiK warned that a successful test would not establish that the development environment was safe. Removing the malicious line would also not reverse code that had already been executed.

However, the recovered code alone does not establish whether credentials were actually stolen or which remote payloads ran on an affected machine. Confirming the extent of any compromise would require additional host or network evidence.

The delivery mechanism could also be used to distribute other payloads, including credential stealers and tools designed to maintain access to an infected environment.

CertiK linked the recovered loader to PolinRider, a software supply-chain campaign targeting developer environments. The firm based the connection on a matching Ethereum resolver address and similarities between the loader’s payload retrieval paths and those documented in other PolinRider variants.

CertiK cautioned that disabling package installation scripts alone would not prevent this type of activity, since malicious code can execute when a configuration file or module is loaded.

Earlier malware campaigns also targeted crypto developers

The discovery follows several malware campaigns targeting crypto and Web3 developers through compromised software packages and development tools.

In June 2026, security firm JFrog identified IronWorm, a self-propagating malware campaign distributed through compromised npm packages. The malware targeted Web3 developers and was reported to steal Exodus wallet data and other sensitive information. Its capabilities also included deploying eBPF rootkits and using OpenID Connect (OIDC) tokens to spread through software supply chains.

In May 2026, security firm Socket reported a campaign called TrapDoor involving 34 malicious packages across npm, PyPI, and Crates.io. The packages targeted developers working in crypto, DeFi, Solana and AI, with the malware designed to steal cryptocurrency wallet data, SSH keys and cloud credentials.

Another campaign, Mini Shai Hulud, also used malicious npm packages to target crypto developers. The malware sought cryptocurrency wallet files, cloud credentials, SSH keys, and npm tokens, with stolen information sent through victims’ GitHub accounts.

Unlike those campaigns, the PolinRider loader was concealed in a Hardhat configuration file and used Ethereum transactions to locate remote payload servers.

Other reports also identified malware targeting crypto developers

Separate reports have also documented malware targeting crypto firms and their employees. These incidents involved different campaigns and have not been linked to PolinRider.

In April 2026, CertiK linked a campaign attributed to North Korea’s Lazarus Group, called Mach-O Man, to attempts to steal login credentials, browser data, and crypto-related access keys from high-value targets.

Around the same time, Bybit’s Security Operations Center identified a macOS malware campaign targeting developers searching for Claude Code. The reported attack chain involved search engine manipulation, an AMOS-variant infostealer, and a C++ backdoor designed to collect cryptocurrency wallet data and credentials.

CertiK advises teams to investigate and rotate credentials

CertiK advised potentially affected teams to preserve suspicious files and available logs, isolate compromised environments, and determine whether the loader had executed.

Potentially exposed deployment keys and other credentials should be rotated from a clean system. Teams should also review repository permissions and changes to determine how the malicious configuration entered the development workflow.

The extent of any exposure will depend on whether the loader executed and what access the downloaded code obtained within the affected environment.

Also Read: Binance Hackers Move $137M in ETH as Bitcoin Conversion Continues


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *