Malicious VS Code Extensions Masquerading as Solidity Tools Steal Crypto Wallets, API Keys and Credentials

Two malicious extensions for Visual Studio Code promoted as utilities for Solidity development have been used to steal cryptocurrency wallet data from browsers along with API keys and stored credentials. The incident once again highlights supply-chain risks in extension marketplaces: a single installation is enough to expose development secrets.

The security community has identified two malicious extensions that present themselves as tools for Solidity and the Web3 ecosystem but actually aim to harvest sensitive information from developer machines. The operation uses the clear lure of the name Solidity Pro and targets developers working with smart contracts who typically keep credentials, tokens and active sessions in the same environment.

The objective extends beyond the editor itself. Detected activity includes collection of data associated with browser-based crypto wallets, saved credentials and common development secrets such as API keys and other tokens. This type of theft is especially dangerous because one compromised workstation can open doors to lateral movement from repositories to cloud services and, in the case of wallets, direct loss of funds.

Indicators that have emerged point to two specific identifiers in the extension store: helper-beeps.solidity-pro and web3devtoolsx.solidity-pro. In a supply-chain attack of this kind the vector is rarely a complex exploit but rather an apparently legitimate installation that exploits trust in the extension ecosystem.

The operational risk grows because the editor coexists with .env files, SSH keys, system credential managers and active sessions in critical services. If an extension manages to read or exfiltrate that data, recovery is not limited to uninstalling it: organizations must assume every accessible secret on the machine may have been exposed.

The immediate recommendation is to uninstall helper-beeps.solidity-pro and web3devtoolsx.solidity-pro and prevent reinstallation. All secrets on the affected machine should be treated as compromised, tokens and API keys rotated, and recent credential usage reviewed for anomalous activity. To reduce the attack surface, teams should audit their VS Code extension inventory, remove non-essential extensions and enforce stricter installation policies with allow-lists and centralized logging.

In Web3 environments it is also advisable to separate sensitive operations from the development workstation through dedicated browser profiles, isolated accounts and, where possible, hardware wallets for signing transactions outside the reach of local software.