DEV Community

Cover image for Anyone with the link is a DNS name: what Claroc's 35,578 open Grok apps teach about AI app builders
Mukund for VxSure

Posted on

Anyone with the link is a DNS name: what Claroc's 35,578 open Grok apps teach about AI app builders

On 10 Nov 2026, Claroc Research published "GhostShares 2", a study of apps built with Grok, the AI assistant from SpaceXSI (formerly xAI). Grok can build a working app from a chat and publish it under grok.me. The report opens with a detail that sets the problem: "Nobody had sent us any of them."

Claroc tried 43,551 Grok app addresses. In the report's words: "37,571 were still online, and 35,578 of those (94.7%) opened for anyone, with no sign-in." Only 1,993 answered with HTTP 401, "the error an app set to Only you or Invited users returns."

Not every open app held anything sensitive. Claroc's estimate is "roughly 650 to 800 apps with private data". The apps in the post "did real work: sales pipelines, galley checklists, staff rosters, customer and order records," and one was "a contractor’s staff timesheet whose code held every employee’s account with the password in plain text, admins included." Besides SpaceXSI and X, Claroc identified 30 organisations with internal data in open apps.

The share link is a hostname

Most people read "Anyone with the link" as "anyone I send the link to". On Grok, the link works differently. From the report: "On Grok the link is the hostname: every published app gets its own address, <name>.grok.me."

A hostname is not private. Claroc explains why: "Every hostname gets its own DNS lookup, and that lookup is what makes the name findable." Passive DNS services "collect those lookups from the resolvers they run or buy data from", and Claroc found the app names "with common subdomain discovery techniques".

Random names don't change that. "Grok proposes four random words instead, and about half the names we saw were exactly that." Random words defeat guessing, not a list.

In our view, the hostname is the detail most threat models miss. A secret in a URL path travels inside TLS. A secret in a hostname is resolved in DNS before any connection opens.

The default, and the dispute

In Claroc's account, "clicking Publish on an app Grok built proposed Anyone with the link as the access setting." The panel offered three settings, "with Anyone with the link already selected."

SpaceXSI defends the design. Claroc reports that the company "said Grok apps are private until their creator chooses to share one, and that publishing takes several steps", and that "employee accounts are set to Only you by default". Claroc's answer: "Only you as the default is the change we asked for, and SpaceXSI already uses it for employee accounts." Both sides agree that nothing goes public before the builder clicks Publish.

Sign-in is not membership

Claroc built two test apps of its own and "published both apps with whatever it proposed." The result for the team app: "In a team app Grok built for us, “Continue with Google” let any Google account read, edit and delete the records."

The flaw is an authorisation gap, not a missing login: "a team login checks who you are but not whether you belong to the team". A sign-in button on its own doesn't keep strangers out. The other test was simpler: "From an incognito window, signed in to nothing, we added a row that the next visitor saw."

Why the IT team may never hear about it

Claroc names the reason these apps go live without company controls: "Grok, Lovable, Replit, v0, Bolt, Base44 and Google AI Studio need no admin rollout and no company account." An app "is made in a chat window and published from the same window, often in minutes". And an app can change after anyone looked at it. In Claroc's words, "an app that was harmless yesterday holds customer records today."

One trace sits on your own network. When someone in the office builds or opens one of these apps, the browser looks up the builder's hostname and connects to it. In effect, your own resolver and proxy logs are a passive DNS dataset for your own staff.

Five checks for this week

  1. Find the builders. Search your DNS and web proxy logs for grok.me and the domains of the other builders your staff might use. Claroc's first step is the same: "Find out which AI app builders your people use."
  2. Open every company app as a stranger. Use an incognito window, signed in to nothing. Claroc: "A Grok app holding anything internal should say Invited users or Only you, and a stranger should get an error page."
  3. Test sign-in from outside. Sign in with an account that isn't on the team. Claroc: "If an account from outside your company gets in, the app needs a list of who may use it."
  4. Read what the browser downloads. Claroc's advice: "Search the scripts an app loads for names, emails and passwords". Passwords in client-side code are public the moment the page loads.
  5. Unpublish what nobody owns. Per Claroc, "unpublishing takes a grok.me app offline at once".

Block or allow?

Blocking every AI app builder is the simplest rule to write. In our view, a blanket block moves the work to personal phones and home laptops, where the business sees nothing. Allowing everyone leaves the builder's default to decide who can read your customer list.

The middle option keeps the tool and puts a name on every app: allow the people who need a builder, check what goes into it, and keep a record of who used which builder.

Know what leaves your business on the web, and secure it.

Which AI app builders did your staff open last month, and could you list the apps they published?


Sources

Top comments (0)