Identified
Oct 27 · 12:38 AM
Bubble
Some Bubble functionality remains affected by security measures we introduced in response to a security incident.
**Containment**
We believe the attacker has been contained and is no longer active in our systems. Since our last update, we have seen no evidence of further access.
**Security impact of the attack**
Forensic work is ongoing to confirm the full extent of what was accessed. What we can report so far:
• At this time, we do not have evidence that the attacker accessed private data of apps hosted on Bubble, or any credentials stored inside non-public Bubble applications.
• The attacker was able to access metadata about Bubble plugins. This includes private API keys stored inside those plugins (often used by the plugin developer for testing that plugin). We have emailed the affected plugin developers to let them know that they should rotate potentially-exposed private keys.
• The attacker downloaded application data from apps that were set as publicly viewable (see Settings -> General -> "Define who can see and modify the app editor" in the Editor). Apps with this setting were already open to the public, so the attacker did not access any non-public data, but we recommend confirming that this setting is set to "Private app" on your app unless your intention is for the editor in your app to be open to the public.
**Service status**
Parts of Bubble, including the editor and live apps, remain affected by the measures we took to contain the attack. We’re actively bringing systems back online. We've restored full service for some apps; other apps have impacted functionality including file access, some plugins, and some users being able to access their editors.
Our next update will be by 9:30 pm ET