35,578 Grok Build Apps Opened for Anyone With the Link, Including SpaceXSI’s Own Sales Plans
Claroc Research found 35,578 of 37,571 live Grok Build apps open without sign-in. Twenty-four were built by SpaceXSI and X staff, including confidential sales plans and ad proposals.

Claroc Research tried 43,551 web addresses under grok.me on 8 November 2026. Of the 37,571 apps still online, 35,578 opened for anyone with the link and no sign-in, a rate of 94.7 percent, the security firm said in a report published on 10 November.
Twenty-four open apps were built by staff at SpaceXSI, formed by the SpaceX and xAI merger, and at X. They included a confidential onboarding plan, a sales territory map covering 594 accounts, eight advertising proposals, and four live advertiser boards with campaign spend.
Claroc reported it to SpaceXSI on 8 November and got no reply. SpaceXSI removed the 24 staff apps after Ars Technica asked questions, and all 24 returned an app not found error at publication. Apps built by other Grok users stayed open.
Quick answer: Grok Build gives every published app its own hostname under grok.me, and the random part of that name reaches DNS, where anyone can index it. Claroc found 35,578 of 37,571 live apps open without authentication. In the paid account it tested, the publish panel had Anyone with the link already selected, and a team app Grok built let an uninvited Google account read, edit and delete customer records.
What Claroc actually counted
It did not guess links or crack passwords. It used subdomain discovery to list names under grok.me, opened the first page of each app once with no account, and read the saved copies offline.
Of 43,551 addresses it tried, 37,571 were live. Of those, 35,578 returned content, while 1,993 returned HTTP 401, the response an app set to Only you or Invited users gives a stranger.
Most were games, landing pages and calculators. Claroc estimates about one in ten held sensitive material, and roughly two percent rated high or critical. After hand checks against a sample, it puts apps with private data at roughly 650 to 800.
The flaw sits in the hostname, not the password
A Grok Build app is published at an address such as cinder-crane-sand-frost.grok.me. The four words are unguessable. But the name is a domain, so the first time anyone opens the link, a DNS resolver sees the query.
Passive DNS services collect those queries and let customers search them by pattern. Nobody has to guess a name when a commercial index lists every name under a domain.
The comparison is fair. Claude artifacts, ChatGPT shared conversations and Gemini shared links put the secret in the URL path, so DNS never sees it. Grok put it in the hostname, where it leaks by design.
SpaceXSI’s own apps were the loudest example
The onboarding plan listed the systems a new sales hire should access in week one, the internal chat channels to join and a 30-day plan. It was marked confidential and asked for no sign-in.
The territory map held 594 strategic accounts and pipeline data. Advertising material included proposals to advertisers in Brazil, Japan, Korea and Thailand, and one proposal to a US federal agency marked confidential.
SpaceXSI told a reporter that employee accounts default to Only you, so publishing one publicly takes an extra switch. Claroc agrees nothing goes live until someone clicks Publish. Its point is that the access step still ends with everyone selected, and 24 employees did it anyway.
The default is the real story
Claroc built two apps with invented data to test what Grok does when nobody specifies security. In its paid account, the publish panel offered Anyone with the link, Invited users and Only you, with Anyone with the link already chosen.
The first test app was a contact list with a database and no login. From an incognito window, Claroc added a row that the next visitor could see. That is write access for anyone who finds the name, not just a read leak.
The second was a customer list for a four-person sales team. Grok added Google and X sign-in on its own, which sounds responsible. But the code it wrote adds every person who signs in to the team before checking whether they belong, so an uninvited Google account read every customer, changed one record and deleted another.
Grok has the right controls. Switched to Only you, the first app returned 401 to a stranger, and unpublishing took the second offline within seconds. They are not the default, and nothing at publish warns that an app with a database and no login is open to the world.
How the platforms handle a shared app
| Platform | Where the secret sits | What a stranger gets |
|---|---|---|
| Grok Build | Random words in the hostname, under grok.me | Open app by default, findable through passive DNS |
| ChatGPT apps | App name and username in a two level hostname | Only me by default, so a found name still asks for sign-in |
| Claude artifacts | Random ID in the URL path | Path secret is not exposed to DNS, but can still be indexed |
| ChatGPT shared chats, Gemini shares | Random ID in the URL path | Path secret stays out of DNS; search indexing remains a risk |
Confirmed vs Not Confirmed
| Claim | Status |
|---|---|
| 35,578 of 37,571 live Grok Build apps opened without sign-in | Confirmed by Claroc’s published method and counts |
| 24 open apps were built by SpaceXSI and X staff | Confirmed by Claroc; SpaceXSI removed them after press questions |
| Publish panel defaults to Anyone with the link for paid accounts | Confirmed in Claroc’s own account, not a universal sample |
| Any visitor could edit data in other people’s apps | Not confirmed. Claroc tested writes only on its own two apps |
| 650 to 800 apps hold private data | Estimate from an AI classifier plus a hand checked sample |
| SpaceXSI will change the default or notify affected owners | Not confirmed. It did not commit to either in its replies |
What it means for Indian developers
Many Indian developers use vibe coding tools for client work, dashboards and sales trackers. The publish button is a data transfer decision, not a deployment detail. Claude Code users learned a similar lesson in November.
If an app holds customer names, phone numbers, invoices or employee records, the builder is processing personal data. Under India’s Digital Personal Data Protection Act, a business must use reasonable security safeguards and report a personal data breach to the Data Protection Board and to affected people.
The test is simple. Open the app in an incognito window with no account. If it loads, the data is public, whatever the link looks like. Then check the browser script files for keys and passwords; Claroc found one timesheet with 18 plain text passwords in code every visitor downloads.
Teams should also decide who owns an AI-built app after the person who prompted it leaves. The app keeps running, the data keeps changing, and nobody is watching the access setting.
What Grok could change
Claroc sent SpaceXSI four fixes: serve shared apps on a hard to guess path under one host, add an option limited to a company email domain, make Only you the default and show who can open an app before it goes live, and warn at publish when an app stores data with no login.
None of those is exotic. Three are standard on competing platforms. The fourth is a dialog, cheaper than telling a hospital its staff roster is on the open web.
The number that matters is not 35,578. It is 24. If the company that builds Grok cannot keep its own sales plans out of its default sharing mode, every other team using the same button has the same problem.
Frequently asked questions
Is Grok Build leaking data right now?
The 24 SpaceXSI and X apps were taken down on 10 November. Apps from other users and organizations were still open at publication, so check yours in an incognito window.
Were the Grok Build links hacked?
No password was broken. App names were discovered through passive DNS and subdomain enumeration, then opened like any public page. The design made the links findable, not guessable.
Does Grok Build require sign-in to view a shared app?
Only if the builder chooses Only you or Invited users. In Claroc’s paid account, Anyone with the link was preselected, and 94.7 percent of live apps opened without authentication.
What should I do if I published a Grok app?
Open it in a private window. If it loads without sign-in, switch it to Invited users or Only you. Then remove passwords and keys from any script the browser downloads.
Did SpaceXSI deny the findings?
No. It said apps are private until shared and publishing takes several steps. It did not dispute the counts and removed its own staff apps after Ars Technica asked.
Sources
Claroc Research, “GhostShares 2: Grok Apps Exposed xAI’s Business Secrets and People’s Private Data”, 10 November 2026. blog.claroc.io
Dan Goodin, “Grok Build coding agent leaks oodles of confidential info, some belonging to SpaceXSI”, Ars Technica, 10 November 2026. arstechnica.com
India, Digital Personal Data Protection Act 2023, accessed 11 November 2026. meity.gov.in