Short answer: an employee can now describe an app in an AI chat and publish it in an hour, with a database and a web address. On 10 November, researchers reported 35,578 apps built this way with Grok that anyone could open, some holding staff lists, a patient briefing and plaintext passwords. If your team builds tools like this, the useful question is who else can open it.
What the researchers found
On 10 November 2026, security firm Claroc published its study of apps people build by describing them to Grok, the AI assistant from SpaceXSI (formerly xAI). It tried 43,551 app addresses. Of the 37,571 still online, 35,578 (94.7%) opened for anyone, with no sign-in. Only 1,993 returned the error an app set to private would give.
Most of the open apps were games, landing pages and calculators. Claroc says about 1 in 10 held internal business or personal data. The ones it confirmed by hand included a hospital group's searchable roster of more than 3,500 employees, an intensive care briefing for a single patient, a trucking firm's recruiting list of over a thousand people with personal email addresses, and a contractor's timesheet whose code held 18 accounts with their passwords in plain text.
The maker's own staff weren't spared. Claroc found 24 open apps built by SpaceXSI and X employees, including a confidential onboarding plan and a sales territory map of 594 accounts. Claroc says the company took those 24 down after its report but not other users' apps. As The Hacker News relays from the researchers, the company told a reporter that Grok apps stay private until their creator shares them, that publishing takes several steps including a choice of access and a legal disclaimer, and that employee accounts start on "Only you".
The Cloud Security Alliance's note on the study adds that it hasn't independently verified Claroc's figures, so treat them as one firm's research. The pattern is still worth acting on, because it isn't new. The same note lists earlier cases at Lovable, Base44 and Meta's Muse.
Three ways an app built in a chat ends up public
None of these needed anyone to break in.
The setting said "anyone". Nothing went public until the person clicked Publish. But in Claroc's account, the access panel that opened at that point had "Anyone with the link" already selected, next to "Invited users" and "Only you". It's easy to click through a default. When Claroc switched its test app to "Only you", strangers got an error page.
The address wasn't secret. Each Grok app gets its own web address under grok.me. Every time someone opens it, their computer looks the name up in DNS, and passive DNS services record those lookups and let account holders search them. Grok suggests four random words as a name, and about half the names Claroc saw were exactly that. Such a name is hard to guess, but nobody has to guess it once it's in a list.
The login didn't check anything. Claroc built a customer list for a pretend four-person sales team. Grok added "Continue with Google" sign-in on its own, but the code it wrote added each person who signed in to the team before checking whether they belonged. An uninvited Google account viewed every customer, edited one record and deleted another. A login screen looked like protection and wasn't.
Defaults differ by tool. When Claroc shared an app built in ChatGPT, access was set to "Only me" until they changed it. So "which builder" matters less than "what did the person pick when they published".
Why this lands on an owner's desk
The people building these apps are often not engineers. The CSA note describes them as analysts, sales staff, clinicians and operations managers, the people who know exactly which spreadsheet they're tired of. That is the good part. A sales head who builds a pipeline tracker over lunch has solved a real problem.
The risk is that the data in that tracker now lives outside your email system, your file permissions and your list of software, with nobody responsible for it. In an Indian business that usually means customer phone numbers, staff details, quotes and payment status. The data doesn't become less yours because an AI built the screen around it.
A one-week check for your team
You don't need a security team for this. You need a list and an hour of someone's time.
- Ask who has published an app. Send one message to managers: which AI tools have you used to build an app or dashboard that has a web link? Claroc, which sells tools to secure apps like these, names Grok, Lovable, Replit, v0, Bolt, Base44 and Google AI Studio as builders staff can use with no IT setup or company account. You'll hear about apps you didn't know existed.
- Open each link while signed out. Use a private browser window. If the app opens and shows real data, it's public. Change it to invited users or "Only you", or unpublish it, then open it signed out again to confirm you now get an error.
- Try to sign in as an outsider. For any app with a login, sign in with a personal account that wasn't invited. If it gets in, the app needs a proper list of who is allowed.
- Look for passwords and keys in the app. Claroc's timesheet example handed every visitor's browser a file with passwords in it. If you find any credential this way, change it, because it was readable while the app was open.
- Give each app an owner. One named person, what data it holds, and a date to review it. Apps with no owner get unpublished.
Then write one line into your company's AI use policy: apps built with AI that hold company or customer data are shared with invited people only, and every published app has an owner.
Keep building, just check the door
Building small tools in an afternoon is one of the most useful things AI gives a business right now, and banning it tends to push the apps somewhere you can't see them. The gap the Grok study shows is narrow and fixable: the tool made publishing easy and left the "who can open this" decision to a preselected button and to code nobody read. That decision is a person's job, and it takes a minute per app.
Arthat AI
Working on something similar at your company?
Arthat AI builds these automations for Indian businesses every week. If you want to talk through whether this fits your situation, we'll give you a straight answer — even if the answer is "don't build it."


