About 72,000 images from the women-only dating-safety app Tea were exposed on 28 July 2025 after a cloud storage bucket was left open to the public. The data included 13,000 verification selfies and photo IDs plus around 59,000 other images, roughly 59 GB in total. A second exposed database leaked 1.1 million private messages between users.
What is going on
Tea stored user uploads in Firebase, a Google service that apps use to keep files and data in the cloud. Firebase decides who may read a file using settings called security rules. If those rules are left open, anyone who knows the address can list and download everything inside.
Think of a self-storage unit with the shutter rolled up and the aisle open to the street. Nothing is broken into; the contents are simply there for the taking.
That is what happened here. A script that automated the downloading of the files was posted on 4chan, which turned a quiet misconfiguration into a mass download.
Who is affected
Tea's users are affected directly, in particular those who sent a selfie and a photo ID to verify their account.
The wider lesson reaches further. Any app or website that uses Firebase or Google Cloud storage for user uploads faces the same risk of mass exposure. There is no vulnerable version to patch, because the problem is a configuration choice, not a software flaw.
Sites that collect identity documents, customer photos, invoices or signed contracts carry the most sensitive exposure if a bucket is left open.
What to do now
- Set your Firebase Storage and Database security rules so that only the authenticated owner of a file can read or write it. Public read access should be the exception, never the default.
- Delete verification images such as selfies and ID scans once they have been processed. Data you no longer hold cannot leak.
- Audit old and legacy storage buckets, including ones left over from prototypes, migrations or former developers.
- Check whether any upload folder can be listed. If you can open a file in a private browser window without logging in, so can anyone else.
- Keep a short written record of which buckets exist, what they hold and who may read them, so the next change does not reopen the door.
How to check your own site
Storage rules sit inside your cloud account, so start there. For the public side of your site, the free Website Security Check spots outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want deeper coverage of your own site, including exposed-file and secret checks, you can run a full scan against sites whose ownership you have verified.
Source: BleepingComputer, July 2025.
Comments
No comments yet.