Replit app security audit
A typical Replit app talks to Postgres through its own server with full database rights, so nothing like RLS filters rows for you. Every route has to check who is asking. This check signs in as two of your users and tries each route with the other's ids, then shows you the request, the response and the fix. Five working days after access.
What gets checked on your app
- Server routes, one by one Each Express or similar route that reads or writes data, called as user A with user B's ids, on read, update and delete.
- What Replit's Security Agent leaves to you It audits code, dependencies and privacy issues before you publish. It does not sign in as two of your users and ask for each other's records.
- Secrets DATABASE_URL and API keys kept in Replit Secrets on the server, and nothing private reaching the browser bundle.
- Sign-in and payments Replit Auth or your own login, session handling, and Stripe webhooks verified against the raw request body.
What you receive
- The request sent and the response received for every check
- A short video of any request where one user gets another user's data
- Findings ranked by what a stranger could do, each with the fix
- A one-page note of what was tested and what was left out
- One recheck after you apply the priority fixes
- £449 off the fix invoice if the fix starts within 14 days
See a sample report from a real test, or watch the recording of user A reading user B's note.
Questions
Is Replit's Security Agent enough?
Run it and fix what it finds. It reviews code; it cannot know which rows belong to which of your users. The two-account test checks that on the running app.
Do you need my Replit login?
No. We need the live URL, read-only access to the code, and your written permission. We create our own two test users.
What if you find nothing?
You still get the request and response for each check. If a check in scope has none, you do not pay.
Your admin page is only hidden in the UI
The method is free. The check is the run, the evidence and the recheck. It is not a penetration test and does not certify the app as safe to launch.
Book before you launch
At checkout, add the app URL and the date you plan to turn on payments or let real users in. After payment, send read-only repository access and the signed permission. Run by David Salami. Full scope on the 5-Day Two-Account Check.