OOF-AII-719717

Z.ai's ZCode AI Coding Assistant Reportedly Uploaded Developers' Local Code Repositories to Alibaba Cloud Without Consent

Developers reported that Z.ai's ZCode AI coding assistant uploaded local code repositories to Alibaba Cloud without consent. Z.ai said a default-enabled Codebase Indexing feature caused the behavior, apologized, patched the vulnerability, and later disabled the upload path. One company retracted a separate claim that six workspaces containing sensitive data had been uploaded; Z.ai said independent reviews found no code data retained.

Event date
2026-09-18
Country
Location not specified
Severity
Moderate
Evidence state
Single-source

Assessment status

Generated from available public incident evidence using OOF® governance methodology. It is not an official investigation, legal determination, regulatory finding, certification, or OOF® Approved Assessment.

View source record from AI Incident Database (Responsible AI Collaborative)

Assessment confidence dimensions

Source corroboration
Single-source

Measures source-group corroboration only; it does not establish factual truth.

Extraction completeness
Moderate

Measures populated source fields after deterministic normalization; it does not measure correctness.

Methodological assignment confidence
Limited

Measures automated assignment support; substantive correctness requires authorized human review.

Known facts from the incident record

  • The incident record identifies the event date as 2026-09-18.

Reported claims

  • Developers reported that Z.ai's ZCode AI coding assistant uploaded local code repositories to Alibaba Cloud without consent. Z.ai said a default-enabled Codebase Indexing feature caused the behavior, apologized, patched the vulnerability, and later disabled the upload path. One company retracted a separate claim that six workspaces containing sensitive data had been uploaded; Z.ai said independent reviews found no code data retained.

Material unknowns

  • Independent corroboration is not established in the available incident record.

Primary governance problem

The incident appears to expose a governance problem involving been, later. Available reporting supports preliminary methodological interpretation, not a finding of fault or non-compliance.

Architecture intelligence

LIGA™ — Liability Governance Architecture

Primary architecture

The reported been, later concern falls within the governed questions represented by LIGA™ — Liability Governance Architecture.

Governance focus: How should been, later be governed in the conditions described by the available incident evidence?

Deeper methodology is withheld because the available evidence does not justify a Parent Standard or Core Module.

Preliminary governance questions

  • How should been, later be governed in the conditions described by the available incident evidence?
  • What operational authority and controls applied to Z.Ai, Ai Service Providers at the relevant time?
  • What evidence would establish how Zcode Ai Coding Assistant, Ai Code Generation Systems, Zcode Codebase Indexing Feature, Enterprise Ai Systems produced or enabled the reported outcome?
  • What additional independent evidence is required to resolve the material evidence gaps?

Evidence gaps and limitations

  • Only one independent source group is represented; corroboration is not established.
  • Country could not be resolved from the available evidence.
  • AI technology is not specified in the source record.
  • industry is not specified in the source record.
  • AI system type is not specified in the source record.

Return to the public incident index