Burp Intruder Attack Types and Payloads
You'll learn how Burp Intruder automates custom attacks using four distinct attack types and configurable payload positions.
What Is Burp Intruder?
Burp Intruder automates customized attacks against web applications by injecting payloads into specific positions of HTTP requests. Think of it as a precision artillery system where you mark targets (payload positions) and choose how to fire (attack type). This tool excels at fuzzing inputs, testing authentication, and discovering vulnerabilities through systematic parameter manipulation.
The Four Attack Types
Sniper
Uses one payload set and tests each position individually. Like a sniper taking precise, single shots—if you mark three positions, it fires at position 1, then position 2, then position 3, cycling through all payloads for each position separately.
Battering Ram
Uses one payload set and inserts the same payload into all positions simultaneously. Like ramming a door with synchronized force—if you mark username and password fields, both get "admin" together, then both get "test" together.
Pitchfork
Uses multiple payload sets (one per position) and iterates through them in parallel. Like synchronized gears—payload set 1's first value pairs with payload set 2's first value, second with second, etc. Perfect for testing username/password pairs from a list.
Cluster Bomb
Uses multiple payload sets and tests every possible combination. Like carpet bombing—if position 1 has 10 payloads and position 2 has 20 payloads, you get 200 total requests (10×20). Comprehensive but generates many requests.
Configuring Payloads
Mark payload positions in requests using markers (Burp highlights them). Then configure payload sets—simple lists, numbers, character substitutions, or custom generators. Each attack type determines how many sets you need and how they're applied.
Key Takeaway: Burp Intruder's attack types—Sniper (sequential single-position), Battering Ram (synchronized), Pitchfork (parallel pairs), and Cluster Bomb (all combinations)—provide targeted automation for different testing scenarios, with payload positions and sets defining what gets injected where.