Free build time

A collection of things to build during the free build block, or after the workshop. Pick something that solves a real problem in your testing workflow. That’s where the best extensions come from.

Legend: 🟒 quick win Β· 🟑 a session’s work Β· πŸ”΄ ambitious

Bambdas come in several types: table filters, custom columns, match and replace, custom actions (Repeater), and custom scan checks. Extensions can do all of that and far more via the Montoya API. Don’t feel limited by the examples. You can build far beyond them.


Table of contents

  1. Where to look when you get stuck
  2. Bambda ideas
  3. Extension ideas

Where to look when you get stuck

Resource Link
Bambdas documentation portswigger.net/…/bambdas
Community Bambdas (reference) github.com/PortSwigger/bambdas
Montoya API JavaDoc portswigger.github.io/…/javadoc
Extension examples github.com/PortSwigger/…-examples
Extension starter project github.com/PortSwigger/extension-template-project

If you’re stuck on the API, the CLAUDE.md in the extension template is built to paste into an AI assistant alongside your idea. See the β€œUsing an LLM to generate your extension” section of the extension workshop README.

See also the Downloads & Resources page for prerequisites and further reading.


Bambda ideas

Table filters

  • 🟒 Hide noise: drop requests for static assets (.css, .js, .png, .woff, fonts, analytics beacons) so history shows only the interesting traffic.
  • 🟒 In-scope only, without Burp scope: show only requests whose host matches a regex you control, even before you set Burp scope.
  • 🟒 Error spotter: show only responses with status >= 500, or 4xx that aren’t 404.
  • 🟒 Big responses: show only responses over N kilobytes (candidate data leaks, verbose error pages).
  • 🟒 Slow responses: surface requests whose round-trip time crosses a threshold (timing oracle candidates).
  • 🟑 Reflected parameters: show rows in which a query/body parameter value appears verbatim in the response body (XSS/reflection triage).
  • 🟑 Auth state diff: show only requests that carry a session cookie but got a 401/403 back (broken access control candidates).
  • 🟑 Interesting content types: show only application/json, xml, octet-stream, or anything that isn’t HTML.
  • 🟑 Secrets in responses: flag rows whose body matches patterns for AWS keys, JWTs, private keys, BEGIN RSA, bearer tokens, Google API keys.
  • 🟑 Set-Cookie without flags: show responses that set a cookie missing HttpOnly, Secure, or SameSite.
  • 🟑 CORS interesting: show responses with Access-Control-Allow-Origin: * or a reflected Origin.
  • 🟑 Method anomalies: show PUT, DELETE, PATCH, or TRACE requests only.
  • πŸ”΄ Parameter pollution: show requests that contain the same parameter name more than once.
  • πŸ”΄ GraphQL traffic: show only requests whose body looks like a GraphQL query/mutation.

Custom columns

  • 🟒 Response time: surface round-trip latency as a sortable column.
  • 🟒 Body size: response length in bytes/KB.
  • 🟒 Server / X-Powered-By / X-Runtime: fingerprint tech stack at a glance.
  • 🟒 Content-Type: pull the type into its own column.
  • 🟑 Cookie count: number of cookies set in the response.
  • 🟑 Reflected param name: show which parameter was reflected, not just that one was.
  • 🟑 JWT alg: decode the token header and show the algorithm (weak-config triage).
  • 🟑 JWT exp countdown: decode the payload and show time-to-expiry.
  • 🟑 CSP presence/score: show whether a Content-Security-Policy exists and how strict it looks.
  • 🟑 Auth scheme: Basic / Bearer / Digest / none, parsed from the Authorization header.
  • 🟑 Parameter count: number of query + body parameters (large requests are worth inspecting).
  • πŸ”΄ WAF/CDN guess: infer Cloudflare, Akamai, and similar from response headers and surface it.
  • πŸ”΄ Entropy score: compute Shannon entropy of a token/parameter to flag likely secrets.

Match and replace

  • 🟒 Force verbose errors: inject X-Debug: true or similar on every request to trigger stack traces.
  • 🟒 Spoof mobile: swap the User-Agent to a mobile device to reach a different code path.
  • 🟒 Pin a header: always add a custom tenant/feature-flag header (X-Tenant-Id, X-Feature: beta).
  • 🟑 Strip caching: remove If-None-Match/If-Modified-Since so you always get fresh 200s, not 304s.
  • 🟑 Cache-buster: append a random query param to bust CDN caches while testing.
  • 🟑 Downgrade content negotiation: rewrite Accept-Encoding to identity so responses are uncompressed and readable.
  • 🟑 Origin reflection probe: set Origin: to an attacker domain on every request to test CORS reflection.
  • πŸ”΄ Conditional rewrite: only modify requests to a specific host or path (logic inside the Bambda, not just a static rule).

Custom actions: Repeater

  • 🟒 Base64 decode selection: decode the highlighted bytes and print the result to the output console.
  • 🟒 URL-decode / HTML-decode selection: quick one-click decoders.
  • 🟑 JWT decoder: take the selected JWT, decode header + payload, and print both as pretty JSON.
  • 🟑 Timestamp converter: find Unix timestamps in the request and print them as readable dates.
  • 🟑 Hash the selection: MD5/SHA-1/SHA-256 the highlighted bytes (useful for cache keys, ETags, signatures).
  • 🟑 Extract all links: pull every URL out of a response body and list them.
  • 🟑 Generate TOTP: compute a current TOTP code from a hardcoded secret and print it for pasting.
  • 🟑 Parameter inventory: list every parameter (query, body, cookie) in the request with its source.
  • πŸ”΄ Re-sign the request: recompute an HMAC signature over the (modified) request and show the value to paste back in.
  • πŸ”΄ Decode proprietary blob: decode a custom/serialized format in the selection and print the structured result.

