metir
metir
Docs
Download on App StoreGet it on Google PlayLog inSign up
Back to Blog
Grok Build
xAI
AI Security
Vibe Coding
Data Exposure

Grok Build Shared Apps Exposed: What Claroc Found, Why DNS-Visible Share Links Leak and How to Protect Vibe-Coded Apps (2026)

Security firm Claroc reported more than 35,000 Grok Build apps reachable without sign-in through DNS-discoverable share links, including medical, payroll and sales data. An analysis of the cause, the default sharing setting, how it compares with other app builders and a practical checklist.

Metir AI TeamNovember 15, 20267 min read
Grok Build Shared Apps Exposed: What Claroc Found, Why DNS-Visible Share Links Leak and How to Protect Vibe-Coded Apps (2026)

A security report published in the week of November 9, 2026 found that applications built with Grok Build, xAI's coding agent, were reachable by anyone who could find their share links. According to IBTimes, the security firm Claroc identified more than 35,000 Grok Build applications accessible without authentication, and some contained confidential company data. The operator, referred to in coverage as SpaceXSI, removed 24 apps linked to its own and X personnel after the findings were raised.

The incident is a useful case study because it is a design problem, not a break-in. This post explains how the exposure worked, what was reportedly visible, where the accounts differ, and what teams building with any AI app generator should check.

35,000+apps reachable without sign-inper Claroc
24apps linked to SpaceXSI and Xlater removed
Nov 8Claroc notified the companySunday
Nov 10report publishedTuesday

How the exposure worked

Grok Build lets users share an app through a URL whose hostname contains randomly generated words placed before the grok.me domain, per IBTimes. The words are random, so the links cannot be guessed. The weakness is that hostnames are not private: they appear in passive DNS databases, which record domain lookups. A researcher can query those databases for every hostname under the domain and obtain a list of live apps without guessing anything.

IBTimes contrasts this with a design in which the random identifier sits in the URL path, as in a similar scheme from Google, because paths are not captured by DNS records. The difference is a general principle: an unguessable link is only private if it is also not published somewhere else.

The sharing default

Claroc's account is that tests found "Anyone with the link" preselected as the sharing setting, with users required to switch to "Invited users" or "Only you" to restrict access. A default of public access plus a DNS-visible address is what turns a convenience feature into a discoverable index.

There is a dispute on this point in the coverage. IBTimes reports that a representative described Grok Build apps as private by default, becoming public only when creators share them, and noted that other tools offer similar shareable links. Those two descriptions can both be partly true: an app may be private until a creator shares it, while the share dialog may default to the broadest option. The sources do not settle which setting the share dialog presented at each point in time, so this post treats the default as reported by Claroc and disputed by a company-side voice.

“

A share link that nobody can guess is still a public address if the hostname is indexed in DNS.

Analysis of the Claroc findings

What was reportedly exposed

Records in exposed Grok Build apps cited by Claroc

Counts of people or accounts named in the examples Claroc reported; units differ by bar.

Worker medical exams (Peruvian construction firm)3,784 exams
Employee roster (healthcare company)~3,565 employees
Sales territory map (SpaceXSI and X apps)594 accounts
Personnel roster (Navy-logistics contractor)108 personnel
Technician scorecard (service centre)22 technicians

Examples as reported by IBTimes citing Claroc. Units: medical exams, employees, accounts, personnel, technicians.

Examples listed in coverage of Claroc's report:

  • A Peruvian construction company's occupational-health dashboard with records of 3,784 worker medical examinations.
  • A roster of 108 personnel at a ship engineering contractor supporting a US Navy logistics contract.
  • A Tesla service-centre scorecard covering 22 technicians and their bonus status.
  • A healthcare company's roster of approximately 3,565 employees.
  • From the 24 apps linked to SpaceXSI and X: a confidential enterprise sales onboarding plan, a sales territory map covering 594 accounts, internal system addresses and advertising proposals.

The pattern is that people built internal tools, such as dashboards, rosters and scorecards, and shared them for convenience. Those are exactly the artifacts that carry personal and commercial data, and none of them was designed as a public website.

Is this unique to one tool?

According to the report, the researcher acknowledged that Lovable, Bolt and Replit also generate DNS-discoverable addresses, but said Grok exposed far more sensitive company data. That distinction is about volume and sensitivity, not mechanism. The shared lesson across the category is that AI app builders have made it cheap for non-engineers to deploy web apps, while the access-control decisions that engineers once made explicitly now sit behind a share toggle.

An earlier, separate issue concerned how the Grok Build command-line tool handled repository uploads. A Better Stack guide dated July 2026 describes an analyst intercepting its traffic and finding full git bundles sent to xAI servers, and notes that xAI responded by flipping a server-side setting. That is a different mechanism and a different date from the share-link finding, and it is mentioned here only to distinguish the two.

Elon Musk, whose companies operate xAI and the Grok products, in a 2021 portrait
Elon Musk, whose companies are associated with xAI and Grok. File portrait from 2021; it does not depict the incident.

A practical checklist for teams using AI app builders

  1. Treat every shared app as published. Assume anything shared by link can be found, whatever the URL looks like.
  2. Change the default. Set sharing to invited users or owner-only before adding any real data, and check the setting again after each edit.
  3. Keep real records out of prototypes. Use synthetic or masked data for dashboards until access control is verified.
  4. Inventory what exists. Ask who in the organisation has deployed apps, and on which platforms, since non-engineers can create them without review.
  5. Look for hostname exposure. Check whether your tool puts identifiers in hostnames, which passive DNS can list, or in paths.
  6. Plan for exposure. If medical, payroll or customer data was in an app, treat it as a potential breach and follow your notification obligations.

Organisations that want AI assistance without tying work to one vendor's hosting can keep documents and analysis in a workspace that separates the model from where results are stored, which is the approach Metir takes. Whatever the tool, sharing defaults deserve the same scrutiny as any other access policy.

What is still unknown

Coverage does not state how long the apps were reachable, whether anyone other than researchers accessed them, or what notification the affected companies made. IBTimes reports that Claroc notified the company on Sunday, November 8, and had no direct response by publication on Tuesday, and that removals of the 24 company-linked apps followed. Those details will matter for any assessment of impact.

Sources:

  • Elon Musk's Grok exposed 3,784 medical exams and Navy contractor data, then its apps went offline - IBTimes UK
  • The Grok CLI data leak: what was uploaded and what to do now - Better Stack

Image credits

Header and in-body image: Elon Musk in 2021, by Ministerio Das Comunicacoes, via Wikimedia Commons, licensed CC BY 2.0.

Ready to experience AI that adapts to you?

metir brings together the world's best AI models in one seamless experience. Start for free today.

Get Started Free
metir

metir is where work gets done. Hire your team of Orbs, AI teammates with their own computer, alongside your mail, meetings and workspace.

© 2026 metir. All rights reserved.

Product

  • Features
  • Pricing
  • Research
  • Docs
  • Blog
  • Enterprise

Company

  • Docs
  • Support
  • Careers

Legal

  • Terms of service
  • Privacy policy

Personalisation is powerful. Privacy is non-negotiable.

Status: All systems operational