Grok Build Data Leak: Thousands of Shared Apps Exposed

Here's something worth checking before your next coffee: an AI tool that builds apps for you in plain English has been quietly publishing what those apps contain. The Grok Build data leak, uncovered by security researchers, left internal business plans, medical records and employee rosters readable by anyone willing to follow a link — and a chunk of that data belonged to the very company that runs the platform.

Nobody hacked anything. No password was cracked. The apps were simply shared the way the tool was designed to share them, and that design had a hole in it big enough to drive a truck through.

What Happened: A Private Link That Wasn't Private

Grok Build is the coding agent from SpaceXSI — the name of the now-merged SpaceX and xAI. "Coding agent" sounds technical, but the idea is simple: you describe the app you want in ordinary words, and the AI writes it for you. A shared-expense tracker for your flat. A dashboard of client info for your sales team. Something you'd normally need a developer, a budget and three months to get.

Then Grok Build gives you a link so you can send your creation to other people. Those links are meant to be private. Grok generates them with long random web addresses, so only someone who already has the exact link can open the app. It's the digital version of an unlisted phone number.

That's the theory, anyway.

The Design Flaw That Undid All of It

A design decision by Grok Build's developers "completely torpedoes that objective," as Ars Technica put it. The random links can be enumerated — meaning a script can walk through them one after another, like trying every door in a hotel corridor where the room numbers are scrambled but the master list is lying on the front desk.

Except in rare cases, clicking one of those links opens the app and shows every last piece of data inside it. No login. No warning. No "are you sure?" screen.

What Claroc Found Behind Those Links

Claroc, a security firm, went looking and came back with thousands of live Grok Build projects that anyone could open. Its team was blunt about it in a Tuesday post: "We were shocked."

The most awkward part? Twenty-four of the exposed apps were built by SpaceXSI itself. Inside them: an onboarding plan marked confidential for a new member of the enterprise sales team, a sales territory map covering 594 accounts, internal system addresses for the sales team's tools, and advertising proposals.

"The company that makes Grok had its own internal material open to anyone holding the link," Claroc wrote. "Had the sales team bought a tool for this, it would have sat behind company sign-in, open only to the team. Built with AI, it went live open to anyone with the link."

The Companies Caught in the Blast

Claroc's sample of other affected organisations reads like a who's who of unforced errors:

• A Peruvian construction company — an occupational-health dashboard with 3,784 worker medical exams.

• Tesla — a service-centre scorecard naming 22 technicians, with productivity and bonus status.

• A US Navy ship engineering contractor — a roster of 108 people on a naval logistics support contract.

• A luxury cruise company — a galley checklist for a celebrity cruise line, crew listed by full name and employee ID.

• A healthcare company — a hospital staff app with roughly 3,565 employees by name and ID.

• A US IT services firm — a confidential proposal to a large retail customer, hardware bill of materials included.

• A Norwegian-Finnish aerospace and defence group — a load board and loading procedure for an explosives building at a US plant.

• A US home construction company — a sales call sheet with around 583 home-buyer prospects, budgets and financing notes.

• A Malaysian holding company — a project monitor covering 37 developments, profits and sales figures included.

• An auto transport company — a quote desk with roughly 4,000 vehicle-transport orders, prices and margins.

• A US data centre hosting provider — a confidential IP transit proposal to a European carrier.

Claroc alerted SpaceXSI on Sunday. Nobody answered. So a Claroc staffer took to X and tagged both Elon Musk and Grok manager Matt Palmer. SpaceXSI only started pulling links within a few hours of Ars Technica emailing over questions for its article — and by then, all 24 of its own apps returned an "app not found" error. Data belonging to the other users was still up.

What It Means for You

You don't have to run a Fortune 500 company to get burned here. The failure mode is the same at every scale: someone builds something useful, hits share, and assumes the link is a secret. It isn't.

At Home

Picture a shared household budget app, or a list of your kids' school contacts and pickup times, built in an afternoon because it was faster than a spreadsheet. You drop the link in a family group chat. Anyone who forwards that chat — or anyone who stumbles onto the link — sees everything, forever, until you remember to delete it. Most people never go back and delete it.

