SpaceXAI 的 Grok 编程工具曾将用户完整代码库上传至云存储

SpaceXAI 的 Grok Build AI 编码工具在被曝光之前会将用户的整个代码库上传到 Google Cloud，随后该公司关闭了此功能。The Register 报道，Cereblab 在周一发布的研究显示，Grok Build CLI 会打包并上传整个代码仓库，“包括它被指示不要打开的文件以及从历史记录中删除的密钥”，其数据保留量远超 Claude Code 等类似工具。

研究人员称，截至周一，他们的测试显示 SpaceXAI 的服务器返回了一个 “disable_codebase_upload: true” 标志，且代码库上传“不再触发”。

Elon Musk 在 X 上发帖声称，此前 Grok Build 上传的所有数据将被“彻底、完全删除”。Musk 在另一篇帖子中还表示，“隐私设置始终被尊重”，但请求用户允许 SpaceXAI 保留他们的数据，称这“有助于调试问题”。

伦敦国王学院的独立安全研究员 Lukasz Olejnik 博士向 The Verge 确认，这种数据保留量“过度”，并补充说，可能面临风险的数据包括“专有源代码、安全漏洞信息、个人数据、基础设施详情[以及]凭据”。

SpaceXAI 最初在一篇帖子中回应称，“如果[零数据保留]被禁用，CLI 中可使用 /privacy 命令来禁用数据保留，该命令同时会删除先前同步的数据。”然而，Cereblab 指出，“/privacy 是每会话的保留开关，并不是修复此问题的开关，因此不应将其作为控制手段。”

SpaceXAI’s Grok Build AI coding tool was spotted uploading users’ entire codebases to Google Cloud before it was reported, and the company turned it off. The Register reports that Cereblab published findings on Monday showing how the Grok Build CLI was packaging and uploading entire code repositories, “including files it was told not to open and secrets deleted from history,” significantly more data retention than similar tools like Claude Code.

The researchers say that as of Monday, their tests show SpaceXAI’s servers returning a “disable_codebase_upload: true” flag, and the codebase upload “no longer fires.”

Elon Musk responded to the incident in a post on X claiming that all data Grok Build previously uploaded will be “completely and utterly deleted.” Musk also said in a separate post that “privacy settings are always respected,” but asked users to allow SpaceXAI to retain their data, saying it’s “helpful for debugging issues.”

Dr. Lukasz Olejnik, an independent security researcher at King’s College London, confirmed to The Verge that this amount of data retention is “excessive,” adding that the data potentially at risk could include “proprietary source code, information about security vulnerabilities, personal data, infrastructure details, [and] credentials.”

SpaceXAI initially responded to the issue with a post saying that, “If [zero data retention] is disabled, the /privacy command is available in the CLI to disable data retention, which also deletes previously synced data.” However, Cereblab points out that “/privacy is a per-session retention toggle, not the switch that fixed this, so it shouldn’t be pointed to as the control.”