Skip to main content
promotional banner for can you prove your CC^ checklist
IncidentSeverity S: serious, 4/5Reported: press reporting only

Grok Build coding agent's public share links exposed confidential app data, including SpaceXSI's internal information

A security researcher said a passive DNS search found 43,601 links ending in grok.me for apps built with the Grok Build coding agent, and more than 35,000 of them were public, so anyone clicking a link could open the app and all the data it stored. His tests found that Grok sets links to 'Anyone with the link' by default. That contradicts a statement from Cursor, the AI coding service SpaceXSI recently acquired, that apps are private by default. Some of the exposed information was proprietary internal data belonging to SpaceXSI, and the company removed that data after Ars Technica asked about it. The researcher said other app builders such as Lovable, Bolt and Replit expose apps through the same DNS records, but Grok had by far the most sensitive company data.

What the AI did

Grok Build, an AI coding agent, was used to build apps that were each given a shareable web address ending in grok.me. A researcher's tests found that these share links were set by default to 'Anyone with the link', so anyone who found a link could open the app and all the data it stored.

First reported November 10, 2026 · Added to the register November 15, 2026 · 4 sources

Developer
SpaceXSI
Model
Grok Build
Affected
SpaceXSI, US Navy ship engineering contractor (108 personnel), Peruvian construction company workers (3,784 medical exam records), SpaceXSI and X, A hospital group, a fire department and SpaceXSI
When it happened
Not stated in the sources
First reported
November 10, 2026

What this means for you

Could this affect you?

Yes

If you build or share apps with Grok Build or similar AI app builders. More than 35,000 Grok Build app links were reported to be public, exposing organisations and developers who built and shared apps this way, including SpaceXSI, and users of builders such as Lovable, Bolt and Replit may also be exposed through findable app addresses.

What to check

  • Audit any apps you have built with Grok Build.
  • Switch sharing from 'Anyone with the link' to invited users or only you unless public access is intended.
  • Treat app web addresses on AI app builders as discoverable by anyone.
  • Keep confidential data out of shared apps.

Timeline

  1. November 10, 2026First reported
  2. November 11, 2026Claroc reported that exposed Grok Build apps included a Peruvian construction company's occupational-health dashboard with records of 3,784 worker medical examinations, and a roster of 108 personnel associated with a ship engineering contractor supporting a US Navy logistics contract. Claroc said it notified SpaceXSI on 8 November about 24 publicly accessible apps created by SpaceXSI and X employees.[3]
  3. November 11, 2026SpaceXSI reportedly did not respond until Claroc tagged Musk and another company official on X, after which it took down 24 of its own exposed apps; Claroc said it has not done the same for apps other Grok users and organisations left open. Exposed organisations included a hospital group, a fire department and six Fortune 500 companies.[2]
  4. November 11, 2026In a post, Grok said the Ars Technica article was "incorrect," saying it referred to the app builder feature on grok.com rather than Grok Build, and added that users review sharing settings and a warning before publishing apps.[4]
Every fact and its source (14)
  1. Claroc notified SpaceXSI8 November
    “Claroc said it notified SpaceXSI on Sunday, 8 November”[3]
  2. Other platforms with similar exposureLovable, Bolt and Replit
    “app builders, including Lovable, Bolt, and Replit, “also give each app its own web address”[1]
  3. Company responseData removed after Ars asked about it
    “why the company removed the data after Ars asked about it”[1]
  4. Cursor's responseSaid apps are private by default
    “apps are private by default and nothing goes public unless the creator chooses to share it”[1]
  5. ResearcherAprozper
    “Aprozper’s tests contradict the representative’s statement”[1]
  6. Default sharing setting found in testsLinks set to 'Anyone with the link' by default
    “by default, Grok sets links to”[1]
  7. Links that were publicMore than 35,000 (nearly 95 percent)
    “Of them, more than 35,000, or nearly 95 percent, were public”[1]
  8. Links found via passive DNS search43,601 links ending in grok.me
    “a passive DNS search returned 43,601 links ending in grok.me”[1]
  9. ResearcherSecurity firm Claroc
    “security fraud firm Claroc told Ars Technica”[2]
  10. Large companies exposedSix Fortune 500 companies; 26 with over 1,000 employees
    “Six other companies exposed were in the Fortune 500 list and 26 had more than 1,000 employees”[2]
  11. SpaceXSI material exposedSales territory map of 594 strategic accounts
    “sales territory map of 594 strategic accounts”[2]
  12. Password protectionOnly one exposed app asked for a password
    “Only one of the exposed apps asked for a password.”[2]
  13. SpaceXSI responseTook down 24 of its own exposed apps
    “SpaceXSI took down 24 of its own apps exposed by the links”[2]
  14. Company responseUsers review sharing settings and a warning before publishing
    “It added that users review sharing settings and a warning before publishing apps.”[4]

Sources

  1. Grok Build coding agent leaks oodles of confidential info, some belonging to SpaceXSI
    arstechnica.com · November 10, 2026
  2. A Grok Vibe-Coding Agent Leaked Sensitive SpaceXSI Data
    engadget.com · November 11, 2026
  3. Elon Musk's Grok Exposed 3,784 Medical Exams and Navy Contractor Data—Then Its Apps Went Offline
    ibtimes.co.uk · November 11, 2026
  4. SpaceXSI's Grok Build reportedly leaked private info from thousands of users — including its own business.
    theverge.com · November 12, 2026

How this record is classified. Severity S (4/5): real harm to one organisation, data exposed, or a containment failure. OECD level: incident, an event in which an AI system led to actual harm. Evidence: Reported, meaning press reporting only.

The facts in At a glance and in Every fact and its source are quoted from the sources listed. The summary, What the AI did and What this means for you are written from those sources and checked against them automatically before publication. Records reflect what has been disclosed, not everything that has happened. Incidents are found through news feeds and the GDELT Project.

Promotional banner graphic asking if you are ready for PCI DSS 4.0 with a call-to-action to get the guide