Skip to content
Tutorials Center
My learning

Topics

Lesson 18 of 38 ยท Repeater and Intruder

Intruder Payloads, Processing and Grep

Choose Intruder payload types, apply payload processing rules, and use Grep Match and Grep Extract to turn thousands of responses into clear, useful signals.

An Intruder attack has two halves: what you send (the payloads) and how you recognise what came back (the results analysis). Beginners spend all their time on the first and get lost in a wall of near-identical rows. Professionals spend just as much time on the second, adding columns that make the answer pop out.

This lesson covers the payload types, the rules that transform payloads on the fly, and Grep - Match and Grep - Extract, which add those revealing columns.

Payload sets and types

In the Payloads tab you pick a payload set (one per position for pitchfork and cluster bomb) and a payload type. The common ones:

Type What it generates Typical use
Simple list Items you paste or load Lists of IDs, file names, inputs
Runtime file Reads items from a file at run time Very large lists
Numbers A numeric range with a step and format Sequential IDs: 1000 to 1100
Dates A range of dates in a chosen format Date parameters
Custom iterator Combines several lists with separators Structured values like AB-1234
Character substitution Swaps letters for look-alikes Variations of a word
Case modification Changes capitalisation Testing case sensitivity
Null payloads Empty payloads, n times Repeating a request (for example to test rate limits or timing)
Brute forcer All strings from a character set up to a length Short codes in a lab
Recursive grep, Extension-generated Values taken from earlier responses, or from an extension Multi-step flows

The paid edition includes built-in lists; in Community you supply your own wordlist.

Prefer small, thoughtful lists

Ten well-chosen values beat ten thousand random ones. For an input-handling test, a short list of boundary cases (empty, zero, negative, very long, special characters, wrong type) finds most validation gaps. For identifier testing, a numeric range around your own ID is enough to show the weakness.

Payload processing

Under Payload processing you add rules that change each payload before it is sent, in order:

  • Add prefix / Add suffix: attach fixed text (for example user-).
  • Match / Replace: regex replace within the payload.
  • Encode / Decode: URL, HTML, Base64 and others.
  • Hash: send the MD5 or SHA digest of the payload.
  • Skip if matches regex: drop payloads that fit a pattern.
  • Reverse substring, Invoke Burp extension, and more.

Use Payload encoding (just below) to URL-encode special characters in the final value so they are not misread by the server, a common source of "my test did nothing" confusion.

Grep - Match: flag interesting responses

In Settings for the attack (the Grep - Match section), enter words or regular expressions. Intruder adds a column with a tick for each response that contains the text. Typical flags:

  • Welcome, Dashboard, Logout: signs of a successful login in a lab.
  • Invalid, incorrect, locked: failure and lockout messages.
  • Traceback, SQL, Exception: verbose errors.

Combine with sorting by status and length and the one interesting row is usually obvious.

Grep - Extract: pull a value out of every response

Grep - Extract defines a region (by regex, or by selecting text in a response) and adds a column showing that region's text for each response. It is perfect for:

  • reading a user's name or a balance from each response,
  • extracting an error code,
  • following a counter or token that changes.

For flows where a one-time CSRF token must be copied from one response into the next request, Burp offers Recursive grep (a payload type) or session-handling rules; both let Intruder carry a token along.

Choosing columns that matter

Column Reveals
Status Different handling (200 vs 302 vs 403)
Length Different content
Response time Different code path (a database lookup, a slow hash)
Grep match A word that appears only on success
Grep extract The actual value of interest

Try it: payload generators and processing

A stand-in with a numbers generator, a custom iterator and processing rules (prefix, URL-encode, hash), so you can see what the final payloads look like.

Python Stand-in: payload generators and processing

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Try it: grep match and extract on fake responses

A second stand-in simulates a lab login endpoint, runs a small wordlist, and adds match and extract columns, the same way Intruder's Grep tools work. The fake app has a known test account, so no real system is involved.

Python Stand-in: grep match and grep extract

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Look at the table: the status is 200 for every attempt, so the status column is useless. The Welcome match column and the length expose the only successful row. This is why grep columns matter, and also why the defender's lesson is to add lockouts and rate limits, not just generic messages.

Practical advice

  • Start with Repeater. Understand one request fully before automating.
  • Mark as few positions as needed.
  • Pre-calculate the number of requests, and compare with the agreement.
  • Choose grep terms from real responses you saw in Repeater.
  • Save results (with sensitive values redacted) as evidence.
  • Use a time delay if the target is fragile; see Safe, rate-limited testing.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which payload type is most natural for testing sequential order ids such as 1000 to 1100?

    The Numbers type generates a numeric range with a step and optional zero padding.
  2. 2. What does Grep - Match add to the results table?

    Grep - Match marks responses containing your terms, making rare successes or errors easy to find.
  3. 3. Every response has the same status and similar length. Which feature helps find the odd one?

    When status and length are uniform, a custom column on a distinguishing word or value reveals the difference.
  4. 4. Why use payload encoding for special characters?

    Unencoded characters can break the request structure, so the test would not exercise the intended field.

Summary

  • Choose a payload type that fits the data: numbers, lists, iterators, null payloads and more.
  • Processing rules add prefixes, encode, hash or filter payloads before sending.
  • Grep - Match and Grep - Extract add columns that show which responses matter.
  • Use small, thoughtful payload lists and calculate request counts first.
  • Defenders learn from the same view: uniform status codes need rate limits and lockouts too.

Next: Safe, rate-limited testing