Musk promises purge after Grok Build failure
Elon Musk is at the center of yet another controversy, this time involving Grok Build, a tool from SpaceXAI. The issue is serious: Grok Build was caught sending entire repositories to the cloud without the proper authorization from users. This is not just a technical slip; it's a potential privacy nightmare. A researcher from Cereblab raised the alarm, revealing that Grok Build was transmitting data to a Google Cloud Storage bucket. It wasn't just the file the user requested, but entire repository packages. Imagine, you order a coffee and they deliver the whole bakery.
The discovery was shocking, especially because Grok Build was going beyond other similar tools, like Claude Code and Codex, which only open specific files. The cherry on top? Even when the command was just an "OK", Grok Build sent everything, including Git histories with secrets deleted long ago. Other users reported the same, with sensitive data such as SSH keys and password manager databases being exposed.
The quick response from SpaceXAI
The backlash was so great that SpaceXAI and Musk himself had to speak out. The company quickly adjusted Grok Build to stop sending entire repositories. The detail is that this only happened after developers set the parameter "disable_codebase_upload" to "true". SpaceXAI assured that it respects the choice of customers who activate zero data retention, but for those who did not activate it, a simple command can delete everything that was collected.
"We deeply care about your privacy," stated SpaceXAI. But, honestly, this sounds like an apology after the damage has already been done. Musk, for his part, promised that all data sent before the change would be completely deleted. However, he still encourages users to share data, claiming that it helps in debugging.
The solution that did not please everyone
Despite the measures taken, Cereblab is not completely satisfied. They point out that what really stopped the upload was a silent global adjustment, not the "/privacy" command that the company suggests. The criticism is that
Comments (0)
Comments are moderated and if they violate our Terms and Conditions of use, the comment will be deleted. Persistence in violation will result in a ban of your account.