Burpsuite Project Parser
Searches and explores Burp Suite project files (.burp) from the command line.
Install
npx skills add trailofbits/skills --skill burpsuite-project-parser -g -a claude-code -y- Repository
- trailofbits/skills7.9k
- Category
- Security
- Updated
- 7d ago
- License
- CC-BY-SA-4.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.
Burp Project Parser
Search and extract data from Burp Suite project files using the burpsuite-project-file-parser extension.
When to Use
- Searching response headers or bodies with regex patterns
- Extracting security audit findings from Burp projects
- Dumping proxy history or site map data
- Analyzing HTTP traffic captured in a Burp project file
Prerequisites
This skill delegates parsing to Burp Suite Professional - it does not parse .burp files directly.
Required:
- Burp Suite Professional - Must be installed (portswigger.net)
- burpsuite-project-file-parser extension - Provides CLI functionality
Install the extension:
- Download from github.com/BuffaloWill/burpsuite-project-file-parser
- In Burp Suite: Extender → Extensions → Add
- Select the downloaded JAR file
Quick Reference
Use the wrapper script:
{baseDir}/scripts/burp-search.sh /path/to/project.burp [FLAGS]
The script uses environment variables for platform compatibility:
BURP_JAVA: Path to Java executableBURP_JAR: Path to burpsuite_pro.jar
Check the exit code. Empty output is not a clean result. Burp ignores flags it does not recognise, so without the parser extension it starts normally and drops the query, which looks exactly like a search that matched nothing.
| Exit | Meaning | What to do |
|---|---|---|
| 0 | Output produced | Proceed |
| 1 | Bad usage, or a missing file, Java or JAR | Read the message; fix the path |
| 3 | No output at all | Do not report this as "nothing found". An empty result set and an unloaded extension are indistinguishable from here. Run the control query below to tell them apart |
| 4 | Output was not JSON | The extension is not loaded and Burp ignored the flags. Install it before trusting any result |

