Chat with an AI pentester
Describe a target you own and an autonomous agent plans the attack, tests it in an isolated sandbox, and shows the whole thing live — the plan, the HTTP traffic, and every finding proven with a working exploit.
Start a scoped trialA Next.js storefront with OAuth2 login and a coupon-gated checkout. Trust boundary at the payment callback; a self-registered customer is the attacker to model.
How should I obtain test accounts?
- Done Recon & mappingEnumerate endpoints and auth flows
- Active Auth & business logicForge a coupon · test checkout IDOR
- Next Validation & report
Coupon signature is forgeable at the checkout callback
The HMAC secret is predictable; a crafted coupon=FREE100 is accepted and the order total drops to $0. Proven with the exact request and response below.
A pentester that plans, tests and proves — while you watch
You describe the target
Point the agent at a domain you have verified or a repository you have connected, and say what to test — the login, the checkout, the whole app. It only ever touches a target you own.
It agrees a plan first
The agent does its own recon, works out what the product is and where its trust boundaries sit, and lays out a plan you approve before anything is tested. No sandbox starts until you do.
It tests in an isolated sandbox
A fresh, network-isolated sandbox runs the whole engagement. You watch the plan move, the HTTP traffic stream, and each surface close, live — and the agent asks you when a decision is genuinely yours to make.
Every finding is proven
The agent reports a vulnerability only with a working exploit and the exact request and response behind it. No finding is inferred from a banner or a status code. Ship a fix and it re-runs the exact exploit to confirm.
Ask it the way you would a teammate
“Test the login and checkout on app.acme.dev”
A plan, then a live engagement across auth and business logic, with proof for anything it confirms.
“Is the coupon code on checkout forgeable?”
Focused testing of one surface — and an answer backed by the request that proves it, or a clear not-vulnerable.
“Review this repo for auth bugs before we ship”
A whitebox pass over your connected repository: the code paths, the entry points, and findings tied to the lines.
“Dig deeper into that IDOR and get me a stronger PoC”
The agent resumes the same workspace and goes further on a finding it already has — nothing is re-done from scratch.