A researcher who reverse-engineered xAI's official Grok command-line client (Grok CLI) found that the client quietly packaged entire project directories into tar.gz “before-and-after” snapshots and uploaded them to an xAI cloud bucket. The uploads were sent over a separate channel that was not part of the model response path.
Details of the finding
- The researcher tested the CLI on an isolated repository and asked the model for a single-word reply. Despite the minimal request, the Grok CLI uploaded all files from the project.
- Uploaded items included the source code, a Claude Code configuration located in a different folder, and a live API key the researcher had not provided to the service.
- The client compressed the project state into tar.gz archives and a separate pipeline forwarded those archives to what the researcher identified as an xAI cloud storage bucket.
Why this matters
The issue is notable for two reasons:
- Separate channel: the data transfer happened outside the communication channel used for normal model interaction, meaning files were exfiltrated in the background rather than being part of the requested response.
- Sensitive data exposure: files and credentials that users had not intended to share were included in the uploads, creating the risk that keys or other secrets could reach third parties or be stored on company servers.
xAI's response
According to the researcher, hours after the discovery became public, xAI silently disabled the server-side upload functionality. xAI did not provide a detailed public explanation at the time about why the upload existed in the client or whether it was intended as diagnostics.
Consequences and open questions
The incident highlights how agent-oriented clients can reach into local user environments. Developers and users should consider:
- What data packaging and uploading behavior is implemented or required by a client?
- Is there a transparent, opt-in mechanism for such uploads?
- How do providers control access to and deletion of stored archives?
Advice for users
- Monitor: check client behavior, logs, and network traffic in development or isolated environments.
- Isolate secrets: keep API keys and sensitive configuration in separated, secure secret stores rather than in project folders.
- Be cautious: if a client does not document background uploads clearly, consider avoiding it or seeking alternatives.
Closing
The researcher reported that Grok CLI automatically packaged and transmitted whole project folders, including files the user did not intentionally share. xAI later disabled the server-side upload, but the incident underscores the need for transparency about background data transfers performed by agents and command-line clients.
