SourceThe Next Web (TNW)•Freshcollected in 12h
ZCode’s Encrypted Upload Raises Deletion Concerns
#data-privacy#workspace-upload#code-securityzcodez.aizcodealibaba cloudferstar
Encrypted workspace uploads expose a hard problem: proving your code was actually deleted.
30-Second TL;DR
What Changed
A 313MB encrypted archive was reportedly found in ZCode’s local directory.
Why It Matters
This raises data-governance concerns for coding assistants that upload workspaces, especially in proprietary or regulated environments. Transparent upload controls, retention policies, and verifiable deletion are essential for enterprise adoption.
What To Do Next
Disable workspace uploads in ZCode and inspect network traffic and local caches before using it with proprietary repositories.
Who should care:Enterprise & Security Teams
Key Points
- •A 313MB encrypted archive was reportedly found in ZCode’s local directory.
- •The archive had reportedly failed to upload 564 times to Alibaba Cloud.
- •Exclusive decryption by Z.ai complicates independent verification of deletion.
Deep Insight
Background and context from public sources — not the original article. 13 sources cited.
Enhanced Key Takeaways
- •Security researcher ferstar exposed the issue on September 18, 2026, after observing the local
~/.zcodedirectory swell beyond 700MB with automated background upload jobs. - •The bundled payload captured entire local Git repositories—including complete
.githistory, reflogs, and revisions accounting for over 86% of the snapshot—exposing historical secrets and internal hostnames. - •Reverse engineering of the Electron client's
app.asarbundle revealed direct HTTP POST uploads to Alibaba Cloud Object Storage Service (OSS) via dynamic credentials, bypassing Zhipu's intermediate application tier. - •Z.ai attributed the behavior to default-enabled 'repository indexing' and 'Repo Wiki' documentation tools, pledging to open-source the client and grant quota resets to appease users.
- •On September 20, 2026, Taiyuan Chengming Technology served Beijing Zhipu Huazhang with a formal legal demand after detecting continued background uploads in version 3.12.3.
Competitor Analysis
ZCode
- Provider
- Z.ai (Zhipu AI)
- Data Ingestion & Workspace Telemetry
- Automatic, default-on uploads of entire Git trees (including
.githistories) to cloud storage - Decryption & Auditability
- Client-side envelope encryption with private keys held exclusively on server
- Verification & Remediation Stance
- Unverifiable backend deletion; pledged open-source audit amidst enterprise bans and legal action
Grok Build
- Provider
- xAI
- Data Ingestion & Workspace Telemetry
- Background telemetry and interaction tracking
- Decryption & Auditability
- Standard inspectable client-to-cloud transport
- Verification & Remediation Stance
- Permitted independent third-party retesting to verify cessation of background uploads
Claude Code
- Provider
- Anthropic
- Data Ingestion & Workspace Telemetry
- Local terminal-based execution; subject to external prompt-injection attack vectors
- Decryption & Auditability
- Direct API transport with platform logging controls
- Verification & Remediation Stance
- Governed by enterprise zero-data-retention and standard API audit terms
| Coding Assistant | Provider | Data Ingestion & Workspace Telemetry | Decryption & Auditability | Verification & Remediation Stance |
|---|---|---|---|---|
| ZCode | Z.ai (Zhipu AI) | Automatic, default-on uploads of entire Git trees (including .git histories) to cloud storage | Client-side envelope encryption with private keys held exclusively on server | Unverifiable backend deletion; pledged open-source audit amidst enterprise bans and legal action |
| Grok Build | xAI | Background telemetry and interaction tracking | Standard inspectable client-to-cloud transport | Permitted independent third-party retesting to verify cessation of background uploads |
| Claude Code | Anthropic | Local terminal-based execution; subject to external prompt-injection attack vectors | Direct API transport with platform logging controls | Governed by enterprise zero-data-retention and standard API audit terms |
Technical Deep Dive
- Local Storage Footprint: Local directory
~/.zcodeballooned past 700MB, packaging uncompressed workspace data into an automated 313MB.encpayload. - Exfiltration Composition: Over 86% of the archive comprised
.gitdirectory trees, capturing complete commit histories, reflogs, and historical credential revisions rather than just active workspace files. - Cryptographic Bottleneck: Utilized client-side envelope encryption where the private decryption key was retained exclusively on Zhipu's backend, rendering payload contents opaque to local developers.
- Upload Mechanism: The client's Electron
app.asararchive acquired dynamic temporary authorization tokens to stream archives straight to Alibaba Cloud Object Storage Service (Aliyun OSS) via HTTP POST, bypassing primary application servers.
Future ImplicationsAI analysis grounded in cited sources
Enterprise adoption of Chinese proprietary coding clients will drop in favor of self-hosted solutions
Silent exfiltration of sensitive Git histories has triggered internal enterprise bans across security-sensitive industries.
Coding assistants will be forced to implement verifiable client-side zero-knowledge audits
Unilateral vendor assertions of data destruction without cryptographic user verification are no longer legally or technically sufficient for enterprise compliance.
Timeline
2026-09
Researcher ferstar uncovers automated 313MB encrypted workspace upload attempts in ZCode client
2026-09
Z.ai apologizes, cites Repo Wiki indexing, and pledges to open-source the ZCode client
2026-09
Taiyuan Chengming Technology issues formal legal notice to Zhipu over persistent uploads in v3.12.3
- 2026-09Researcher ferstar uncovers automated 313MB encrypted workspace upload attempts in ZCode client
- 2026-09Z.ai apologizes, cites Repo Wiki indexing, and pledges to open-source the ZCode client
- 2026-09Taiyuan Chengming Technology issues formal legal notice to Zhipu over persistent uploads in v3.12.3
Sources (13)
Factual claims are grounded in the sources below. Forward-looking analysis is AI-generated interpretation.
1An AI Coding App Was Silently Uploading Your Entire Git History Inside the Zcode Incident 54e0f5047541medium.com2Chinese AI Firm Zai Faces Reputation Hit After Users Spot Unauthorised Uploadsscmp.com3Zai Zcode Encrypted Upload Only Zai Can Verifythenextweb.com4biggo.comfinance.biggo.com5Zcode Is Now Open Sourcereddit.com6Z AI Encrypted the Workspace It Uploaded So That Only Z AI Could Open It Now Only Z AI Can Say It W X49pcvagudaily.dev7An AI Coding App Was Silently Uploading Your Entire Git History Inside the Zcode Incident 54e0f5047541medium.com81416973 Zcode Tried Uploading Your Files 564 Times Researcher Findsthenews.com.pk9Ncf34556a31d9note.com10ycombinator.comnews.ycombinator.com11biggo.comfinance.biggo.com12368539392115557binance.com13Z AI Encrypted the Workspace It Uploaded So That Only Z AI Could Open It Now Only Z AI Can Say It W X49pcvagudaily.dev
Weekly AI Recap
Read this week's curated digest of top AI events →
Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: The Next Web (TNW) ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
The weekly digest
One email a week. Unsubscribe anytime.