Custom scan checks

  • 🟑 Passive: secret leak: raise an issue when a response body contains an API key / private key / token pattern.
  • 🟑 Passive: verbose error: flag stack traces, SQL errors, framework debug pages.
  • 🟑 Passive: missing security headers: report responses lacking CSP, X-Frame-Options, HSTS.
  • 🟑 Passive: insecure cookies: flag Set-Cookie without HttpOnly/Secure/SameSite.
  • 🟑 Active: reflected probe: inject a unique marker and report if it returns unencoded.
  • πŸ”΄ Active: error-based injection: send payloads that provoke distinguishable error responses and report on the signature.
  • πŸ”΄ Active: time-based oracle: send a payload that should delay the response and report if latency spikes.

Extension ideas

Extensions reach the parts of Burp that Bambdas can’t: persistent UI, background work, Intruder, Collaborator, project storage. Any Bambda idea can become a richer extension; the ideas here genuinely need the full API.

Message editor tabs

  • 🟒 JSON pretty-printer: a tab that indents minified JSON responses (the workshop example).
  • 🟑 JWT inspector tab: decode and display header + payload as formatted JSON, with the alg/exp highlighted.
  • 🟑 Base64/Hex auto-decoder: a tab that detects and decodes encoded blobs in the body.
  • 🟑 Protobuf / MessagePack viewer: render a binary body in a readable structure.
  • πŸ”΄ GraphQL explorer tab: pretty-print the query, list operations, show variables separately.
  • πŸ”΄ Diff tab: show this response diffed against the previous one for the same endpoint.

Session handling rules

  • 🟑 Auto-TOTP injector: generate and inject a fresh TOTP on requests to the login endpoint (workshop example, extended).
  • 🟑 Request signer: recompute an HMAC/JWS signature for each request so you can tamper freely and still pass signature checks across tools.
  • 🟑 Auto-renew bearer token: detect 401s, hit the refresh endpoint, and update the session with the new token.
  • πŸ”΄ Nonce/CSRF handler: scrape a fresh CSRF token (via a macro) and inject it into the next request automatically.

Proxy / HTTP handlers

  • 🟑 Header injector with UI: add/strip headers configured from a settings panel (not hardcoded).
  • πŸ”΄ Traffic recorder: log every request/response to a structured file (JSONL/HAR) for offline analysis.

Scanner

  • 🟑 Custom pack of passive checks: bundle several passive checks (secrets, headers, cookies) into one extension.
  • πŸ”΄ Custom active check: a real injection check with baseline comparison to cut false positives.
  • πŸ”΄ Custom provider for insertion points: teach Burp to inject into a custom header, a JSON field, or a serialized blob it wouldn’t normally treat as a parameter.

Intruder

  • 🟑 Payload generator: feed Intruder a custom sequence (incrementing IDs, date ranges, wordlist transforms).
  • 🟑 Payload processor: sign/encode/timestamp each payload before Burp sends it.
  • πŸ”΄ Stateful payload generator: generate the next payload based on the previous response (for example, follow pagination).

Collaborator

  • πŸ”΄ OOB canary: register a Collaborator payload, inject it across requests, and alert when it gets a hit (SSRF/blind injection).
  • πŸ”΄ DNS exfil detector: watch for Collaborator interactions tied to specific test cases and correlate them back.

UI / workflow

  • 🟑 Context-menu toolkit: right-click actions you might find useful.
  • 🟑 Notes panel: a suite tab where you jot findings tied to the current request, persisted in the project file.
  • 🟑 Scope dashboard: a suite tab summarising hosts seen, status-code spread, and tech fingerprints.
  • πŸ”΄ Checklist tracker: a suite tab with your pentest methodology checklist that auto-ticks items based on traffic seen.

Integrations & reporting

  • 🟑 Slack/Discord notifier: POST a message when a high-severity issue is found.
  • 🟑 Jira/ticket creator: turn a selected issue into a ticket via API.
  • πŸ”΄ Markdown report generator: export findings (with request/response evidence) to a formatted report file.
  • πŸ”΄ SARIF exporter: emit findings in SARIF so they drop into a CI security dashboard.

AI-powered: Burp AI

  • 🟑 Issue triage: send each new issue to Burp AI and tag the ones it judges interesting (auth flows, error leaks, hidden endpoints).
  • πŸ”΄ Payload suggester: ask Burp AI to propose injection payloads tailored to the parameter and tech stack it sees.
  • πŸ”΄ Finding write-up: turn a confirmed issue’s evidence into a drafted report section via Burp AI.

Off the beaten path

  • πŸ”΄ Auto-grouped site map: cluster similar requests (same endpoint, different IDs) in your own tab to collapse history noise.
  • πŸ”΄ Replay differ: re-send a saved request on a timer and alert when the response changes (config drift / deploy detector).
  • πŸ”΄ WebSocket inspector: capture and pretty-print WebSocket frames in a dedicated tab.