Likelihood: MODERATE
Impact: HIGH
Treatment: MITIGATE
Confidence: Moderate
Six of 73 extensions are confirmed actively delivering malware, establishing real-world exploitation rather than theoretical risk; however, organizational exposure depends on whether developers have installed any of the 73 identified extensions, making likelihood moderate until inventory is assessed. Impact is high because a single compromised developer workstation can yield source code, cloud credentials, and deployment secrets — enabling lateral movement into production infrastructure well beyond the initial endpoint.
Treatment rationale: Active credential-theft malware in developer toolchains represents an unacceptable residual risk that cannot be transferred or accepted without first removing the malicious extensions, revoking exposed secrets, and hardening extension-installation controls.
Third-Party / Supply-Chain Risk
The OpenVSX Registry and Visual Studio Code Marketplace are shared third-party distribution platforms whose extension-vetting processes were bypassed by GlassWorm's deferred-payload technique; any organization that delegates trust to these registries without independent verification inherits this supply-chain exposure. The npm ecosystem is additionally implicated, meaning CI/CD pipelines pulling packages from npm are a downstream vector — organizations should treat OpenVSX, VS Marketplace, and npm as untrusted third-party suppliers for the duration of this campaign (NIST SP 800-161 Tier 3 supplier risk).
Loss Exposure (illustrative)
Magnitude: High — illustrative $500K–$5M per incident, driven by secret-exposure scenarios that enable downstream production or customer-data compromise rather than the initial endpoint loss alone
Frequency: For an organization with an unaudited developer population actively using VS Code or Open VSX-compatible IDEs and no extension-allowlisting controls, an illustrative frequency of 1 material event per 2–4 years reflects the confirmed active delivery status of six extensions and the breadth of the targeted developer toolchain
Annualized: Illustrative ALE: $125K–$2.5M annually for an exposed organization, representing loss magnitude spread across the illustrative frequency range
Basis: Magnitude is anchored on the attack path, not a cited report: a stolen cloud credential or CI/CD secret in a production-connected developer environment creates a plausible breach scenario with incident response, credential rotation, code audit, and potential customer-notification costs. The lower bound reflects a contained workstation compromise; the upper bound reflects a scenario where stolen credentials enable unauthorized production access requiring customer notification and regulatory response. Frequency reflects confirmed active exploitation of six extensions within a population of 73, the broad install surface of VS Code across developer teams, and the absence of confirmed KEV status (which suppresses frequency relative to a weaponized-at-scale campaign).
Illustrative estimate — not actuarially derived.
Insurance / Contractual / Legal — Potential Obligations
Potential triggers, not legal determinations. Verify with counsel/broker before acting.
• Confirmed credential theft and potential access to customer data or PII may invoke state and federal breach-notification obligations — verify with counsel.
• Cloud credential and production infrastructure exposure may trigger cyber-insurance notice obligations under your policy's 'security event' or 'computer fraud' provisions — verify with broker.
• If developer workstations accessed customer data or regulated environments (PCI-DSS, HIPAA, SOC 2), those contractual and regulatory notification clauses may be implicated — verify with counsel.
