In July 2025 the Tea app's photo storage sat open to anyone with the link, and a stranger wrote a script that walked the folders and downloaded 72,000 images, including 13,000 verification selfies and government IDs.

Two class-action suits followed within days, and a second open database spilled 1.1 million private messages. The app's matching and posting worked fine. The failure sat one layer down, in storage nobody had locked.

TechCrunch and 404 Media, 2025, on the Tea breach

The images lived in a storage bucket that anyone on the internet could read.

The file paths were not secret, only unlisted, and the bucket even allowed directory listing. One script that walked the folder tree pulled every file in minutes.

The app's features worked. Three choices in the layers underneath did not.

A better model would not have prevented any of it, because none of the gaps were in a model. They were in the layers the build was assembled from.

Open storage and leaked keys are the common way AI-era builds break.

The dangerous layer is rarely the clever part of a build. It is the plumbing: a key in the browser, a database with no lock, a config nobody read.

GitGuardian, State of Secrets Sprawl 2025

Every product runs on the same seven layers, and a feature is only as safe as the layer you forgot to check.

The screen, the server, the API between them, the stored data, the rented computer, the sign-in, and the monitoring. Miss one and that is where the incident starts.

Four of the seven layers, one skill each.

"The coding tool handles the layers. That is the whole point of using it."

The tool builds each layer, but it does not decide which one holds your users' IDs or whether that store is locked. Tea's storage was reportedly generated with AI help and shipped without an audit, and the tool will build an open bucket just as readily as a closed one if nobody says which to make.

Understanding a layer is not writing its code. It is knowing that anything the browser can reach is public, that a database needs its own lock, and that the choice the tool cannot make for you is the one that breaks.

Each gap in this story has a chapter that closes it.

Check the layer before you approve it, and the open bucket never ships.

Every gap in this story is a chapter here.

Seven chapters walk the layers every product is built from, from the screen down to monitoring, so you can trace any build end to end, name where each feature must run and what it costs, and steer what a coding tool builds instead of rubber-stamping it. No engineering background needed.