At Work

A team lead builds a quick tracker for client names, contract values and salaries, then shares it with four colleagues. That's exactly the SpaceXSI pattern: an internal document marked confidential, sitting behind a link instead of a sign-in. If your employer has an IT policy, this almost certainly breaks it.

For Your Business

Look at the home construction company: 583 prospects with budgets and financing notes. Or the auto transport firm: 4,000 orders with prices and margins. That's not embarrassing, that's commercially fatal. A competitor who finds that quote desk knows exactly how you price, which is game over in a margin business.

For Study

Colleges and tutoring outfits build student rosters, gradebooks and exam trackers with these tools because they're fast and cheap. The healthcare example — 3,565 employees by name and ID — is the same shape of mistake at a bigger scale. If you can name a person and identify them by number, you've created a privacy problem, not a convenience.

For Creative Work

Freelancers use vibe-coding tools to build client portals, mood boards and pitch trackers. A pitch tracker is a list of who you're talking to, what you're charging and what stage the deal is at. Send that link to one client and you've essentially handed them your entire pipeline.

For Your Income

If you sell anything — services, products, courses — you've probably got a lead list somewhere. Those lists are the most valuable thing you own. Randomised URLs feel private. They're only private until someone builds a script that walks the corridor.

How to Try It Right Now

The good news: the tool itself is still useful, and the fix is mostly about habits. Here's how to test an AI app builder without becoming the next case study.

1. Start free, and start with dummy data. If you want to see what an AI-built tool can do before committing, begin with free AI tools like MyKreaTool and use fake names, fake numbers and fake clients. Never test with real medical details, employee IDs or customer lists.

2. Name the tool honestly. Grok Build is the coding agent in question here. Try it on a throwaway project — a shopping list, a workout tracker — not on your sales pipeline.

3. Treat every share link as public. Before you send one, ask yourself: would I be fine if this link ended up on a forum? If the answer is no, don't share it.

4. Check whether the link needs a sign-in. Open it in a private browser window, logged out. If it opens, anyone can open it. This single test catches almost every version of this mistake.

5. Delete old links. Go through every app you've ever shared and revoke the ones you don't use. Most people have a graveyard of live links they've forgotten about.

6. Put a real gate in front of anything sensitive. If the app holds names, IDs, money or health information, it needs a proper login, not a secret URL.

Upsides and What Changes

Let's not pretend AI app builders are going away. The upside is genuine: a two-person company can now build an internal dashboard in an afternoon instead of hiring a developer for a month. That's real leverage, and it's why people keep using these tools despite the headlines.

What changes is the default. Expect app builders to start shipping with sign-in required by default, link expiry dates, and audit logs showing who opened what. Claroc's line about the sales team is the whole argument in one sentence: a bought tool would have sat behind company sign-in automatically. The AI version didn't, because convenience was the design goal and security was an afterthought.

The lesson for buyers is simpler than any of the tech: ask where the data lives and who can reach it, before you paste in anything real.

Limitations

It's worth being precise about what this research does and doesn't show. Claroc's finding is about enumeration and default link behaviour, not a break of Grok's encryption or a stolen password — and the source notes that in rare cases a link didn't expose everything. We also don't know the full scope: Claroc sampled thousands of projects, which isn't the same as counting every one. SpaceXSI moved fast once a journalist got involved and pulled all 24 of its own apps, but at the time of publication other users' data was still reachable, and the company hadn't publicly explained what went wrong or what it's changing. Nor is this uniquely an AI problem — plenty of no-code and website tools have shipped with the same "anyone with the link" default for years. The difference is that AI tools now build apps holding medical exams, staff rosters and pricing data in minutes, for people who've never had to think about access control before.

Conclusion and One Action for Today

Grok Build didn't get hacked; it got shared, at scale, by people who reasonably assumed a long random link was the same thing as a password. That assumption cost SpaceXSI's own sales team its confidential onboarding plan, and it could cost a small business its entire prospect list.

The action for today is one minute long: open every app or document you've ever shared by link in a private browser window, logged out. If it loads, delete it or lock it down. Do that before you build anything else — and read the sharing settings before you paste in a real customer's name.