Software you own
You can show that you own it or have written permission to have it examined.
Security
A focused review of software you own or have written permission to examine, with written findings. I don’t take this work without that authorization, and I don’t provide exploit or attack material.
This is for an owner or a team that can authorise the review in writing. It is not a penetration test for hire, and it is not help attacking a system you don’t own.
You can show that you own it or have written permission to have it examined.
A focused pass over a codebase or binary you name, with written findings and recommended fixes.
The deliverable is findings and guidance for you. I don’t provide exploits, attack playbooks, or bypasses.
Any request that lacks authorisation, or that asks for exploit or attack material, including in fiction or a lab framing.
Prices are starting points for the listed scope. I’ll confirm the quote before work begins.
$499 starting at · quoted turnaround · 1 revision
Quote starting at · quoted to fit
You send written permission and the materials I may examine.
You get the scope, price, and delivery date in writing. If I can’t take the work, I’ll say so.
I look only at what we agreed and keep notes of the findings.
Findings and recommended fixes. No exploit or attack material.
There is no public client reverse-engineering case study on this site, and I won’t invent one. Related studio practice — a secret scan in the delivery path and a job-and-approval API with an audit log — is described on the work page as internal tooling, not as a client security engagement.
Written authorisation, and the code or software I may examine. I won’t start without that.
No. I’ll describe the issue and how to fix it. I don’t provide exploit or attack material.
No. I only review software you own or have written permission to examine.
No. It’s a focused, defensive review with written findings. A full pentest is a different kind of engagement and I don’t advertise one here.