Grok Build CLI Reportedly Uploaded Full Repositories, Including Private Code and Secrets

· Original article ↗

Summary

Reports allege Grok Build CLI uploaded users’ full repositories, including private code and secrets, to cloud storage. The company says sharing can be disabled and prior uploads may be deleted, but scope and deletion remain unclear.

Key points

  • Reports allege Grok Build CLI uploaded entire local Git repositories to a Google Cloud bucket.
  • Private code and unredacted secrets were reportedly included; the article does not independently verify the uploads or their scope.
  • The article says uploads were temporarily suspended server-side and describes sharing as enabled by default, with an opt-out available through the /privacy command.
  • The company says privacy settings can disable sharing and may remove previously uploaded data, but has not explained the retention or deletion process or provided independent auditing assurances.
  • Security experts advise users to opt out and rotate credentials that may have been included in uploaded repositories.

Article Details

Victim Organization
Grok Build CLI users and organizations whose repositories were reportedly uploaded; none are individually identified.
Incident Type
Reported unauthorized collection and cloud upload of entire Git repositories, including private code and unredacted secrets.
Disclosure Date
2026-07-13
Data Types Exposed
  • Private Git repository source code (reported)
  • Unredacted secrets and credentials (allegedly included)
Affected Records
Not disclosed
Affected Data Size
Not disclosed
Operational Impact
The reported uploads exposed proprietary code and potentially credentials to cloud storage. The article says the upload mechanism was temporarily suspended via a server-side flag and advises affected users to rotate exposed secrets. The scope and deletion of previously uploaded data were not independently verified.
Ransom Or Extortion
None reported
Claim Status
alleged

Vendors

Products

Related Articles