Moltbook records exposure
An app exposed 4.75 million records, including 1.5 million API tokens and 35,000 email addresses.
Finding
Requests for configuration and repository files came back empty or missing.
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.
Requests for configuration and repository files came back empty or missing.
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 change here.
Prompt for your coding agent
Keep configuration and repository files out of the deployed output.
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