xAI's Grok Build CLI secretly uploaded private Git repositories to GCP
The uploads bypassed standard opt-out settings and exposed sensitive.env secrets.
Combined views
12M
41 Sources, first seen ago
Sources
GO 
Gergely Orosz@GergelyOroszCannot see any sensible company use Grok CLI based on this terrible incident If you are an amateur (meaning you don't make much or any money from your code) and do not care about security (aka you don't mind if your .env files leak - which you should care about) then use it…
- likes: 762
- replies: 48
- bookmarks: 70
- reposts: 52
CE Carlos E. Perez@IntuitMachineGPT-5.6 rumoured to delete entire folders... Now Grok found to be uploading entire directories?! WTF is going on? https://twitter.com/IntCyberDigest/status/2076689215258014069
- likes: 15
- replies: 3
- bookmarks: 4
- reposts: 4
“P “paula”@paularambles- likes: 601
- replies: 2
- bookmarks: 33
- reposts: 24
XJ xjdr@_xjdrthis is terrible and unacceptable full stop. but assuming this was benign, and they wanted to enable future cloud operations on your git repo, this is why you would build and vertically integrate an scm into your full product suite and not tar a fucking repo and upload it to a…
- likes: 252
- replies: 8
- bookmarks: 37
- reposts: 11
AM Amjad Masad@amasad- likes: 1.2K
- replies: 23
- bookmarks: 66
- reposts: 38
XL xlr8harder@xlr8harderMy biggest problem with being a user of xAI is that it's run unprofessionally. They shut down 4.1-fast with no migration path and little warning. There should already be publicly acknowledged, mitigated, and we deserve a public incident review. I won't hold my breath.…
- likes: 129
- replies: 13
- bookmarks: 4
- reposts: 2