Moltbook records exposure
An app exposed 4.75 million records, including 1.5 million API tokens and 35,000 email addresses.
Finding
These files tell crawlers and researchers how to treat the site.
Good to know · About ten minutes
Debug routes, admin pages and leftover files survive because nothing links to them. Nothing needs to. Address lists are guessed thousands at a time by tools that cost nothing to run, and an admin route with no check in front of it was one of the causes of the Moltbook exposure.
These files tell crawlers and researchers how to treat the site.
GET https://example.com/admin returned 200
Every finding on a result carries a line like this one: the request that was made and the answer that came back. You can run the same request yourself and get the same answer, which is the point.
Nothing to do. A security.txt file gives researchers a way to reach you.
Prompt for your coding agent
Add a /.well-known/security.txt file with a contact address for reports.
A result gives you this prompt written for your builder, in its own dialect, and a batch prompt that carries every fix at once.
An app exposed 4.75 million records, including 1.5 million API tokens and 35,000 email addresses.
Run the free Launch Risk Check on your app
ShipReady is not a penetration test or a security certification. No automated check can prove an application is secure.
Last updated September 20, 2026