conv.

All stories
SecurityQuiet 4d · day 6

Developer reveals ZCode silently uploads encrypted Git history to Z.ai's cloud

A reverse-engineering analysis shows Zhipu's AI coding app packages and encrypts entire workspaces—including deleted code and API keys—without user control.

What to know

  • ZCode, Zhipu's official AI coding app, automatically uploads entire Git repositories—including deleted code, API keys, and branch metadata—to Alibaba Cloud whenever the user is logged in.
  • The uploads are encrypted with a private key held only by Z.ai's servers, meaning users cannot decrypt the 300MB+ archives stored on their own disks.
  • The upload pipeline runs automatically with no user-facing toggle or privacy setting to disable it.
  • The finding triggered rapid spread across English and Chinese developer communities, with security researchers warning against closed-source AI coding tools.
most voices

Closed-source AI coding tools pose unacceptable security and privacy risks; users should switch to open-source alternatives.

some voices

Confusion between open-weight models and proprietary applications; users incorrectly assumed ZCode was open source because GLM is.

ferstar Security researcherZ.ai (Zhipu) Developer of ZCode and GLM modelsPetri Kuittinen Open-source AI agent developerFeiZ Chinese developer/community member

Developer reveals ZCode silently uploads encrypted Git history to Z.ai's cloud
tokenstead.ai

How it unfolded 2 developments, newest first · click a bar or a number to jump articlesposts

