All posts
2 min readby Romiel Inolino

Claroc found 35,578 Grok Build apps that opened for anyone, including 24 from SpaceXSI staff. Audit what your team publishes with AI app builders

AI securityAI app buildersGrokdata privacyinternal tools

The fastest way to build an internal tool is now also the fastest way to publish your customer list.

What happened

Security firm Claroc tried 43,551 Grok Build app addresses under grok.me. 37,571 were online, and 35,578 of those (94.7%) opened for anyone with no sign-in. 24 of the open apps were built by SpaceXSI and X staff, including a confidential onboarding plan, a sales territory map of 594 accounts and advertising proposals.

The cause is how the links work. Every published app gets its own hostname. When someone opens it, the DNS lookup lands in passive DNS datasets that anyone with an account can search. Random words in the name don't help when the dataset lists them. Claroc notes that Lovable, Replit, Bolt and other builders also give each app its own hostname, while shared chats on Claude, ChatGPT and Gemini keep the secret part in the path.

In Claroc's paid account, the publish step had "Anyone with the link" preselected. SpaceXSI disputes this and says apps are private until shared and employee accounts default to Only you. Claroc also built two test apps: one stored data with no login, so any visitor could change it, and a team app whose Google sign-in let an uninvited account read, edit and delete records. Among real apps it found a timesheet whose script held 18 accounts with plain-text passwords. Claroc says SpaceXSI took down its own 24 apps after the report, but not the apps other users left open.

My take

Your clients' staff are building these tools right now, often without telling IT. A sales manager builds a territory map in minutes and clicks Publish. Here is the audit I'd run:

  1. Ask which builders people use. Grok, Lovable, Replit, v0, Bolt and others need no admin rollout.
  2. Check the access setting on anything holding internal data, and open it from an incognito window to confirm a stranger gets an error.
  3. Test sign-in from outside the company. A login that checks who you are but not whether you belong is not access control.
  4. Read the scripts the browser downloads for names, emails and passwords.
  5. Unpublish what nobody owns.

When a tool touches customer data, it belongs behind real auth and connected to the CRM properly, not on a public hostname.

More posts