GrokBuild Exposed for Leaking Repository Data

新智元 · wechat · 2026-07-14

GrokBuild Exposed for Uploading Repository Data

An independent security researcher discovered that despite its "local-first" marketing, xAI's AI coding agent GrokBuild actually uploads user repository contents to cloud storage buckets. Through honeypot repositories, fake keys, and packet capture replays, the researcher verified that even if only asked to reply with an OK and explicitly forbidden from opening files, it still uploaded the entire repository and its full modification history.

Key Findings

Impact & Aftermath

Following the report's release, the developer community panicked, with many rotating keys and uninstalling the tool overnight. xAI quietly halted the uploads, later introducing a /privacy command to allow disabling retention and deleting previously uploaded data; Elon Musk himself acknowledged the incident and pledged to purge historical user data.

The core risk of this incident lies in the fact that AI coding agents often possess elevated permissions to read files, modify code, and execute commands. If they overstep their bounds, the leakage isn't just code—it could expose SSH keys, database passwords, and sensitive information across the entire machine.

Related event: Grok Build/CLI accused of silently uploading entire codebases; xAI promises to delete data(47 posts)→

Original post →

More from coding & agent

coding & agent channel →