Audit your app like an attacker: every way to crash it, cheat it or abuse it
0xbobaa's 0xbobaa read-only attacker audit, the one that found the bug that had already taken his game's server down twice: your AI lists every way to crash, cheat or abuse your app, ranked by severity with file:line and a fix, checks your server logs for which ones already hit production, and makes the server re-check anything a client claims.
What your AI will deliver
- AUDIT.md: every way to crash, cheat or abuse the app, ranked critical, high, medium, low, each with file:line, evidence and a fix
- A log check marking which findings already happened in production, with dates
- Fixes for every critical and high finding, each with a test that failed before and passes after
- A re-audit of the changed code with the remaining findings listed
How it runs
In your AI, with your accounts. It starts by researching your business. How kits work ›
- 1. Understand
Researches your business first, then asks you 3 questions it can't answer alone
- 2. Choose
Nothing to choose: the kit follows one path
- 3. Build
4 steps, risky ones ask you first
- 4. Deliver
6 checks before delivery
Tools it uses
You pay each tool directly, not CloneKit. Your AI checks which ones you already have.
Details
What the creator's process is built on. Your AI loads them during the run.
- Source
- The app's repo
- Read-only access to production logs, if available
Reference files your AI can read during and after the work.
- Audit your app like an attackerREADME.md
- Read only during the audit: run nothing against production, send no requests to the live site.
- Only audit code the person owns or is allowed to test.
- No fix ships without the person's OK.
First version, based on 0xbobaa's 0xbobaa post.
Everyone running this kit gets updates. See changelog ›
- Type
- Delivery
- License
- Own use
- Uses
- 0
- Runs completed
- 0