Executive Summary

In January 2026, security researchers uncovered that two AI coding assistant extensions, 'ChatGPT - 中文版' and 'ChatMoss (CodeMoss)', available on the Visual Studio Code Marketplace, were surreptitiously exfiltrating developers' source code to servers in China. These extensions, collectively installed by approximately 1.5 million users, functioned as advertised but secretly transmitted entire file contents and user data without consent. The campaign, dubbed 'MaliciousCorgi', exploited the trust developers place in marketplace extensions, leading to significant exposure of proprietary code and sensitive information.

This incident underscores the escalating risks associated with supply chain attacks targeting developer tools. The widespread adoption of AI-powered extensions, combined with insufficient vetting processes in extension marketplaces, has created a fertile ground for malicious actors. Organizations must prioritize stringent security assessments of third-party tools to safeguard intellectual property and maintain operational integrity.

Why This Matters Now

The 'MaliciousCorgi' campaign highlights the urgent need for enhanced security measures in software development environments. As AI coding assistants become integral to development workflows, their potential misuse poses significant threats to data security and intellectual property. Immediate action is required to implement robust vetting processes and educate developers on the risks associated with third-party extensions.

Attack Path Analysis

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

The campaign revealed significant gaps in the vetting processes of extension marketplaces, leading to unauthorized data exfiltration and potential violations of data protection regulations.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Aviatrix Zero Trust CNSF is pertinent to this incident as it could have limited the malicious extensions' ability to escalate privileges, move laterally, and exfiltrate sensitive data, thereby reducing the overall impact of the attack.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: The malicious extensions' ability to establish unauthorized connections may have been constrained, reducing the risk of initial compromise.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: The extensions' ability to access sensitive code repositories and developer credentials would likely have been constrained, reducing the scope of privilege escalation.

Lateral Movement

Control: East-West Traffic Security

Mitigation: The extensions' ability to propagate across systems and access multiple codebases would likely have been constrained, reducing the scope of lateral movement.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: The extensions' ability to establish covert channels to external servers would likely have been constrained, reducing the risk of unauthorized data transmission.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: The extensions' ability to exfiltrate sensitive code to external servers would likely have been constrained, reducing the risk of data loss.

Impact (Mitigations)

The overall impact of the attack would likely have been reduced, limiting data breaches and protecting the software supply chain.

Impact at a Glance

Affected Business Functions

  • Software Development
  • Intellectual Property Management
  • Data Security
Operational Disruption

Estimated downtime: N/A

Financial Impact

Estimated loss: N/A

Data Exposure

Potential exposure of proprietary source code and intellectual property from approximately 1.5 million developers.

Recommended Actions

  • • Implement Zero Trust Segmentation to restrict unauthorized access within development environments.
  • • Enforce Egress Security & Policy Enforcement to monitor and control outbound traffic from development tools.
  • • Utilize Threat Detection & Anomaly Response systems to identify and respond to unusual activities within development workflows.
  • • Apply Inline IPS (Suricata) to detect and prevent known exploit patterns and malicious payloads.
  • • Regularly audit and validate third-party extensions and tools to ensure they do not introduce security vulnerabilities.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Get a Free Workload Attack Path AssessmentUnder Active Attack?
Cta pattren Image