Grok Build: SpaceXAI Accused of Downloading Repositories Without Consent

Grok Build: SpaceXAI Accused of Downloading Code Repositories Without Consent

Incident Revealed by Security Researcher

A tool developed by SpaceXAI, Grok Build, transferred entire code repositories to remote servers without user consent. This practice was brought to light on July 10, 2026, by a security researcher known by the pseudonym Cereblab. By analyzing network traffic, they found that the tool systematically sent data to a Google Cloud storage space, including unsolicited files.

Cereblab set up a proxy to monitor exchanges between Grok Build and SpaceXAI’s servers. During a test on a 12-gigabyte repository, 5.1 GB of data was transferred, including a .env file containing API access keys. This data included sensitive information such as passwords and credentials, even when the user had explicitly instructed the tool not to open certain files.

The analysis revealed two distinct channels: one for processing, limited to 192 kilobytes, and another for storage, responsible for the massive data transfer. Unlike other similar tools such as Claude Code, Codex, or Gemini, Grok Build did not limit itself to processing files necessary for a task but sent the entire repository, including the Git history.

SpaceXAI and Elon Musk’s Response

In response to these revelations, SpaceXAI quickly disabled the server-side upload function. On July 14, 2026, Cereblab confirmed that the disable_codebase_upload setting had been activated, halting unauthorized transfers. However, the company did not release an official version note to inform users of this change.

In a message posted on X on July 13, 2026, Elon Musk, CEO of SpaceXAI, stated that, "as a precautionary measure, all data previously uploaded by SpaceXAI would be deleted." He added that "zero data would remain." SpaceXAI also indicated that users with Zero Data Retention (ZDR) mode were not affected by this collection. For others, the company introduced a /privacy command to delete already synchronized data.

Cereblab criticized this measure, noting that the effective disabling of transfers relied on a server-side flag inaccessible to users and that the /privacy command did not block future transfers but only managed retention.

Comparison with Other Similar Tools

Grok Build stands out from other coding assistants due to its approach. Unlike Claude Code, Codex, or Gemini, which limit themselves to files necessary to respond to a query, Grok Build sent entire repositories, including their Git history. This practice exposes users to risks of sensitive data leaks, such as API keys or credentials.

Tests conducted by Cereblab showed that these competing tools did not adopt similar behavior. Even when clear instructions were given not to open certain files, Grok Build ignored these directives and transferred the entire repository.

Risks and Implications for Developers

The consequences of these unauthorized transfers are numerous. Developers working on sensitive projects, such as proprietary software or critical infrastructure, risk having their data exposed. .env files, often used to store confidential information, were among the data sent, increasing the risk of compromise.

One user reported that Grok Build had downloaded their entire personal directory, including SSH keys and password manager databases. These incidents demonstrate that the tool could access information far beyond the scope of software development.

Dr. Lukasz Olejnik, an independent security researcher at King’s College London, described this practice as "excessive." According to him, the exposed data could include proprietary source code, unpatched security vulnerabilities, or personal information.

Recommended Measures for Users

Developers who have used Grok Build are advised to take immediate precautions. It is recommended to assume that all API keys and passwords in the affected repositories have been compromised. These credentials should be regenerated or changed without delay, including those buried in the Git history.

To check if data has been uploaded, users can review Grok Build logs by running the following command in their terminal: cat ~/.grok/logs/unified.jsonl | grep repo_state.upload. This command helps identify repositories sent to SpaceXAI’s servers.

SpaceXAI indicated that the /privacy command allowed for the deletion of already synchronized data. However, Cereblab emphasized that this option did not block future transfers but merely managed retention. Users must therefore remain vigilant.

Conclusion: Unresolved Questions

The Grok Build incident highlights the challenges posed by the increasing integration of artificial intelligence into development tools. While SpaceXAI has taken steps to correct the issue, questions about transparency and respect for user privacy persist. Elon Musk's statement regarding the deletion of collected data remains to be verified, and the lack of clear communication about data protection mechanisms leaves doubts.

For developers, this episode serves as a reminder of the importance of vigilance when using cloud-connected tools. SpaceXAI's practices underscore the need for stricter regulation of AI technologies, particularly in the management of sensitive data.

Key Points

• Grok Build downloaded entire code repositories, including sensitive files like .env, without consent.
• A researcher (Cereblab) revealed the incident on July 10, 2026, through a network traffic analysis.
• SpaceXAI disabled the server-side download function on July 14, 2026, but without official communication.
• Elon Musk stated on July 13, 2026, that all previously uploaded data would be deleted.
• Grok Build stands out from competitors (Claude Code, Codex, Gemini) due to its invasive approach.

Sources

1. Next.ink - "Grok Build was sending repositories to the cloud without developers' consent". (secondary)
2. The Register - "Musk promises purge after Grok Build caught sending entire repos to the cloud". (secondary)
3. The Verge - "SpaceXAI’s Grok programming tool was uploading its users’ entire codebase to cloud storage". (secondary)
4. Frandroid - "Grok Build: SpaceXAI's tool was sending entire code repositories to the cloud without developers' knowledge". (secondary)

Transparency: 4 sources (0 primary, 4 secondary). Verification: July 15, 2026.

Truthyx - July 15, 2026