Vibe-Coded App Risk Report — Week of Nov 9, 2026: Is Your AI-Built App Public?
Last week was about leaked keys. This week added a simpler question: is your AI-built app public? For tens of thousands of apps made with one popular builder, the answer was yes, and many of their owners didn’t know.
Here are the stories from the week of November 9 that matter to a business running on an app built with Lovable, Bolt, Replit, Base44, v0, Grok, Cursor, Claude Code or a freelancer using them, with one action for each.
Is your AI-built app public? 35,578 Grok Build apps were
On November 10, the security firm Claroc reported that of 37,571 apps made with Grok Build, the app builder from SpaceXSI, 35,578 opened for anyone, with no sign-in. Most were harmless: games, landing pages, calculators. But Claroc says about one in ten contained internal business or personal data, and roughly 2% held material it rated high or critical.
The examples are the kind of tools a small or mid-sized business builds for itself. According to The Hacker News, they included a hospital group’s searchable list of more than 3,500 employees, a fire department’s live shift board, a sales territory map, and a contractor’s timesheet app whose code held every employee’s password in plain text. Claroc identified 30 organizations beyond SpaceXSI itself, from construction and energy to healthcare and defense; six are Fortune 500 companies.
The cause was a sharing setting, not a hack. When the researchers published an app from their paid account, “Anyone with the link” was already selected. SpaceXSI told reporters that apps stay private until their creator shares them and that employee accounts default to “Only you.” It took down 24 apps built by its own staff, but not other users’ apps. The researchers have asked for “Only you” as the default.
What it means for a business: an app link is not a lock. The researchers found these app addresses through public internet records, by pattern, so “nobody knows the link” is not protection. Apps that hand out data without a sign-in have been reported on other builders too; for Lovable, see is my Lovable app leaking data?
Action: list every app anyone on your team has built with an AI builder. Open each one in a private browser window, logged out. If you see anything internal, switch it to invited users only, or unpublish it if nobody owns it. Then try signing in with an account from outside your company: if it gets in, the app needs an access list.
Claude Code’s “don’t ask again” put passwords on GitHub
On November 7, reporting on research by Apiiro showed that Claude Code’s “Yes, and don’t ask again” option saves the approved command, including any password or key typed into it, to a settings file that can end up in a public code repository. Apiiro found real secrets in 1,122 public copies of that file, including 379 database passwords. We wrote up the details and the safe order to fix it in our guide to the Claude Code secrets leak.
Action: if anyone who works on your app uses Claude Code, ask whether .claude/ is in the project’s .gitignore and whether that folder was ever committed. If it was, replace the keys in it first, then clean up.
Hijacked GitHub accounts pushed a secret stealer into repositories
A campaign that security researchers call wfx began on November 10. Attackers used hijacked GitHub accounts to push code into repositories those accounts could change, so that the repository’s automated build (GitHub Actions) would run it. According to Aikido’s count, as summarized by the Cloud Security Alliance, 4,837 accounts were compromised and 61,764 repositories targeted, with the stealer confirmed to have run in at least 1,806. It collects the secrets stored for those builds, along with keys for AI services such as OpenAI, Anthropic and Gemini.
What it means for a business: most AI-built apps that outgrow the builder end up in a GitHub repository, and the keys for deploying them often sit in that repository’s settings. Anyone with write access to it, including a freelancer whose account is taken over, can be the way in.
Action: ask whoever maintains your repository to check for commits, pull requests or workflow files since November 10 that nobody on your side made. If anything ran, replace every secret stored in GitHub Actions, using the order in how to rotate API keys after a breach. Then remove access for anyone who no longer works on the app and require two-factor sign-in for everyone who does.
Why public apps and leaked keys keep showing up together
The three stories share one pattern. AI builders make it fast to publish, connect services and approve commands, and the safe choice is rarely the default. None of it requires a rebuild to fix. It needs someone to own the list of apps, the list of keys and the list of people with access. In last week’s report we showed how quickly a leaked key turns into a bill; this week shows how quietly an app becomes public.
Dates ahead
- November 19: Lovable’s Gemini 3.6 Flash model stops working for app AI features. Apps still using it need to switch to a newer model.
- November 30: Vercel Marketplace starts labelling vendors “Not secure” if they still rely on long-lived secrets instead of short-lived credentials.
- December 31: Google’s Jules coding agent, read-only since November 11, shuts down. Anything a freelancer kept only in Jules needs to be in your own repository before then.
This week’s checklist
- List every app built with an AI builder in your business, and who owns each one.
- Open each app logged out in a private window. Nothing internal should appear.
- Set internal apps to invited users only, and unpublish apps nobody owns.
- Ask whether Claude Code is used on your app, and whether
.claude/has ever been committed. - Check your GitHub repository for changes since November 10 that nobody on your side made.
- Remove repository access for people who have left, and turn on two-factor sign-in for the rest.
If you’d like an outside view, our free Forward Scan shows the three biggest risks in an AI-built app, and who can open it without signing in is one of the first things we check.
Sources
- Claroc: GhostShares, Grok Build apps (November 10, 2026)
- The Hacker News: Over 35,000 Grok-built apps exposed online (November 11, 2026)
- Engadget: A Grok vibe-coding agent leaked sensitive SpaceXSI data (November 11, 2026)
- Cloud Security Alliance: CISO Daily Briefing, November 11, 2026
- The Hacker News: Claude Code’s “Don’t Ask Again” file (November 7, 2026)
- Aikido: Compromised GitHub accounts push CI secret stealer to tens of thousands of repositories (November 2026)
- Cloud Security Alliance: CISO Daily Briefing, November 12, 2026
- Help Net Security: A secret stealer hit tens of thousands of GitHub repos (November 12, 2026)
- Vercel: Death to long-lived static credentials
- Google Jules changelog (October 29, 2026)
- Lovable changelog