Grok CLI Silently Uploaded Entire Home Directories to xAI Cloud Storage

Users discovered that xAI's Grok CLI tool was uploading their entire home directory to xAI-controlled Google Cloud Storage buckets — without explicit disclosure, consent prompts, or a clear opt-in.

What Happened

Multiple users reported that after installing and running Grok CLI, the tool exfiltrated the full contents of ~ to remote storage controlled by xAI. The behavior was not prominently disclosed and came as a shock to developers who expected a local AI assistant, not a silent data uploader.

Your home directory is not an empty folder. It routinely contains:

• SSH private keys (~/.ssh/id_rsa, ~/.ssh/id_ed25519)
• Cloud provider credentials (~/.aws/credentials, ~/.azure/, ~/.config/gcloud/)
• Kubernetes configs (~/.kube/config) including cluster access tokens
• Shell history (~/.bash_history, ~/.zsh_history) — frequently containing secrets typed as CLI arguments
• .env files and dotfiles holding API keys, database passwords, and OAuth tokens
• Git credential stores and personal access tokens

Why It Matters

This is not theoretical data collection — it is credential exfiltration at scale. SSH keys provide direct server access. AWS, GCP, and Azure credentials can spin up infrastructure, read production databases, and access object storage. Kubernetes tokens can hand an attacker cluster-level control. Shell history regularly contains plaintext passwords that users typed without realizing they were being logged.

Unlike a browser extension quietly reading page content, a CLI tool with unrestricted home directory access reaches the most sensitive material on a developer's machine. The lack of clear disclosure makes this a serious security incident regardless of xAI's stated intent — and for server administrators, the exposure window begins the moment grok first ran.

What To Do — Act Now

If you installed Grok CLI at any point, treat this as an active breach until you have confirmed otherwise:

1. Uninstall Grok CLI immediately to stop any ongoing uploads.
2. Rotate all SSH key pairs — generate new keys and replace authorized keys on every server and service.
3. Cycle cloud credentials — AWS access keys, GCP service account keys, Azure credentials, and any tokens under ~/.config/, ~/.aws/, ~/.azure/.
4. Revoke Kubernetes tokens — update ~/.kube/config and rotate the referenced service account credentials in every cluster.
5. Audit .env files and dotfiles — rotate API keys for GitHub, Stripe, any payment processor, email providers, and third-party services.
6. Review shell history — scan ~/.bash_history and ~/.zsh_history for plaintext secrets and rotate anything found there.
7. Check for unauthorized access — review SSH login logs (/var/log/auth.log), AWS CloudTrail, GCP Audit Logs, and equivalent services for unusual activity since the date of installation.

Contact xAI directly to request deletion of uploaded data and to establish what was collected, where it is retained, and who can access it. The situation is still developing — monitor the original disclosure thread for updates as more details emerge.