Peak 5 pieces in two hours at Sep 18, 5 AM; 26 pieces over 6 days (4 articles · 8 posts · 14 comments) Sep 18, 1 AM — 4 pieces · 2 articles · 1 post · 1 comment — Newswires 2, Hacker News 2Sep 18, 3 AM — 1 piece · 1 comment — Hacker News 1Sep 18, 5 AM — 5 pieces · 2 articles · 2 posts · 1 comment — Newswires 2, Hacker News 2, Mastodon 1Sep 18, 7 AM — 3 pieces · 3 comments — Hacker News 3Sep 18, 9 AM — 3 pieces · 1 post · 2 comments — Hacker News 2, Mastodon 1Sep 18, 11 AM — 3 pieces · 1 post · 2 comments — Hacker News 2, Mastodon 1Sep 18, 1 PM — 2 pieces · 1 post · 1 comment — Hacker News 1, Mastodon 1Sep 18, 3 PM — 1 piece · 1 comment — Hacker News 1Sep 18, 5 PM — quietSep 18, 7 PM — 1 piece · 1 comment — Hacker News 1Sep 18, 9 PM — 1 piece · 1 post — Mastodon 1Sep 18, 11 PM — quietSep 19, 1 AM — quietSep 19, 3 AM — quietSep 19, 5 AM — quietSep 19, 7 AM — quietSep 19, 9 AM — quietSep 19, 11 AM — quietSep 19, 1 PM — quietSep 19, 3 PM — quietSep 19, 5 PM — 1 piece · 1 comment — Hacker News 1Sep 19, 7 PM — quietSep 19, 9 PM — quietSep 19, 11 PM — quietSep 20, 1 AM — quietSep 20, 3 AM — quietSep 20, 5 AM — quietSep 20, 7 AM — quietSep 20, 9 AM — quietSep 20, 11 AM — quietSep 20, 1 PM — quietSep 20, 3 PM — quietSep 20, 5 PM — quietSep 20, 7 PM — 1 piece · 1 post — Hacker News 1Sep 20, 9 PM — quietSep 20, 11 PM — quietSep 21, 1 AM — quietSep 21, 3 AM — quietSep 21, 5 AM — quietSep 21, 7 AM — quietSep 21, 9 AM — quietSep 21, 11 AM — quietSep 21, 1 PM — quietSep 21, 3 PM — quietSep 21, 5 PM — quietSep 21, 7 PM — quietSep 21, 9 PM — quietSep 21, 11 PM — quietSep 22, 1 AM — quietSep 22, 3 AM — quietSep 22, 5 AM — quietSep 22, 7 AM — quietSep 22, 9 AM — quietSep 22, 11 AM — quietSep 22, 1 PM — quietSep 22, 3 PM — quietSep 22, 5 PM — quietSep 22, 7 PM — quietSep 22, 9 PM — quietSep 22, 11 PM — quietYesterday, 1 AM — quietYesterday, 3 AM — quietYesterday, 5 AM — quietYesterday, 7 AM — quietYesterday, 9 AM — quietYesterday, 11 AM — quietYesterday, 1 PM — quietYesterday, 3 PM — quietYesterday, 5 PM — quietYesterday, 7 PM — quietYesterday, 9 PM — quietYesterday, 11 PM — quietToday, 1 AM — quietToday, 3 AM — quietToday, 5 AM — quietToday, 7 AM — quietToday, 9 AM — quiet 1–2
Sep 19Sep 20Sep 21Sep 22yesterdaynow · 11:54 AM ET
  1. 2

    Story spreads to 276,000+ views; security researcher issues warning

    Ferstar's original post reached 276,000 views within hours. A Chinese-language alert thread by FeiZ drew 63,800 views. Petri Kuittinen, developer of an open-source AI agent, issued a widely quoted warning against closed-source AI tools.

    “My advice has been and continues to be: do NOT trust closed source AI harnesses.”
    — Petri Kuittinen
    • technotenshi@infosec.exchange

      Researcher ferstar reverse engineered ZCode, the closed-source AI coding desktop app from Z.ai (maker of the GLM model family), and found that while a user is logged in it silently packages their entire workspace, including full Git history, LFS cache, and reflogs, encrypts it, and uploads it to Aliyun OSS. The archive uses envelope encryption in…

      technotenshi@infosec.exchangeMastodon5d ago1▲view on Mastodon ↗
    2 more of the top 3 · 14 posts in this stretch
    • I was wondering if I should try to create my own pseudo filesystem with FUSE for easy copy-on-write/snapshots, a native feel, and automated secrets filtering/swapping. I might as well combine that with good/easy isolation.The whole “what sandbox/VM/microVM/thing is best?” question has been bugging me a lot lately, and I no longer trust any of…

      radio879Hacker News4d agoview on Hacker News ↗
    • z.ai made a statement, screenshotted in this article: https://finance.sina.com.cn/tech/roll/2026-09-18/doc-inisfye...claude translation:Dear ZCode users,We take today's community discussion very seriously. We carried out an internal review right away, and we first want to apologize to the affected users. Here is an explanation of what happened:The…

      acrispinoHacker News5d agoview on Hacker News ↗
    all of them →
  2. 1

    Upload pipeline runs automatically with no user-facing toggle

    The capture/upload sidecar is instantiated unconditionally at startup whenever the user is logged in. There are no UI settings to disable it—the only requirement is a valid JWT from the tokenProvider. Capture triggers occur before every prompt and on task completion, with a single session generating up to 62 capture events.

    “A key that only the server can use serves exactly one purpose: making sure the server can read your code whenever it wants.”
    — ferstar, Security researcher · source
    • They learned nothing from the Grok Code saga.If anything, that should have been a learning lesson to NOT trust harnesses, especially new ones.

      denysvitaliHacker News6d agoview on Hacker News ↗
  3. background

    Uploads capture complete Git history, not just current working files — The encrypted archives contain the full lineage of repositories since day one, including deleted-in-later-commits API keys, unpushed branch names revealing unreleased product plans, and internal hostnames from .git/config. The .git directory comprises 86.6% of the 313MB encrypted archive from a 42,411-file snapshot.

  4. background

    ZCode uses server-held encryption keys that users cannot decrypt — The app uses envelope encryption: the payload is encrypted with AES-256-CTR, and the symmetric key is wrapped with an RSA-OAEP public key delivered by Z.ai's servers. The private key lives only in Z.ai's cloud. Ferstar confirmed that the 313MB ciphertext on disk cannot be decrypted by the user or the ZCode client itself.

  5. background

    Ferstar publishes reverse-engineering analysis of ZCode's upload pipeline — Researcher ferstar discovered that ZCode automatically packages and encrypts the entire workspace—including .git history, LFS asset cache, reflogs, and global configs—and uploads it to Aliyun OSS. The researcher found a 313MB encrypted archive and reconstructed the full upload flow by examining the app.asar client bundle.

Also covered reported alongside — the timeline has no entry for these yet

  1. first by HN Best, 6d ago · also HN Frontpage

  2. first by HN Best, 6d ago · also HN Frontpage

What people are saying 11 voices from 1 site · best of 15 · verbatim