Grok build CLI was silently uploading entire private Git repositories (including unredacted secrets) to a Google Cloud bucket, transferring far more data than the coding task required.
Scott relays a security report showing Grok's build CLI was uploading whole private codebases—secrets included—to a Google Cloud bucket, with a 12GB test repo sending 5.1GB despite the task needing only 192KB, and no opt-in was ever required. ✦ AI generated
Scott Tolinski · Syntax · 2026-07-13 · original ↗
starts at this moment · 50:39
Grock build CLI was uploading entire Git repositories to a Google Cloud bucket. Private code bases, unredacted secrets included... On a 12 gigabyte test repo, 5.1 GB flew out the door to XAI's GR code session traces bucket while the actual coding task just needed 192 kilobytes.
verbatim transcript · starts at 50:39
50:39kilobytes. The tool grabbed whatever the repository it ran in, not only the files needed. The fix arrived as a hidden flag. Disable codebase upload equals true. A day after a researcher's wire level analysis, the improve the model opt out never stopped the uploads. Still advisory scope. No word on whether or not already uploaded code gets deleted for anybody pointing XAI. Um, my gosh, >> this is insane. There's This is like
51:11>> insane. >> There's what? Just stop using any Grock tool right now. Like the fact that that wasn't some kind of opt in or opt out. >> There's >> the fact that it's not opt in. Yeah, the fact that it's not opt in, that's crazy. Um, they they were I mean like they're just uploading whatever they can. Uh, they're just uploading everything. Um, this this, by the way, this comes in
51:37from International Cyber Digest. I found this Twitter account to be a really good follow if you're into um stuff that's going on in terms of cyber security. Int Cyber Digest. Really good follow here. Um, this thing has gotten some attention as you can see. Uh, definitely some attention here. And SpaceX AAI, which is the dumbest name, uh, SpaceX AAI Space XAI. Why can't like Okay, whatever. SpaceX AI has a statement. We
52:09care deeply about your privacy and respect customer choice. Oh, sorry, folks. I have a sandwich delivery. Thank you. Thank you, Courtney. Little sandwich and grapes. Uh, sorry about that, folks. Sandwich delivery. Uh, SpaceXi tweeted, "We care deeply about your privacy and respect customer choice." Oh, sure you do. That's why you're just hoovering up every single bit of thing that you can. For teams using zero data retention, no
52:37trace code and code data is ever retained. All API key use of Grock build also respects zero data retention. If zero data retention is disabled, the privacy command is available in the CLI to disable data retention, which also deletes previously synced data. Run privacy command to view or change your settings at any time. Come on. What I'm baffled by is just how blatant it is. Like literally just uploading
- ·Grok build CLI uploaded entire Git repos to Google Cloud
- ·Included unredacted secrets, not just code
- ·Sent to xAI's Grok code session traces bucket
- ·No opt-in was ever required
- ·Test repo was 12GB total
- ·Task only required 192KB of data
- ·Yet 5.1GB was uploaded anyway