SE Bug Bounty Arena / Hunting with AI / Lesson 1

Lesson 1 of 6

Where an AI assistant helps a bug hunter, and where it hurts

An AI assistant is the fastest reader and the most confident liar on your team. This lesson sets the rules I hunt by, so it saves you hours without costing you a report.

  • 6 min read
  • Free

In this lesson

  1. What it is good atRead
  2. What it is bad atRead
  3. Three rulesRead
  4. 2 prompts to copyCopy
  5. Three-question check+20 XP

What it is good at

Reading. Give an assistant a long scope page, an API reference or a few hundred lines of code and it will tell you what is there in seconds. It is also good at lists: features to test, questions to ask, things you have not tried yet.

It is a strong editor too. It can turn rough notes into a clear report, as long as every fact in that report came from you.

What it is bad at

Facts it has not been shown. An assistant will describe an endpoint that does not exist, a version that was never released, or a response it never saw, and it will sound exactly as sure as when it is right.

It also cannot test anything. It has not seen the target. Whatever it says about how the application behaves is a guess until you check it yourself.

Three rules

One: stay in scope. The program decides what you may test and which tools you may use. Some programs limit or forbid automated tools, and an assistant acting for you counts.

Two: protect what you paste. Do not paste secrets, tokens, or other people's personal data into an assistant. If you found something sensitive, describe it, do not copy it.

Three: verify before you believe. Treat every claim as a lead. A lead becomes a finding only when you have reproduced it by hand.

Prompts to copy

Replace anything in square brackets with your own material.

Set the working rules
I am doing authorised security testing on a bug bounty program. I will paste material for you to read. Rules for this chat:
- Tell me when you are inferring rather than reading from what I pasted.
- If you are unsure, say so instead of guessing.
- Do not invent endpoints, parameters or responses.
Confirm you understand, then wait for my first paste.
Ask for the weak points in an answer
Look at your last answer. Mark each statement as one of: (a) read directly from what I pasted, (b) inferred, (c) general knowledge that may not apply here. List the (b) and (c) items so I can check them by hand.
The mistake to avoidReporting something the assistant told you without reproducing it. Triagers see these every week, and they close fast.

Check yourself

Three questions. Sign in to save your progress and earn 20 XP.

1. An assistant tells you an endpoint is vulnerable. What is that?
2. You found a customer's personal details during testing. What goes into the assistant?
3. Who decides whether you may use automated tools on a target?