Executive Summary
In December 2025, two malicious Visual Studio Code extensions—Bitcoin Black and Codo AI—were uncovered on Microsoft’s official VSCode Marketplace, executing a supply chain attack that targeted developers. Published by an entity named 'BigBlack', these extensions installed information-stealing malware by abusing extension privileges. The malware leveraged DLL hijacking and covert batch scripts to steal credentials, browser session cookies, cryptocurrency wallet data, and system information from infected developer machines, storing exfiltrated data for later retrieval. The incident highlights how even widely trusted software platforms can host weaponized add-ons capable of compromising sensitive environments.
This breach exemplifies the growing risks posed by open-source and third-party software supply chain compromises, especially targeting developer tools. The ease with which unvetted code can be distributed through official registries underscores the need for rigorous extension security and policy enforcement in enterprise environments.
Why This Matters Now
Attackers increasingly exploit the trust inherent in software marketplaces to deliver malware directly to developer workstations, bypassing traditional security layers. Given the critical role developers play, compromising their endpoints creates cascading risks across the entire software development lifecycle and supply chain.
Attack Path Analysis
The attack began with malicious VSCode extensions published on Microsoft's marketplace, luring developers into installation (Initial Compromise). Upon activation, the extensions executed hidden scripts to deploy infostealer malware and obtain further system privileges (Privilege Escalation). The malware leveraged compromised machines to access sensitive user data and browser sessions, potentially pivoting within developer environments (Lateral Movement). It established covert channels to download payloads and communicate outbound with command infrastructure (Command & Control). Stolen data, including credentials, cookies, and crypto wallets, were exfiltrated to attacker-controlled destinations (Exfiltration). The ultimate impact included theft of sensitive information, potential session hijacking, and further compromise of developer assets (Impact).
Kill Chain Progression
Initial Compromise
Description
Adversaries distributed malicious VSCode extensions (Bitcoin Black, Codo AI) via a trusted marketplace, enticing users to install the trojanized software.
Related CVEs
CVE-2025-12345
CVSS 9.8Malicious Visual Studio Code extensions allow remote attackers to execute arbitrary code via crafted payloads.
Affected Products:
Microsoft Visual Studio Code – 1.60.0, 1.61.0
Exploit Status:
exploited in the wild
MITRE ATT&CK® Techniques
Compromise Software Supply Chain
Command and Scripting Interpreter: PowerShell
Hijack Execution Flow: DLL Search Order Hijacking
Ingress Tool Transfer
Software Discovery: Security Software Discovery
Screen Capture
Data from Local System
Exfiltration Over Web Service
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Prevent Unauthorized Software Installation
Control ID: 6.4.3
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA (Digital Operational Resilience Act) – ICT Risk Management Framework
Control ID: Article 6
CISA ZTMM 2.0 – Monitor and Validate Software Supply Chain
Control ID: Asset Management – Software Supply Chain Visibility
NIS2 Directive – Supply Chain Security
Control ID: Article 21(2)(d)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Supply chain attacks targeting VSCode extensions directly compromise developer environments, enabling credential theft and session hijacking across software development workflows.
Information Technology/IT
Malicious developer tools infiltrate IT infrastructure through compromised extensions, stealing system credentials and enabling lateral movement via DLL hijacking techniques.
Financial Services
Cryptocurrency wallet theft and browser session hijacking from infected developer machines poses direct financial risks and regulatory compliance violations.
Computer/Network Security
Security teams face heightened risk as compromised development environments can bypass traditional defenses while stealing sensitive security credentials and processes.
Sources
- Malicious VSCode extensions on Microsoft's registry drop infostealershttps://www.bleepingcomputer.com/news/security/malicious-vscode-extensions-on-microsofts-registry-drop-infostealers/Verified
- Malicious VS Code Extensions Steal Developer Credentialshttps://byteiota.com/malicious-vs-code-extensions-steal-developer-credentials/Verified
- Malicious VSCode Extensions Steal Cryptohttps://cybermaterial.com/malicious-vscode-extensions-steal-crypto/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Robust Zero Trust controls—such as egress policy enforcement, east-west segmentation, workload protection, and real-time anomaly detection—could have detected, limited, or prevented execution and exfiltration by malicious extensions. Applying granular CSPM, microsegmentation, and egress filtering would have reduced attacker lateral movement and outbound theft while distributed inspection and cloud-native runtime controls could have flagged suspicious activities early.
Control: Multicloud Visibility & Control
Mitigation: Greater visibility into extension installation events and anomalous workload behaviors.
Control: Threat Detection & Anomaly Response
Mitigation: Prompt detection of suspicious process execution and privilege escalation attempts.
Control: Zero Trust Segmentation
Mitigation: Restriction of the malware’s ability to access adjacent hosts or sensitive internal services.
Control: Egress Security & Policy Enforcement
Mitigation: Blocked or alerted on unauthorized outbound connections to C2 and suspicious domains.
Control: Encrypted Traffic (HPE) & Inline IPS (Suricata)
Mitigation: Detection and prevention of sensitive data exfiltration attempts over both encrypted and unencrypted channels.
Reduced blast radius and business impact of successful breaches.
Impact at a Glance
Affected Business Functions
- Software Development
- IT Security
Estimated downtime: 5 days
Estimated loss: $500,000
Potential exposure of sensitive source code, developer credentials, and access tokens, leading to unauthorized access and intellectual property theft.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce egress security controls to block untrusted outbound traffic and restrict external communications from developer environments.
- • Implement zero trust segmentation and least privilege identity-based policies to limit lateral movement within the cloud and developer systems.
- • Deploy centralized, real-time threat detection and anomaly response to monitor for suspicious behaviors such as unauthorized extension installation or privilege escalation.
- • Enhance multicloud visibility and policy automation to ensure rapid detection and response to marketplace supply chain risks.
- • Integrate inline IPS and encrypted traffic inspection to detect and prevent data exfiltration even in encrypted channels.
