CASE · Critical · credential-leak
Unverified reportCollected from public reportsA coding assistant uploaded whole local repositories to the cloud by default (unverified report)
According to press reports, Z.ai's ZCode coding assistant was copying entire local repositories, Git history included, to a cloud storage bucket in the background. The feature was on by default and had no clear off switch.
2 min read
- OBSERVED
- CATEGORY
- credential-leak
- BLAST RADIUS
- data, reputation
- DETECTED BY
- third-party-researcher
- TAGS
- #z-ai #zcode #data-exfiltration #default-on #privacy #cloud-upload
CH 1
Cause
According to Z.ai, the cause was a "Codebase Indexing" feature that was enabled by default. Developers wrote that it had no off switch and was not mentioned in the privacy policy, and the uploads were encrypted with a key only the vendor held, so users had no way to check what had been stored.
CH 2
Consequence
One company said source code, database passwords and employee personal data had been uploaded, then retracted the claim, citing wrong evidence. Z.ai apologized, disabled the feature and deleted the bucket; the episode became a trust problem for enterprise use. These are reported claims, not independently confirmed here.
CH 3
Fix
The vendor removed the upload path, shipped ZCode 3.14.0, open-sourced the assistant and commissioned audits; a security firm and a state-affiliated standards body said the stored data had been deleted. For operators: treat every AI coding tool as a possible outbound data path. Check what indexing or sync features do by default, watch background processes' disk and network use, and keep secrets out of the working tree.
What happened
In September 2026, a Chinese developer who goes by Ferstar noticed ZCode, the coding assistant from Z.ai (also known as Zhipu), using far more disk than expected and traced it to a background process. By Ferstar's account, the assistant was packaging whole local repositories, including .git history, reflogs and cached large files, and sending them to an Alibaba Cloud storage bucket.
The chaos on the ground
According to Reuters, Chinese developers began reporting the same thing on social media in the week before September 21. One company said source code, database passwords and employees' personal information had been uploaded, then retracted the statement, saying it had "wrong evidence".
Users said the data was encrypted with a key only Z.ai held, so they could neither open their own files nor confirm deletion. Z.ai apologized on Friday, September 18, and on Monday, September 21, said it had disabled the feature.
Root cause
According to Z.ai, the uploads came from a "Codebase Indexing" feature that was enabled by default. Developers wrote that there was no toggle to turn it off and no prior mention of it in the privacy policy. Nothing in the tool's normal use told the developer that their repository was leaving the machine.
The fix
Z.ai removed the upload mechanism and the Repo Wiki generation workflow, deleted the storage bucket, released ZCode 3.14.0, published the assistant's source code, and had the cleanup checked by the security firm NSFOCUS and a standards body affiliated with China's industry ministry, which confirmed the data had been deleted. The company says the data was never used for model training.
The lesson for anyone running coding agents is broader than one vendor: an assistant that can read your repository can also send it somewhere. Before rolling a tool out, find out what its indexing, sync or "memory" features do by default, watch what its background processes write and send, and keep credentials out of the working tree so an upload like this has less to take.
Sources
- InfoWorld: Z.ai disables coding assistant feature after flaw exposed enterprise code upload risk(opens in a new tab)
- Reuters (via Yahoo): China's Z.ai disables AI coding assistant features after security issue(opens in a new tab)
- Blog post by the independent developer Ferstar, who first reported the uploads (September 2026)
Pass this record on to your team