Likelihood: HIGH
Impact: VERY HIGH
Treatment: MITIGATE
Confidence: Moderate
Likelihood is high because the affected ecosystems (VS Code Marketplace, npm, GitHub) are default tooling for most development teams, the threat actors have demonstrated sustained reconstitution after takedowns, and the campaign is actively yielding confirmed financial losses at scale in Q1 2026 — meaning exploitation is not theoretical but ongoing across the sector. Impact is very_high because a compromised developer workstation sits at the trust boundary of source code, cloud credentials, and CI/CD pipelines, meaning a single malicious extension can propagate attacker access laterally into every downstream system and customer environment the developer touches, combining direct cryptocurrency theft with IP exfiltration and potential supply-chain injection into the organization's own software.
Treatment rationale: The attack surface — developer toolchains, open registries, and IDE extensions — cannot be avoided without halting software development, and the financial and reputational blast radius of a CI/CD or source-code compromise is too severe to accept; active controls (extension vetting, registry allowlisting, endpoint detection on developer workstations, CI/CD integrity verification) materially reduce exposure without operational paralysis.
Third-Party / Supply-Chain Risk
Exposure is structurally third-party and supply-chain in nature per NIST SP 800-161: the malicious payloads are delivered through Microsoft-operated (VS Code Marketplace), npm-operated (npmjs.com), and GitHub-operated registries that organizations do not control, meaning the organization's vendor-risk posture toward these platform providers directly governs whether malicious packages reach developer workstations. Any organization with transitive npm dependencies or that permits open-marketplace extension installation inherits the registry's vetting risk. The GitHub Actions and Packagist exposures extend this to build-pipeline and PHP-ecosystem dependencies. Organizations relying on shared developer platforms or consuming open-source packages without a private registry proxy or software composition analysis gate have no first-party control at the point of introduction.
Loss Exposure (illustrative)
Magnitude: high — illustrative $500K–$5M per affected organization depending on developer footprint, CI/CD integration depth, and whether credential compromise propagates to cloud infrastructure
Frequency: Organizations with 10+ developers consuming open npm registries or open VS Code Marketplace without registry controls face an illustrative annualized event probability in the range of 1-in-5 to 1-in-3, given confirmed active campaign scale (26,584 wallets, $12M+ sector losses in a single quarter)
Annualized: Illustrative ALE: $150K–$1.5M annually for a mid-size development organization, skewed upward if CI/CD or cloud credential compromise materializes; the $500K single-incident loss from the Cursor IDE case anchors the lower bound of a material event
Basis: Lower bound anchored by the confirmed $500K single-extension incident described in the item. Upper range reflects escalation path: developer credential → cloud infrastructure access → IP exfiltration or customer-environment compromise, which for a software company or SaaS provider represents a materially higher loss magnitude than the initial cryptocurrency theft. Frequency derived from the campaign's confirmed, ongoing, industrial-scale reconstitution behavior and the breadth of affected registries — not from any external report or survey. All figures are illustrative and order-of-magnitude only.
Illustrative estimate — not actuarially derived.
Insurance / Contractual / Legal — Potential Obligations
Potential triggers, not legal determinations. Verify with counsel/broker before acting.
• Confirmed cryptocurrency theft from developer workstations may constitute a direct financial loss event under a cyber or crime policy — verify coverage applicability and notice obligations with broker before an incident occurs.
• If compromised developer credentials resulted in unauthorized access to customer data or customer-facing systems, PII or sensitive data exposure may invoke state and federal breach-notification obligations — verify with counsel.
• CI/CD pipeline compromise resulting in malicious code reaching a customer's production environment could trigger contractual breach, SLA, or indemnification clauses in software development or SaaS agreements — verify with counsel.
• Supply-chain compromise of internally developed software distributed to customers may invoke software liability or vendor security addendum obligations — verify with counsel and review existing customer contracts.