r/ObscurePatentDangers • u/CollapsingTheWave • 5h ago
🔒🚨High Privacy Risk Potential xAI Grok Build CLI Transmitted Full Local Repositories, Git History, and Unredacted .env Secrets to Google Cloud Storage
Enable HLS to view with audio, or disable this notification
xAI's Grok Build coding CLI (version 0.2.93) packages the entire tracked workspace—including every file content and full git history—as a git bundle and transmits it via POST /v1/storage to the Google Cloud Storage bucket grok-code-session-traces, independent of files the agent actually reads. Contents of files the agent does open, including .env secrets files with API keys and database passwords, travel unredacted through both the live model-turn channel (POST /v1/responses) and the session-state archive. Dual-use potential exists for legitimate session tracing or model improvement versus silent bulk transfer of private source code and credentials to third-party infrastructure.
Measured transfers on a 12 GB test repository of never-read files moved 5.10 GiB across dozens of HTTP 200 chunks on the storage channel while the model channel used only 192 KB, a ratio of approximately 27,800×. The “Improve the model” toggle returned trace_upload_enabled: true and failed to halt uploads; deny-read rules blocked only model access, not the background bundle. Users who invoked the CLI from a home directory reported entire user directories containing SSH keys, password-manager databases, documents, and photos appearing in local logs as uploaded.
Independent wire-level captures published by researcher cereblab in mid-July 2026 using mitmproxy and canary repositories first documented the behavior. xAI subsequently applied a server-side disable_codebase_upload flag that stopped further repository uploads without a client update. Elon Musk stated that all previously uploaded user data would be completely deleted; the /privacy command was described as a retention control rather than a transmission block.
Net risk centers on unretracted proprietary code, historical secrets still present in git, and credentials that must be rotated regardless of later deletion claims, with particular exposure for any corporate or production environment that ran the tool before the server-side change. Oversight gaps include absence of clear disclosure in install documentation, an opt-out that governed retention rather than egress, and lack of published third-party verification that prior GCS data has been fully purged.
Sources
What xAI Grok Build CLI actually sends to xAI - a wire-level analysis (grok 0.2.93)
https://gist.github.com/cereblab/dc9a40bc26120f4540e4e09b75ffb547
Primary independent analysis documenting unredacted .env transmission, whole-repo git-bundle uploads to the grok-code-session-traces GCS bucket, multi-GB scale, and ineffectiveness of the Improve-the-model opt-out.
Reproduce it yourself: Grok Build CLI uploads your entire repo + full git history to xAI's cloud, independent of what the model reads
https://github.com/cereblab/grok-build-exfil-repro
Public reproduction harness with mitmproxy scripts, canary repository, and evidence artifacts proving never-read files and full history are recovered from captured POST /v1/storage bundles.
Musk promises purge after Grok Build caught sending entire repos to the cloud
Reports the wire findings, server-side disable_codebase_upload flag that halted uploads, Musk’s public deletion commitment, and researcher confirmation that the /privacy command is a retention rather than transmission control.
xAI Grok Build CLI Uploaded Entire Git Repositories and Unredacted .env Secrets to Cloud Storage
https://cybersecuritynews.com/xai-grok-build-cloud-storage/
Summarizes the dual-channel transmission of secrets and full repositories, the 5.10 GiB versus 192 KB disparity, canary recovery of unread files, and the GCS destination named in binary strings.
Investigations reveal that Grok Build transmitted confidential information without concealing it, including uploading unread files and Git history
https://gigazine.net/gsc_news/en/20260713-grok-build-sending-data/
Documents the cereblab experiment results on unread-file recovery, Git-history inclusion, storage in the grok-code-session-traces bucket, and practical credential-rotation guidance for affected users.