TechAILatest.newsTrackers
Cybersecurity

Grok Build left 35,578 of 37,571 published apps open to anyone, Claroc finds

Security firm Claroc found 35,578 of 37,571 live Grok Build apps open without sign-in, some holding hospital, fire department and SpaceXSI internal data.

By Gürkan E.Published

Image Claroc published with the announcement covered in this storyTech AI Latest
Image published by Claroc with the announcement. Image: Claroc

Security firm Claroc reported on 10 November 2026 that 35,578 of the 37,571 live apps it found on SpaceXSI's Grok Build platform could be opened by anyone, without signing in. Each app gets its own grok.me hostname, which passive DNS services record, and the publish step offered "Anyone with the link" by default. Some apps held data from a hospital group, a fire department and SpaceXSI itself. SpaceXSI says apps stay private until shared.

Key facts

  • Disclosed: 10 November 2026 in Claroc's GhostShares research; found on 8 November
  • Scale: 43,551 grok.me addresses tested, 37,571 live apps, 35,578 open without sign-in (about 94.7 percent)
  • Cause: each app has a public name.grok.me hostname that passive DNS datasets capture, and the publish dialog preselected "Anyone with the link"
  • Exposed data included records from a hospital group, a fire department and SpaceXSI's own sales material, according to Claroc and Engadget
  • Severity: Claroc rates about 2 percent of the exposed material as critical; only one exposed app asked for a password
  • SpaceXSI's position: apps are private until the creator shares them; it removed apps built by its own staff

What Claroc found

Grok Build, the coding agent from SpaceXSI (the AI business formerly known as xAI), lets users describe an app in plain language and publish the result to the web with one click. Security firm Claroc reported on 10 November 2026 that this publish step left most of those apps open to anyone who knew where to look. In its write-up, GhostShares: Grok Build apps, Claroc says it tested 43,551 Grok Build addresses, found 37,571 live apps, and could open 35,578 of them without signing in, about 94.7 percent. The figures were repeated by Engadget, The Next Web and Cybernews, and the Cloud Security Alliance published a research note on the finding.

Most of the open apps were harmless: games, landing pages and calculators. But a share of them held internal or personal data, and Claroc rates about 2 percent of the exposed material as critical. Engadget reported that the exposed material included information from a hospital group, a fire department and SpaceXSI itself; Claroc says the SpaceXSI material included internal sales plans, and that it also found data belonging to large companies. Only one of the exposed apps asked visitors for a password.

How the apps became findable

No software bug was needed. Every published Grok Build app is served from its own hostname in the form name.grok.me, and the name is usually a set of random words that Grok suggests. That looks like a secret link, but hostnames are not secret: commercial passive DNS services record every name that resolvers look up, and those datasets can be searched. Claroc used such data to list the apps in bulk. A separate researcher who ran a passive DNS search reported a similar count, around 43,600 grok.me hostnames.

The second half of the problem is the default. In the paid account Claroc used, clicking Publish proposed "Anyone with the link" as the access setting, so a user who accepted the dialog made the app public to anyone who could find the hostname. Shared links from chat assistants usually live under one domain with a long random path, which DNS records never see; a per-app subdomain leaks the address the moment someone opens it. For more incidents of this kind, see the cybersecurity hub.

SpaceXSI's response and the earlier Grok Build incident

SpaceXSI's position, as given to Ars Technica, is that Grok Build apps stay private until their creator chooses to share them. Claroc disputes that, arguing that a preselected public option is the cause, and Ars reported that its own tests matched Claroc's account. According to the coverage, SpaceXSI began removing links within hours of press questions and took down the apps built by its own staff. No change to the default sharing setting and no notice to affected users had been reported by 13 November.

It is the second data handling problem for Grok Build this year. In July 2026 researchers found that the Grok Build command line tool uploaded users' entire code repositories, including files it had been told not to read; SpaceXSI disabled the feature and Elon Musk said all data uploaded that way would be deleted, as Axios reported. The pattern also fits a wider one: Wiz counted nine AI developer platform breaches in October, and NEAR AI disclosed an SGLang flaw this week.

What users should do

Anyone who has published a Grok Build app should check its sharing setting and switch it to invited users only unless the app is meant to be public, and should assume that a previously public app's address is known. Data, passwords or API keys placed in such an app should be treated as exposed and rotated. Teams that let staff use app builders like Grok Build should add them to their data handling rules, since the generated apps sit outside normal review. The open questions are whether SpaceXSI will change the default and notify owners of exposed apps.

What changed

BeforeGrok Build users could publish apps to name.grok.me addresses that looked private because the names were random words
AfterClaroc showed that 35,578 of 37,571 live apps were open to anyone, found through passive DNS, including some with hospital, fire department and SpaceXSI data
Who it affectsGrok Build users and the organizations whose data they placed in published apps; security teams that allow AI app builders

Questions people ask

How many Grok Build apps were exposed?
Claroc says 35,578 of the 37,571 live Grok Build apps it found could be opened without signing in, out of 43,551 addresses it tested.
Why could anyone find Grok Build apps?
Each app has its own name.grok.me hostname, which passive DNS datasets record, and the publish dialog preselected "Anyone with the link" in the account Claroc tested.
What did SpaceXSI say?
SpaceXSI says apps stay private until the creator shares them. It removed apps built by its own staff after the disclosure; no change to the default had been reported by 13 November 2026.

Sources

  1. GhostShares: Grok apps exposed xAI secrets and private data (Claroc, 10 Nov 2026)
  2. A Grok vibe-coding agent leaked sensitive SpaceXSI data (Engadget, 12 Nov 2026)
  3. SpaceXSI's Grok Build left 35,000 apps open, security firm Claroc says (The Next Web, 12 Nov 2026)
  4. Public by Default: Exposed Grok Apps and the AI App-Builder Leak Pattern (Cloud Security Alliance, 12 Nov 2026)
  5. SpaceXAI wipes customer data after Grok uploads sensitive information (Axios, 14 Jul 2026)

Reference pages

Spotted an error? See the corrections policy and tell the editor. Facts in this story come from the sources listed above; vendor claims are attributed.

Comments

Loading comments.

No links, no insults; comments that break the rules are not published. 0/1000

Related stories

All cybersecurity