Skip to content
Tutorials Center
My learning

Topics

Lesson 17 of 38 ยท Repeater and Intruder

Intruder Attack Types

Learn how Burp Intruder works and what the four attack types do: sniper, battering ram, pitchfork and cluster bomb, with a safe lab model of each.

Where Repeater sends one request at a time, Intruder sends many. You mark one or more positions in a request, supply lists of payloads, and Intruder sends one request per combination, recording status, length and other details for each. It automates repetitive manual work: checking many identifier values, testing a list of inputs, or measuring how an endpoint reacts to variation.

Intruder can generate thousands of requests, which looks identical to a brute-force attack. Use it only on systems you own or are authorised to test, keep volumes modest, and follow the limits in the agreement. Safe, rate-limited testing covers this.

In Community edition Intruder is deliberately throttled, so runs are slow. That is enough to learn the ideas, and the stand-ins below run instantly against a fake in-memory app.

Setting up an attack

  1. Send a request to Intruder (right-click > Send to Intruder, or Ctrl+I).
  2. In the Positions tab, Burp wraps likely values in ยง markers; press Clear ยง and mark only the values you want varied.
  3. Choose an attack type.
  4. In the Payloads tab, choose a payload set and its type (simple list, numbers, and so on).
  5. Start the attack and watch the results table.

A request with a marked position looks like this:

HTTP
GET /api/v1/orders/ยง1001ยง HTTP/1.1
Host: shop.lab.test
Cookie: session=abc123

The four attack types

One list, one or many positions

Sniper One payload set, one position at a time.
Battering ram One set, same value in every position.

Both take a single payload set.

1 / 2

Sniper

One payload set. Intruder puts each payload into one position at a time, leaving the others at their original values. With two positions and 100 payloads you get 200 requests. Use it for testing a single parameter, or for checking each parameter in turn with the same list of inputs.

Battering ram

One payload set. Each request puts the same payload in all positions at once. Use it when two fields must hold the same value (for instance, a username in both the URL and the body).

Pitchfork

One payload set per position. Intruder walks the lists in step: request 1 uses item 1 of every list, request 2 uses item 2, and so on, stopping when the shortest list ends. Use it for data that comes in matched pairs, such as userId with its accountNumber.

Cluster bomb

One payload set per position, and Intruder tries every combination: with lists of 10 and 20 items, 200 requests; with three lists, the product grows fast. Use it when fields are independent but any pair might matter (a username list and a PIN list in a lab login).

The size of a cluster bomb is the product of the list lengths, so it is the attack type most likely to overload a target or exceed your agreed limits. Count before you start.

Reading results

The results table gives each request a payload, status, length, response time and (optionally) matched text. Click a column to sort. The skill is spotting the odd one out:

  • one status among many (200 among 404s),
  • a different length,
  • a slower response,
  • an extracted value that changes.

Try it: the four attack types as generators

A stand-in that builds the list of requests each attack type would send, with no network at all. Compare the counts and the combinations.

Python Stand-in: the four attack types

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.

Notice pitchfork stops at 2 requests (the shorter list), while cluster bomb makes 2 x 3 = 6.

Try it: an Intruder run against a fake app

A second stand-in runs a sniper attack on an order id in an in-memory app, collects status and length, and flags the unusual responses, exactly how you read a real results table. No network is involved.

Python Stand-in: reading intruder results

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.

The two existing orders stand out by status and length. That is the finding: identifiers are guessable and the server reveals which exist, so the fix is an ownership check and, ideally, unpredictable identifiers.

Which type should I use?

Goal Attack type
Try a list of values in one field Sniper
Try a list of values in each of several fields, one at a time Sniper
Same value must appear in several places Battering ram
Matched pairs (id with matching token) Pitchfork
Independent fields, all combinations Cluster bomb (watch the count)

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A request has two positions and you use sniper with 50 payloads. How many requests are sent?

    Sniper tests each position separately with every payload: 2 positions x 50 payloads = 100 requests.
  2. 2. Which attack type tries every combination of several payload lists?

    Cluster bomb multiplies the lists, which makes it powerful and also the most likely to produce huge request counts.
  3. 3. Pitchfork with lists of 10 and 4 items sends how many requests?

    Pitchfork moves through the lists in step and stops when the shortest ends, so 4 requests.
  4. 4. Why is Intruder dangerous if used carelessly?

    Volume is the risk. Count requests, respect the agreed limits and use it only where authorised.

Summary

  • Intruder automates many variations of one request by marking positions and supplying payloads.
  • Sniper tests positions one at a time; battering ram uses one value everywhere; pitchfork pairs lists; cluster bomb tries all combinations.
  • Request counts are products for cluster bomb: calculate them first.
  • Read results by status, length and time, and look for outliers.
  • Use Intruder only in authorised scope and within agreed limits.

Next: Intruder payloads, processing and grep