
Grok Build Uploaded Your Entire Codebase — Without Asking
Grok Build reportedly uploaded entire Git repositories—including files it never opened, full Git history, and deleted secrets—to xAI-controlled cloud storage.
In this episode of Legitimate Cybersecurity, Frank Downs and Dr. Dustin Brewer unpack what that means for anyone allowing an AI coding agent inside a real computer.
Independent researcher CerebLab captured Grok Build packaging a complete repository into a Git bundle and sending it to cloud storage after being explicitly told not to read any files. Turning off “Improve the model” did not stop the transfer in the researcher’s test.
That does not prove xAI trained on the code. It exposes a different problem: “don’t train,” “don’t transmit,” and “don’t retain” are three very different promises.
Frank and Dustin discuss:
• Why deleted passwords and API keys can survive in Git history
• How AI coding agents gain broad access to your computer
• Why developers keep treating security as something to add later
• The difference between a breach, a leak, and a breach of trust
• Why old code can be more dangerous than current code
• What developers should do now: rotate secrets, isolate projects, restrict permissions, and monitor unexpected outbound data
IMPORTANT UPDATE: CerebLab reports that whole-repository uploads later stopped after xAI enabled a server-side control. SpaceXAI also promised to delete previously retained coding data and subsequently open-sourced Grok Build. This episode examines the documented behavior before that change—and the trust problem it exposed.
Research and updates:
Media/interview: mailto:[email protected]
Audio podcast: https://legitimatecybersecurity.podbean.com/
CHAPTERS
00:00 — Grok Build reportedly uploaded whole repositories
01:20 — Why Git repositories are a gold mine
03:19 — Breach, leak, or breach of trust?
04:23 — What AI coding agents actually do
05:20 — Why old code still matters
08:56 — Deleted passwords can survive in Git history
10:41 — “Don’t train” vs. “don’t retain”
12:30 — When an AI codes its own connector badly
14:30 — What affected developers should do now
16:38 — AI agents are becoming highly privileged
19:31 — What system-level AI access can destroy
21:26 — The network anomaly that exposed the upload
22:19 — When bandwidth becomes a security signal
23:43 — Patch quickly—without becoming CrowdStrike
24:34 — The practical takeaway
#Grok #GrokBuild #Cybersecurity #DataPrivacy #AICoding #VibeCoding #AIAgents #xAI #GitSecurity #SourceCode #ArtificialIntelligence #LegitimateCybersecurity
Otros episodios de "Legitimate Cybersecurity Podcasts"



No te pierdas ningún episodio de “Legitimate Cybersecurity Podcasts”. Síguelo en la aplicación gratuita de GetPodcast.








