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
Dependency Confusion Attacks Let Attackers Hijack Internal Library Names in Corporate Builds
A widespread supply chain risk allows attackers to publish packages with internal company names on public registries such as npm and PyPI, causing build systems to pull malicious versions instead of internal ones. The attack works because package managers treat multiple registries as a single list and select the highest version number, with no inherent priority for internal sources. Researcher Alex Birsan demonstrated the technique in February 2021 by registering names harvested from open repositories and error messages, successfully injecting packages into builds at Microsoft, Apple, PayPal, Shopify, Netflix, Tesla and Uber. The malicious code executes during installation because setup scripts and lifecycle hooks run with the privileges of the build agent, exposing environment variables, tokens and internal network access. Mitigation requires a single internal proxy repository that never mixes public responses for internal package names, scoped namespaces bound to private registries, lock files with content hashes, and disabling install scripts where possible. The technique remains effective against any organization that lists both internal and public registries in its build configuration.
NEOMSA ESB Release Strengthens Supply Chain Security Through SBOM and Dependency Hardening
Neoflex has released a new version of its NEOMSA ESB integration platform with a primary focus on cleaning up the software bill of materials and eliminating critical and high-severity vulnerabilities. The team automated SBOM generation using CycloneDX, ran SCA scans with Grype and OWASP Dependency-Check, and performed SAST and secret scanning across all build pipelines. Instead of blindly updating to the latest versions, engineers applied minimal fixed versions for each advisory while handling complex cases involving transitive dependencies, locked files, and deprecated build tools. The effort reduced the total package count from 5,872 to 1,683 after migrating the frontend build to Vite in Camel Karavan 4.18. Remaining medium and low findings were tracked in DefectDojo with clear remediation timelines. The changes deliver measurable risk reduction for on-premise deployments in critical infrastructure and financial organizations.
CodeScoring Launches CodeScoring.Save Artifact Repository for Secure Enterprise Development
CodeScoring has introduced its own artifact storage solution called CodeScoring.Save, designed to handle packages, libraries, container images, and other software components used in development. The product targets corporate users of any size seeking a predictable and resilient repository that integrates security checks directly into storage and distribution workflows. Built in Go for modern Kubernetes environments, Save supports multiple package formats including Maven, npm, NuGet, PyPI, Go Modules, Docker/OCI, DEB, and RPM while providing proxy access to external repositories. It features role-based access, auditing, independent scaling of compute and storage layers, and native integration with CodeScoring.OSA to surface vulnerability data inside the repository itself. The company positions Save as a standalone local deployment option that can operate independently or alongside its existing OSA Proxy module to block malicious components at the repository level. Future plans include support for AI models as artifacts, starting with storage and distribution for ecosystems such as Hugging Face, along with certification for Russian secure development requirements.
WordPress to Automatically Block High-Risk Plugin Updates Before Distribution
WordPress is introducing an automated security screening process for every new plugin release before it reaches millions of sites through the WordPress.org API. Updates flagged with high risk will be blocked from automatic installation, giving developers time to address issues. Previously, only initial plugin submissions were reviewed, while subsequent versions could introduce vulnerabilities, backdoors, or malicious ownership changes without checks. Each release now undergoes a six-hour delay under the Protect The Shire initiative, where multiple AI models and Jetpack Scan analyze changes to produce a combined risk score. High-risk updates are withheld from auto-updates, and developers receive detailed reports. The system has already proven effective by catching a backdoor in a plugin with around 20,000 active installations on July 28, preventing distribution after Wordfence notification. Developers can fix problems and resubmit, or appeal results, though fixing is usually faster than manual review.