bubble security incident what to check

Bubble Security: an Attacker Reached Its Production Systems. Here’s What to Check in Your App.

TL;DR: An attacker got into Bubble’s production systems on 26 October, and Bubble published a preliminary root-cause analysis on 6 November saying the attempts “are still active”. Bubble has contacted every customer it believes needs to act. If it has not contacted you, the bubble security work is short: run the security dashboard, check your privacy rules, and make sure your editor is private. The one line everyone is misreading is further down.

The bubble security incident, as Bubble tells it

Two bubble security documents matter, both Bubble’s own. Co-founder Joshua Haas wrote on 3 November that “since mid-October, an AI-powered threat actor has targeted Bubble and the apps we host”, and that “on Monday, Oct 26th, they managed to get partial access to our production systems.” Then on 6 November Bubble published a preliminary root-cause analysis with a dated timeline.

The way in, in Bubble’s words: “an attacker obtained temporary internal credentials by exploiting a security vulnerability in our platform as well as part of our infrastructure that required updates.” Those temporary credentials led to further internal credentials, which led to other internal systems.

What they reached:

  • Plugin developers’ credentials. The attacker “read private plugin data, including credentials that plugin developers had saved in the plugin editor.” Those developers were emailed on 26 October and asked to change them.
  • Some individual apps, attacked directly. “In certain cases they accessed app data or stored credentials.” Bubble is contacting those owners one by one.
  • Internal configuration, again on 30–31 October, using credentials taken earlier. Bubble detected it and rotated them. Attempts to sign in to Bubble accounts with that configuration “returned no data”.

Bubble engaged an outside forensics firm on 27 October, and says its preliminary findings are consistent so far. Service disruption along the way: several hours on 26 October affecting plugins, file uploads, PDFs, mobile deploys and AI app generation, and a roughly 35-minute outage on 30 October from a rolled-back deploy.

The bubble security sentence people are misreading

Bubble’s RCA says this, and it is being quoted as the all-clear:

“So far, our review has not shown that the attacker’s access to our internal systems was used to read our application databases or the data and files in your apps (in other words, your users’ data).”

Read the scope. That sentence is about the internal-systems route. It is not a statement that no app data was touched — because the same document says the attacker also went at individual apps directly, and “in certain cases they accessed app data or stored credentials.”

Two routes, two different bubble security answers. Bubble has not claimed your users’ data is safe in general; it has said the internal breach has not been shown to have read app databases, and that where individual apps were reached, it is contacting those owners. Bubble also lists “the full scope of what was accessed” as still being verified.

And the second route is the uncomfortable one for anyone who builds this way. Bubble says the attacker got into some apps by exploiting platform issues “even when the app was set up correctly” — but also by looking for apps whose own settings, “such as its privacy rules, which may be set up that way on purpose, granted them access.” In plain English: some apps were open because of how they had been configured, and the attacker simply walked in.

Why this matters if you don’t code

Privacy rules are the part of bubble security that decides who can see which data. They are also the part that is easiest to leave loose while you are building and never tighten before launch. This incident has turned that from a tidiness problem into a live bubble security problem.

It is the same failure we wrote about in the app you built and forgot: the software keeps running, the configuration keeps whatever you last set, and nobody looks again. The difference here is that someone is actively looking on your behalf — just not helpfully.

If “privacy rules” and “API connector” mean little to you, our vibe coding glossary covers the vocabulary.

Your bubble security checklist

Bubble’s own guidance splits on one question: did they contact you?

If Bubble emailed you, follow the steps in that message. Bubble adds that it “should also help inform what you tell your app’s users” — which is Bubble saying, politely, that telling your users may be your job.

If Bubble did not contact you, it says to take routine precautions and otherwise carry on. Specifically:

  1. Run the bubble security dashboard on every app you own — at `bubble.io/security-dashboard` — and fix what it flags. It runs structured checks for things like credentials not marked private, misconfigured API connector calls, and privacy rules with holes in them.
  2. Review your privacy rules. This is the one that let the attacker into some apps. Check what an unauthenticated visitor can actually see.
  3. Check your API keys are marked private and that API Connector calls are set up correctly.
  4. Set your app to private unless you mean the editor to be public. Bubble’s warning is blunt: “A public editor lets anyone view the app’s settings and data, including stored keys.”

One thing Bubble’s bubble security guidance does not tell general app owners to do is rotate their API keys. Plugin developers were asked to; everyone else was not. We would rotate anything genuinely sensitive anyway — it costs an afternoon and the full scope is still being verified.

Who should care (and who shouldn’t)

  • Running a live Bubble app: care most, today. Work the four bubble security steps above even if you were not contacted.
  • Bubble app with real customer data in it: care, and read your contact email carefully if you got one. You may have a notification duty of your own.
  • Plugin developer on Bubble: your editor credentials were in scope. If you have not changed them since 26 October, change them.
  • Building elsewhere — Lovable, Replit, Cursor: not directly affected, but the bubble security lesson about privacy rules travels. Go and look at yours.
  • No idea yet: the 60-second Tool Finder quiz will help you pick a tool whose security model you can actually hold in your head.

Our take

Bubble’s handling of this bubble security incident is better than the industry norm: a named co-founder, a dated timeline, an outside firm, an explicit list of what is still unverified, and a plain admission that attempts are ongoing. Compare that with the vendors who say “we take security seriously” and nothing else. We are not telling anyone to leave Bubble over this, and we said much the same when its Starter pricing changed — judge the platform on how it behaves when things go wrong.

What we would push back on is the framing. “AI-powered threat actor” is Bubble’s label, and its stated basis is behavioural — the attacker “doesn’t feel like it’s a human”. That may well be right, and it may also be the most flattering available description of being breached. It does not change what you have to do. The route into some apps was privacy rules left open, which is the oldest problem in no-code and needs no AI at all.

Not sure which builder’s security model suits you? Take the 60-second Tool Finder quiz →

Some links on this page are affiliate links. If you buy through them we may earn a commission at no extra cost to you.

FAQ

Was my Bubble app’s data stolen?

Bubble says its review has not shown the internal-systems access being used to read app databases or your users’ data. Separately it says some individual apps were reached directly and in certain cases app data or stored credentials were accessed — and it is contacting those owners. The full scope is still being verified.

What bubble security steps should I take now?

If Bubble contacted you, follow its email. Otherwise: run the security dashboard on each app, review your privacy rules, confirm API keys are marked private, and set your app to private unless the editor is meant to be public.

Is the attack over?

No. Bubble’s 6 November update says attempts on its systems “are still active, and we continue to block or contain them”. A final root-cause analysis is promised once the outside forensics work finishes.

Similar Posts