SE Bug Bounty Arena / Hunting with AI / Lesson 2

Lesson 2 of 6

Read a bug bounty program in five minutes

Most wasted hours in bug bounty are spent on things that were never in scope. Here is how I use an assistant to read a program properly before I touch the target.

  • 7 min read
  • Free

In this lesson

  1. Paste the whole briefRead
  2. Find the AI-specific rulesRead
  3. Turn it into a test planRead
  4. 3 prompts to copyCopy
  5. Three-question check+20 XP

Paste the whole brief

Copy the program page in full: scope, exclusions, rules, severity table and reward table. Ask for a digest, not a summary. You want lists you can act on, not a paragraph that sounds helpful.

The digest I ask for has four parts: what is in scope, what is out, what the program says it does not pay for, and anything that is ambiguous.

Find the AI-specific rules

Programs with AI features increasingly say how they treat them. Some pay only when a prompt attack leads to something else, such as data access. Some exclude jailbreaks and model "safety" issues completely. Some name the assistant as its own asset.

Ask the assistant to pull out every sentence about AI, models, chatbots or prompts. If there are none, that is worth knowing too: ask the program before you assume.

Turn it into a test plan

With the digest in hand, ask for a short plan: which in-scope assets have an AI feature, what each feature can reach, and which bug classes fit. This is where the hunter path helps, because each class tells you what evidence to look for.

Keep the digest open while you hunt. When you find something, check it against the exclusions before you spend an evening on the report.

Prompts to copy

Replace anything in square brackets with your own material.

Scope digest
Below is the full text of a bug bounty program page. Produce four lists, using only this text:
1. In scope (asset, and any conditions)
2. Out of scope
3. Findings the program says it will not pay for
4. Anything ambiguous or missing that I should ask about
Quote the exact sentence next to each item.

[paste the program page]
AI rules only
From the same text, quote every sentence that mentions AI, LLMs, models, chatbots, assistants or prompts. Then tell me in one line each: is a prompt injection with no further impact accepted here? Is a jailbreak accepted? If the text does not say, answer "not stated".
First test plan
Using the digest, list the in-scope features that appear to use an AI model. For each one give: what it can read, what actions it can take, and the three bug classes I should test first. Mark anything you are guessing.
The mistake to avoidAsking for a "summary" of the scope. Summaries drop the exclusions, and the exclusions are the part that costs you.

Check yourself

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

1. Why ask for the exact sentence next to each scope item?
2. A program page says nothing about AI features. What do you do?
3. When should you check a finding against the exclusions?