A security firm says thousands of Grok Build projects were accessible through share links, including material it identified as confidential business information and personal data. Ars Technica reports that the issue affected SpaceXSI’s own apps as well as projects belonging to other organisations, making this a consequential warning about how AI-built apps are shared.
xAI Watch analysis
What happened
Ars Technica’s 10 November report attributes the findings to Claroc, which said it identified 43,601 links ending in grok.me and found more than 35,000 opened apps and their stored data. The material Claroc described included employee details, business proposals, medical exam information and operational documents. These are findings reported by Ars and attributed to Claroc, not independently established here.
The report says Claroc notified SpaceXSI on Sunday. Ars says SpaceXSI removed links for 24 of its own apps after the publication contacted the company. A SpaceXSI representative told Ars that Grok Build apps were private by default; Claroc’s tests, as reported by Ars, contradicted that account. The representative did not respond to follow-up questions about customer notification.
Why it matters
The exposure described is not just a matter of an app looking untidy in public. Shared apps may contain the information entered or stored while building them, and the reported examples include data that could affect employees, customers and business operations.
For Grok Build users, Ars’s report says to choose “invited users” rather than “anyone with the link” unless an app is meant to be broadly accessible. That is the practical step readers can take now. The report also notes that other app-building platforms have shareable links, but does not establish that they have the same exposure.
Our read
This is a serious security report, and the disagreement between the company’s account and Claroc’s testing is central, not a footnote. Ars reports that SpaceXSI removed its own affected links, but that does not answer whether other users were notified or whether the underlying sharing behaviour has changed.
If you use Grok Build, check the access setting on every shared app and switch it to invited users or private where appropriate. “Anyone with the link” is not a substitute for access control when the link can expose more than the app’s front page.
What to watch
- Whether SpaceXSI explains the reported discrepancy over the default sharing setting.
- Whether Grok Build changes its sharing controls or clarifies how users can review access.
- Whether affected users are notified and told what information may have been exposed.
- Whether independent follow-up confirms the scope and status of the reported exposure.
Discussion spark: Should AI app builders default to private sharing even when that makes collaboration less convenient, or is the current responsibility on users to check access settings?
Sources and evidence
- Grok Build coding agent leaks oodles of confidential info, some belonging to SpaceXSI – Ars Technica (10 November 2026, 21:12 UTC)
not affiliated with or endorsed by xAI, SpaceXAI, SpaceX, X Corp. or Cursor