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.
Related articles
Uber Breach Exposes 149,000 Drivers After Third-Party Vendor Credentials Stolen
Uber has notified approximately 149,346 drivers that personal data was stolen in an October incident involving a compromised third-party vendor. Attackers used valid credentials belonging to the vendor to access data the ride-hailing company had shared with it, bypassing all security alerts because the access appeared legitimate. The affected information includes driver license images, names, addresses, dates of birth and government-issued identification numbers. The vendor was later identified as Fireworks AI, a cloud platform for running and fine-tuning open-source AI models. The same credential theft campaign had previously impacted Notion and Cursor. Uber immediately severed the connection upon discovery, notified regulators in multiple U.S. states, and is offering credit monitoring to affected individuals.
FBI Warns of ARTEX AI Pentest Framework Abused by Cybercriminals with Backdoored Docker Images
The FBI has issued an alert regarding the open-source ARTEX AI-powered penetration testing framework after it was observed in criminal operations targeting banks, governments, and technology companies since August 2026. Attackers achieved privileged access in under three hours in multiple incidents. The Cloud Security Alliance identified compromised Docker images containing a backdoor that executes root commands without authentication by exploiting a hidden CAPTCHA field value passed to sh -c. Approximately 9,000 downloads occurred from one malicious image, and 62 exposed consoles were found running the tampered version. Check Point reported 1,608 internet-exposed ARTEX consoles, including ten with exposed databases. The original GitHub repository was removed in October 2026, yet third-party copies and images continue to circulate. CERT-EU highlighted the lack of technical restrictions preventing out-of-scope actions by autonomous AI agents.
Optimizely Supply Chain Attack Infects BBC, CNN, HSBC and 177 Other Sites with Crypto-Stealing JavaScript
On November 16, visitors to major corporate websites received malicious JavaScript that swapped cryptocurrency wallet addresses and attempted to intercept banking card data. The code was distributed through Optimizely Web, a platform used for A/B testing. Researchers identified the malicious code in 188 scripts belonging to 178 organizations, including BBC, CNN, Fox News, HSBC, Equifax, Zoom, Salesforce, GitLab and IKEA. Attacker Scott Helm from Report URI reconstructed the attack timeline: adversaries modified the Project JavaScript field in client projects to load a file from an external domain while legitimate code continued to arrive from cdn.optimizely.com. The campaign began at 04:21 UTC on the BBC script and saw 26 payload updates throughout the day, including a card-data harvesting module added at 13:43 UTC. The malicious script could not access Stripe or Adyen payment forms inside iframes but attempted iOS exploit chains Coruna and DarkSword on affected devices. Optimizely confirmed the breach resulted from a vulnerability in Experimentation account registration, closed the flaw, removed the code and notified customers. Content Security Policy blocked the payload on only 24 of 256 tested sites, and attackers collected roughly $7,040 in cryptocurrency before cleanup completed around 21:52 UTC.
Rspamd 4.3.0 Released with Improved Phishing Detection, Attachment Scanning and Authentication Hardening
In mid-November 2026, developer Vsevolod Stakhov released Rspamd 4.3.0, the latest version of the open-source spam filtering system written in C, C++ and Lua under the Apache 2.0 license. The update strengthens HTTP connection handling, URL-based phishing checks, SPF/DKIM/ARC authentication validation and SMTPUTF8 address parsing while adding more robust attachment and HTML analysis. Key improvements include separate scoring for displayed versus actual link destinations, stricter rejection of weak DKIM keys and duplicate tags, and better archive filename handling to prevent executable hiding. The release also introduces the HTML_TINY_PIXEL_TRACKER rule to detect tracking beacons and fixes multiple bugs that could cause worker crashes or memory issues after free. Several changes may require configuration adjustments for existing users, particularly around symbol options and stricter authentication policies. Rspamd continues to support high-throughput Milter integration with Postfix and Sendmail while offering an extensive Lua API for custom processing logic.