Grok Build’s disaster shows why it trails behind ChatGPT, Claude, Gemini
Follow Us
Musk would have you continue to feed Grok Build your code, which is really what I am concerned about regarding this week’s screw-up rather than the breach per se. The story starts with a security researcher who goes by the name of Cereblab, who used a proxy to route the coding CLI of xAI and discovered that whereas the actual channel of the tool transmitted a moderate 192 KB to complete a coding mission, there was another channel through which entire repositories were being sent to a Google Cloud Storage bucket – with their entire Git history – amounting to 5.1 gigabytes on one test repository alone, in dozens of chunks, which is some 27,800 times more data than the job required. Other users mentioned the tool accessing SSH keys and password managers.
SurveyTo xAI’s credit, once this report went live, the uploads ceased. Indeed, Cereblab confirmed that flipping the server-side flag called disable_codebase_upload was enough for stopping the whole-repo transfer. This is a fix rather than a PR stunt. However, everything surrounding the fix paints a clear picture as to why Grok always ends up fourth in a race of three.
Also read: OpenAI’s first hardware device: Why not a wearable speaker tied to a necklace?
One should start with the toggle that turned out not to work as intended despite the instruction received by the users. According to xAI staff, the /privacy toggle was the element that stopped leaking the information from the application. However, there was another option that actually managed to halt this process – an undocumented global flag which was unknown to the users. It does not mean that this communication tactic was used as an alternative for an engineering solution to the problem.
Another example is xAI’s response to the situation. In spite of the fact that researchers had found out that developers’ codebases and secrets were not secure, the company did not publish any security advisory on the topic yet. There were neither deadlines nor verification methods, as well as any information on the scale of the problem, the number of affected users, or the time needed for the solution. Instead, one can find several threads where company employees reassure about the safety of the application and the promise made by Elon Musk on X that everything would be “completely and utterly deleted.”
Also read: 200 economists say AI threatens jobs but no one has a plan to fix it
Then there’s Musk, who somehow managed to make this worse in real-time too. Even as Musk later confirmed that all of the previously uploaded user data will be purged, he further went on to justify that holding onto “some” data was useful for debugging purposes, in effect asking users to continue to trust a tool that had been found out to do the opposite of what it said it would do. This is not security, but negotiation. It’s also completely characteristic of how Musk behaves in his typical way when making promises and delivering through Full Self-Driving, the Hyperloop and the timelines of Mars.
This doesn’t mean that Grok Build does not have the technical know-how. The issue is one of trust, which is exactly what determines whether developers and companies even give their coding agent access to their private repos to begin with. Claude Code, Gemini, and Codex apparently read individual files and not whole code bases, which is a lower bar compared to “stop leaking secrets,” and even xAI required a public researcher and a Twitter thread to get there.
Shipping fast and fighting loud might work for X. For a coding tool that needs enterprises to trust it with their actual source code, it’s a losing strategy, and this week is a pretty good explanation of why xAI keeps losing.
Also read: Best 16-inch laptops in 2026 for work, gaming and entertainment
