Grok Build Agent Exposes 35,000 Apps, Including SpaceXSI's Own Files

Grok Build, the AI coding agent run by Elon Musk's SpaceXSI, exposed data from roughly 35,000 user-built apps to anyone who located the right link, including 24 internal apps built by SpaceXSI itself, according to research from security firm Claroc reported by Ars Technica. Grok Build is a "vibe-coding" tool, industry shorthand for AI agents that let users build software by describing it in plain language rather than writing code directly.

How Did the Leak Happen?

Grok Build generates a sharable link for each app a user builds, and the platform randomizes those URLs so that, in theory, only someone who already knows the exact address can open the app, Claroc said. A design flaw in that system let researchers enumerate thousands of live project links regardless of the randomization, according to the firm's Tuesday post cited by Ars Technica. Clicking most of those links opened the app and surfaced whatever data had been stored inside it, with no login wall in front.

What Kind of Data Was Exposed?

The exposed material ranged from internal business plans and advertising proposals to medical records and staff rosters, Claroc found. Specific examples cited in the research include an occupational-health dashboard built by a Peruvian construction company containing 3,784 worker medical exams, a Tesla service-center scorecard naming 22 technicians along with productivity and bonus data, a roster of 108 people tied to a US Navy ship-engineering logistics contract, a galley checklist from a celebrity cruise line listing crew by full name and employee ID, and a hospital staffing app listing roughly 3,000 names, according to the Ars Technica report.

Why Was SpaceXSI's Own Data Among the Leaks?

Claroc said it found 24 apps built by SpaceXSI — the merged SpaceX and xAI entity that owns Grok — exposing the company's own internal material. Those apps included a confidential onboarding plan for a new enterprise sales team member, a sales territory map covering 594 accounts, internal system addresses used by the sales team's tools, and advertising proposals, the firm said. "We were shocked," Claroc wrote in its Tuesday post. "The company that makes Grok had its own internal material open to anyone holding the link, and we had never been given it. Had the sales team bought a tool for this, it would have sat behind company sign-in, open only to the team. Built with AI, it went live open to anyone with the link."

How Did SpaceXSI Respond to the Report?

Claroc said it notified SpaceXSI of the exposure on Sunday and got no response. A Claroc official then posted on X, tagging both Musk and Grok manager Matt Palmer, to flag the issue directly, according to Ars Technica. By Monday evening, the 24 SpaceXSI apps were still exposing their data. SpaceXSI began pulling the sharable links within a few hours of Ars Technica sending the company questions for its article, and by the time that story published, all 24 SpaceXSI links returned an "app not found" error. Ars Technica did not report a similar fix timeline for the roughly 35,000 non-SpaceXSI apps Claroc said remained exposed.

What Does This Mean for Other Grok Build Users?

The episode lands as regulators are already scrutinizing how AI firms handle data: New York's AI oversight law carries fines of up to $3 million for violations by major developers including OpenAI and Anthropic, underscoring the compliance stakes facing companies that build and deploy generative AI tools at scale. For Grok Build users specifically, Claroc's findings suggest that any app built on the platform and shared via its default link system may have been retrievable by outside parties without a password, regardless of whether the builder intended the project to stay private. Ars Technica's report does not say whether SpaceXSI has committed to redesigning the link-generation system for the broader user base beyond the fixes applied to its own 24 apps, nor does it specify how long the roughly 35,000 exposed third-party apps had been reachable before Claroc's disclosure. SpaceXSI has not published a public statement addressing the scope of the exposure beyond removing its own affected links, according to the sourcing available.