Level 2. Safeguard failure
Grok Build Uploaded Entire Git Repositories to xAI Storage, Not Just Files It Read
- Developer
- xAI
- Model
- Not established
- When it happened
- July 10, 2026
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by thehackernews.com. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 2 of 5Safeguard failure
- Potential
- 3 of 5Significant control incident
A safeguard, permission or control was defeated, and the effect stayed limited. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
Why this level
- The system acted without authorisation. Argues for level 2
- Sensitive data was reachable. Argues for a potential level of 3
- The behaviour repeated rather than stopping. Argues for a potential level of 3
What is established, and what is not
Confirmed
Nothing is confirmed yet.
Reported, not confirmed
The behaviour repeated rather than stopping
Cloning the captured bundle recovered it verbatim along with the repo's full commit history, and the same test replicated on a second, unrelated repo.
Grok Build Uploaded Entire Git Repositories to xAI Storage, Not Just Files It ReadSensitive data was reachable
The behavior is still the problem: a credential file the agent read during a task went out and was stored with no redaction.
Grok Build Uploaded Entire Git Repositories to xAI Storage, Not Just Files It ReadThe system acted without authorisation
With "Improve the model" turned off, Grok still uploaded the repository, and the server's own /v1/settings response kept returning trace_upload_enabled: true .
Grok Build Uploaded Entire Git Repositories to xAI Storage, Not Just Files It Read
Checked, and did not happen
Nothing here was checked and ruled out.
Not confirmed
Nothing is outstanding.
Where this came from
The original report · read September 20, 2026
Grok Build Uploaded Entire Git Repositories to xAI Storage, Not Just Files It ReadA structured incident database · read September 18, 2026
AI Failure Index (CC-BY-4.0 data fields)Where we first saw it · read September 19, 2026
Grok Build was caught uploading entire repositories, deleted secrets included, to xAI's cloudWhere we first saw it
What xAI Grok Build CLI actually sends to xAI, a wire-level analysis (grok 0.2.93)Where we first saw it
Musk promises purge after Grok Build caught sending entire repos to the cloud
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.