Abbi Labs

Breach breakdowns

Breakdown: 35,578 Grok-built apps opened for anyone, because "anyone with the link" was the default and the links were in DNS

By Abbi Labs · Published 22 November 2026

What does a stranger see in your app?

The Abbi Labs quick check opens your live app as a signed-out visitor and looks for secret-looking keys in its JavaScript, exposed .env and .git files, and Supabase tables readable with your public key. It can't tell whether a page that opens was meant to be private, and it doesn't try signing in with a stranger's account, so do the checks below too. No sign-up.

No app handy?

No sign-up. Read-only public-resource and protocol metadata checks. No model prompts or tool execution. Scan only sites you own or are allowed to test.

Run on every deploy or use from Cursor / Claude Code via MCP →

Weekly AI-app security checklist

One short email a week: a practical check for apps built with Supabase, Next.js and AI tools (RLS, leaked keys, headers and more). Unsubscribe anytime.

Most AI app builders now end the same way: you describe the app, it works, you click Publish and get a link to share. On 10 November 2026, security firm Claroc published research on what happened to the apps people publish from Grok's chat-based builder. Of 37,571 Grok apps it found still online under grok.me, 35,578 (94.7%) opened for anyone, with no sign-in. Twenty-four of them were built by staff at SpaceXSI, the company that makes Grok, and at X.

Nobody needed to guess a link. Each app's random name is its own hostname, and hostnames end up in passive DNS databases that anyone with an account can search. Everything below comes from Claroc's report, with The Hacker News and Ars Technica as cross-checks. I'm not naming any of the other organisations or apps. Claroc didn't either.

What happened

The numbers

What's confirmed and what we don't know

Check the apps you've published

This works for any AI builder, not just Grok. Do it for every app you've ever shared a link to.

  1. Make a list. Every app you've published from Grok, Lovable, Replit, v0, Bolt, Base44, Google AI Studio or ChatGPT, including the "just for the team" ones and the old experiments. If nobody owns it any more, unpublish it.
  2. Open each one signed out. Use a private window, or from a terminal:
    curl -s -o /dev/null -w "%{http_code}\n" https://your-app.example/
    A private app should give you an error page (Claroc saw 401 for "Only you" on Grok). If you get 200 and the real app, so does everyone else.
  3. Assume the link is public. If a hostname has been opened even once, it can be in a passive DNS list. "Anyone with the link" means anyone. For anything internal, pick "Invited users" or "Only you".
  4. Check the data, not just the page. Open DevTools, go to Network, reload while signed out, and look at the data requests the page makes. Real records coming back without a sign-in means the data is open even if the page looks empty.
  5. Try a stranger's account. Sign in with a second Google account that isn't on the team. If it gets in, the app checks who you are but not whether you belong. The fix is an allowlist the owner controls, checked before granting anything. Illustrative, not Grok's actual code:
    // wrong: anyone who signs in is added first, so the check always passes
    await addToTeam(user.email);
    if (!isTeamMember(user.email)) return deny();
    
    // right: check a list the owner controls before granting anything
    const ALLOWED = new Set(["you@yourco.com", "teammate@yourco.com"]);
    if (!ALLOWED.has(user.email.toLowerCase())) return deny();
  6. Search the scripts for things that shouldn't be there. Everything in your JavaScript is downloaded by every visitor:
    curl -s https://your-app.example/ | grep -oE 'src="[^"]+\.js"'
    curl -s https://your-app.example/assets/index-XXXX.js \
      | grep -oiE '(password|passwd|secret|api[_-]?key|@[a-z0-9-]+\.(com|org))[^,;]{0,40}' | head
    Names, emails or passwords in there are public. Move them to a database behind sign-in, and change any password that was ever in the code.
  7. No sign-in plus a database means open writes. Claroc's test contact list let any visitor add rows. If an app stores data, either require sign-in or make it read-only for visitors.

Check what a signed-out visitor gets

Paste your app's URL and Abbi Labs looks at it the way a stranger would: secret-looking keys in your JavaScript, exposed .env and .git, open Supabase tables. Read-only. It won't know whether your roster was meant to be private, so steps 2 and 5 above are still on you.

Run a free scan

If you find an open app with real data

  1. Change the access setting or unpublish it first. On Grok, Claroc saw unpublishing take an app offline within seconds.
  2. Change any password or key that sat in the app's code. Hiding the app doesn't un-copy what was already downloaded.
  3. Work out what was in it and for how long. If it held personal data about customers, staff or patients, talk to whoever handles privacy at your organisation. That may be a notifiable breach where you are.
  4. Tell your security team about the builders people use. Claroc's point is that these tools need no IT rollout, so nobody else knows the apps exist.

My take

No one hacked anything here. The apps did what their settings said. The problem is a default that treats a random-looking name as a lock, when that name gets written into DNS the first time someone uses it. A sales map and a lunch poll get the same Publish button, and the person clicking it usually isn't thinking about passive DNS. Open every app you've published in a private window today. It takes a minute per app.

Scan your live app free

Sources

Related

Weekly AI-app security checklist

One short email a week: a practical check for apps built with Supabase, Next.js and AI tools (RLS, leaked keys, headers and more). Unsubscribe anytime.