# Grok Build coding agent exposes confidential data, security firm Claroc reports

Published 2026-11-11T11:04:48.000Z · AI Pulse · https://ai-pulse.news/code-dev/grok-build-apps-data-exposure-claroc

*This story was written with the help of artificial intelligence, checked automatically, then reviewed by an editor before publication, under our AI policy : https://ai-pulse.news/ai-policy*

Security firm Claroc reported in early November 2026 that more than 35,000 apps built with SpaceXSI's Grok Build coding tool were open to anyone with a link; according to Claroc, SpaceXSI says Grok apps are private by default.

## Key points

- Claroc says 35,578 of 37,571 live Grok Build apps (94.7%) opened to anyone without a login, including internal data from about 30 identified organisations.
- Claroc found 24 apps built by SpaceXSI and X that were publicly open, including a confidential onboarding plan and a 594-account territory map.
- Claroc says Grok defaults to "Anyone with the link" when publishing; Ars Technica says its tests confirmed this default.
- According to Claroc, SpaceXSI says Grok apps are private by default; a Cursor spokesperson says the same, a claim Ars Technica says its own testing contradicts.

## What Claroc reports

Claroc, a security company, reports that SpaceXSI's AI coding tool Grok Build exposes confidential user data, including some belonging to SpaceXSI itself ([Ars Technica](https://arstechnica.com/security/2026/11/grok-build-coding-agent-leaks-oodles-of-confidential-info-some-belonging-to-spacexsi/)).

According to Claroc, it found 43,601 links ending in grok.me through passive DNS. More than 35,000 of them, close to 95%, were public and opened onto the app and its data. In its own blog post dated 8 November 2026, Claroc gives a figure of 35,578 apps out of 37,571 still online (94.7%) that opened to anyone without signing in. It says these included internal data from roughly 30 identified organisations ([Claroc blog](https://blog.claroc.io/ghostshares-grok-build-apps/)).

These figures are Claroc's findings. The accounts available do not describe how Claroc verified the organisations' identities or what share of the exposed data was sensitive.

## SpaceXSI and X apps among those exposed

Claroc says it found 24 applications built by SpaceXSI and X that were open to everyone. They included a confidential onboarding plan, a map of commercial territories covering 594 accounts, and advertising proposals ([Claroc blog](https://blog.claroc.io/ghostshares-grok-build-apps/)).

According to the Claroc blog, SpaceXSI removed those 24 apps after the report but did not do so for the other exposed apps.

## Default settings and how links can be found

Claroc says Grok offers "Anyone with the link" as the default setting when a user publishes an app. Ars Technica reports that its tests confirmed this default behaviour ([Ars Technica](https://arstechnica.com/security/2026/11/grok-build-coding-agent-leaks-oodles-of-confidential-info-some-belonging-to-spacexsi/)).

Claroc also argues that the random part of Grok links sits to the left of the domain name. In its account, that placement lets anyone enumerate them through passive DNS, unlike Google Docs. By contrast, Claroc says ChatGPT apps default to "Only me", and that shared conversations on Claude, ChatGPT and Gemini put the secret in the URL path, outside DNS ([Claroc blog](https://blog.claroc.io/ghostshares-grok-build-apps/)).

This comparison is Claroc's analysis, not an independent assessment.

## Disclosure and company response

Claroc says it notified SpaceXSI of the leak on a Sunday and received no reply. It then raised the issue publicly with Elon Musk and the head of Grok on X ([Ars Technica](https://arstechnica.com/security/2026/11/grok-build-coding-agent-leaks-oodles-of-confidential-info-some-belonging-to-spacexsi/)).

According to Claroc, SpaceXSI says Grok apps are private by default. A spokesperson for Cursor, which SpaceXSI recently acquired, also says Grok Build apps are private by default. Ars Technica says its own tests contradict the Cursor spokesperson's claim.

### Open questions

The accounts do not say whether SpaceXSI plans to change the default setting, or whether the remaining exposed apps have been taken offline. The available accounts come from Claroc and Ars Technica, so the full scale of the exposure has not been independently established.

**Claroc's reported figures on exposed Grok Build apps (Ars Technica, 10 Nov 2026; Claroc blog, 8 Nov 2026)** (data as of 2026-11-10)

| Measure | Figure | Source date |
| --- | --- | --- |
| grok.me links found via passive DNS | 43,601 | 2026-11-10 |
| Of which public (approx.) | More than 35,000 (nearly 95%) | 2026-11-10 |
| Apps still online | 37,571 | 2026-11-08 |
| Apps open without login | 35,578 (94.7%) | 2026-11-08 |
| SpaceXSI and X apps open | 24 | 2026-11-08 |
| Organisations with internal data exposed (approx.) | 30 | 2026-11-08 |

## FAQ

### How many Grok Build apps were exposed, according to Claroc?

Claroc says 35,578 of 37,571 apps still online (94.7%) opened to anyone without a login.

### Does Grok make apps public by default?

Claroc says the default is "Anyone with the link", and Ars Technica says its tests confirmed it. According to Claroc, SpaceXSI says apps are private by default; a Cursor spokesperson says the same, and Ars Technica says its testing contradicts that claim.

### Did SpaceXSI fix the problem?

According to Claroc's blog, SpaceXSI removed its own 24 open apps after the report but not the other exposed apps.

## Sources

1. [Grok Build coding agent leaks oodles of confidential info, some belonging to SpaceXSI](https://arstechnica.com/security/2026/11/grok-build-coding-agent-leaks-oodles-of-confidential-info-some-belonging-to-spacexsi/), Ars Technica, 2026-11-10
2. [https://blog.claroc.io/ghostshares-grok-build-apps/](https://blog.claroc.io/ghostshares-grok-build-apps/), blog.claroc.io, 2026-11-08 (primary source)
