DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to scope a target and start a Burp scan over REST with Reburp

Add a host to Burp scope with one call, then start an audit or crawl through the scanner routes.

Authorization notice. Reburp is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA tester on a Burp Suite Professional license who wants a script or agent to set up scope and launch scanning for a new target.

The problemSetting scope and starting scans by clicking through Burp for each target is repetitive when many hosts are in play.

The outcomeThe target is in scope, a scan is running, and the tester can pull scanner issues over REST when it finishes.

What you need first

  • Burp Suite with the Montoya API (reburp 1.1.14 lists 2026.7 as minimum; older Burp needs the matching older jar from Releases)
  • The reburp-*.jar from the Releases page, or Java 17+ to build from source
  • Written authorization to test the target systems
  • A terminal with curl, or an AI agent that can make HTTP calls to 127.0.0.1:9090

Steps

  1. Load Reburp.jar in Burp and confirm the server with curl -s http://127.0.0.1:9090/api/status.
  2. Add the target to scope with curl -s http://127.0.0.1:9090/api/scope/include -H 'Content-Type: application/json' -d '{"url":"https://example.com"}', replacing the URL with your target. (inferred, check the README)
  3. Open http://127.0.0.1:9090/docs and use the Scanner group under /api/scanner/ to start an audit or crawl and check task status. (inferred, check the README)
  4. Poll the scanner task status until the task finishes, then read the issues from the scanner routes.
  5. Review each issue in Burp before reporting it.

Prompt for your agent

Using the reburp API at http://127.0.0.1:9090 (spec at /openapi.json), add <target URL> to scope, start an audit through the scanner routes, and poll task status until it completes. Return the list of scanner issues with names and severities, and verify that the target is in scope with /api/scope before reporting results.

Caveat. Scanner and collaborator endpoints return HTTP 403 on Community edition, so this workflow needs Burp Suite Professional.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page