Musk pledges full data purge after Grok Build caught uploading user repos

Security researchers discovered that xAI's Grok Build coding assistant was quietly uploading users' entire Git repositories — including sensitive credentials — to cloud storage, prompting Elon Musk to pledge a full data purge.

What Researchers Found

Cereblab, an independent research group, published a wire-level analysis on July 12 showing that Grok Build CLI version 0.2.93 was transmitting complete Git repositories, including full commit histories, to a Google Cloud Storage Alphabet Inc. ↗ 0.87% bucket operated by xAI — regardless of which files the coding agent actually needed for a given task. The uploads occurred independently of per-file read permissions, meaning that even files a user explicitly told the agent not to access, such as .env files containing API keys and database passwords, were bundled and sent to xAI's servers.reddit+3

One researcher recovered a file from the uploaded Git bundle that Grok had been specifically instructed not to read, demonstrating that the opt-out toggle within the product did not prevent full-repository transfers. In one test, 5.10 GB was transferred across 73 chunks from a 12 GB repository — roughly 27,800 times more data than what the model-turn channel required.explainx+1

xAI's Response and Musk's Pledge

On July 13, the same Grok Build binary stopped making storage requests. Retesting confirmed the server now returned a `disable_codebase_upload: true` flag, indicating a server-side mitigation. xAI addressed the matter through its @SpaceXAI account on X, stating that enterprise teams using Zero Data Retention never had code stored, and that individual users could run a `/privacy` CLI command to disable retention and delete previously synced data.theregister+3

Musk responded directly on X: "As a precautionary measure, all user data that was uploaded to SpaceXAI before now will be completely and utterly deleted. Zero anything whatsoever will remain." He acknowledged that retaining some data is useful for debugging but stressed that privacy settings would always be respected.basenor+3

Lingering Concerns

Cereblab noted that the fix came without a formal security advisory, changelog entry, or public explanation of the scope or retention period of already-collected data. The researchers also pushed back on xAI's framing of the `/privacy` command as the relevant control, writing: "What actually stopped the upload was a silent global flag — `disable_codebase_upload: true` — that applies whether you opt in or out. /privacy is a per-session retention toggle, not the switch that fixed this."aiweekly+2

The incident has intensified scrutiny of how AI-powered coding tools handle local developer environments, particularly as competitors face similar questions about the boundary between useful context and unauthorized data collection.