Executive Summary
In October 2025, a major supply chain risk was exposed when over 100 Visual Studio Code (VS Code) extensions were found to have leaked access tokens, allowing threat actors to publish malicious updates to widely used extensions. Attackers who obtained these tokens could have distributed compromised software versions to millions of developers globally, undermining trust in open-source ecosystems and introducing the risk of code tampering, credential theft, or insertion of backdoors into organizational environments. The vulnerability lay in the mishandling and inadvertent leakage of personal access tokens (PATs) for both the VSCode Marketplace and Open VSX, giving adversaries an insidious update path into developer workstations and CI/CD pipelines.
This incident highlights the increasing frequency and sophistication of supply chain attacks targeting developer tools and open-source dependencies. As the software landscape grows more interconnected, private access tokens and code-signing credentials now represent high-value targets, requiring robust security controls and zero trust validation across the development lifecycle.
Why This Matters Now
With attackers increasingly targeting the software supply chain and developer infrastructure, improperly secured extension publishing credentials put entire organizations and their customers at risk. The scale of VS Code extension usage means a single compromised token can rapidly propagate malicious code, stressing the need for immediate action around credential management, automated scanning, and supply chain visibility.
Attack Path Analysis
The attack began when threat actors obtained leaked personal access tokens from over 100 VS Code extension publishers, enabling direct injection of malicious code into widely used extensions. Leveraging these privileged tokens, attackers escalated access to the publisher’s update rights, distributing trojanized extensions to unsuspecting developers. Newly installed or updated malicious extensions could then pivot laterally within developer environments, potentially targeting local files or credentials. The trojanized extensions established command and control by initiating outbound traffic from compromised environments to attacker-controlled infrastructure. Sensitive information or credentials were exfiltrated via unmonitored egress channels. The impact resulted in widespread potential compromise of developer systems, propagation of malicious code, and the risk of further supply chain abuse.
Kill Chain Progression
Initial Compromise
Description
Attackers obtained leaked personal access tokens for VS Code Marketplace/Open VSX, granting them unauthorized publishing access to over 100 extensions.
Related CVEs
CVE-2023-29338
CVSS 5.5An information disclosure vulnerability in Visual Studio Code allows unauthorized access to sensitive information.
Affected Products:
Microsoft Visual Studio Code – < 1.78.0
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Supply Chain Compromise: Compromise Software Dependencies and Development Tools
Valid Accounts
Compromise Client Software Binary
Trusted Relationship
Credentials from Password Stores
Phishing
Compromise Infrastructure: Domains
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Change and Configuration Management Procedures
Control ID: 6.3.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA (Digital Operational Resilience Act) – ICT Risk Management Requirements
Control ID: Article 6
CISA Zero Trust Maturity Model (ZTMM) 2.0 – Protect Credentials and Secrets
Control ID: Identity Pillar – Credentials Protection
NIS2 Directive – Supply Chain Security
Control ID: Article 21(2)(e)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Critical supply chain exposure through compromised VS Code extensions enabling malicious updates across developer environments, threatening code integrity and deployment security.
Information Technology/IT
Leaked personal access tokens create direct attack vectors for malicious extension distribution, compromising development infrastructure and zero trust segmentation capabilities.
Financial Services
Developer toolchain compromise threatens secure application development pipelines, potentially violating PCI compliance requirements and enabling unauthorized access to financial systems.
Health Care / Life Sciences
Supply chain attacks via development tools risk exposing patient data systems, violating HIPAA compliance and threatening secure healthcare application deployment processes.
Sources
- Over 100 VS Code Extensions Exposed Developers to Hidden Supply Chain Riskshttps://thehackernews.com/2025/10/over-100-vs-code-extensions-exposed.htmlVerified
- Supply Chain Risk in VSCode Extension Marketplaceshttps://www.wiz.io/blog/supply-chain-risk-in-vscode-extension-marketplacesVerified
- Access tokens exposed by numerous VSCode extensions pose supply chain riskhttps://www.scworld.com/brief/access-tokens-exposed-by-numerous-vscode-extensions-pose-supply-chain-riskVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Zero Trust segmentation, egress policy enforcement, microsegmentation, and anomaly detection within CNSF could have constrained malicious extension communications, contained lateral movement, and enabled rapid detection of suspicious updates or data egress, mitigating the full kill chain.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Distributed inline policies detect introduction of unexpected publishing activity.
Control: Zero Trust Segmentation
Mitigation: Limits blast radius of malicious updates from compromised accounts.
Control: East-West Traffic Security
Mitigation: Restricts malicious workload-to-workload communication within cloud and dev environments.
Control: Egress Security & Policy Enforcement
Mitigation: Blocks or alerts on suspicious outbound C2 connections.
Control: Cloud Firewall (ACF)
Mitigation: Detects and blocks data exfiltration attempts through observed egress spikes.
Rapidly detects anomalous behaviors and automates incident response workflows.
Impact at a Glance
Affected Business Functions
- Software Development
- IT Security
Estimated downtime: 7 days
Estimated loss: $500,000
Potential exposure of sensitive source code, API keys, and developer credentials due to compromised extensions.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce egress controls and FQDN filtering to restrict outbound C2 and exfiltration channels from developer and CI/CD environments.
- • Implement zero trust segmentation to strictly limit permissions for extension publishing infrastructure and reduce blast radius from compromised accounts.
- • Continuously monitor east-west traffic and internal flows for lateral movement attempts using microsegmentation and workload visibility.
- • Deploy distributed threat detection and anomaly response to detect malicious updates, privilege abuse, and suspicious extension behaviors in real-time.
- • Prioritize least privilege and automate identity-based segmentation across cloud workloads and SaaS pipelines to reduce supply chain attack surface.
