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

How to triage Burp proxy history with an AI agent with Reburp

Let an agent read recent proxy traffic over REST and rank the most unusual exchanges first.

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

Credentials. Proxy history contains cookies and tokens from the target, so keep the agent output and any exports within the engagement scope.

Who it is forA pentester or bug bounty hunter with a large proxy history who wants help finding the interesting requests before reading them by hand.

The problemProxy history grows fast during a browsing session, and scrolling through it to spot anomalies takes time.

The outcomeA short, ranked list of proxy exchanges that look most anomalous, which the tester can open in Burp to investigate.

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. Download Reburp.jar from the Releases page, then in Burp open Extensions, Installed, Add, set Extension type to Java, select the jar, and click Next.
  2. Run curl -s http://127.0.0.1:9090/api/status to confirm the extension is up.
  3. Run curl -s "http://127.0.0.1:9090/api/proxy/history?limit=10" to read the latest proxy entries.
  4. Open http://127.0.0.1:9090/docs in a browser to find the ranking route under /api/utils/rank in the spec, then point the agent at it.
  5. Ask the agent to review the ranked exchanges and list the ones worth opening in Burp.

Prompt for your agent

Using the reburp API at http://127.0.0.1:9090 (spec at /openapi.json), read the latest proxy history for <target host>, rank it by anomaly through /api/utils/rank, and return the top 10 exchanges with method, path, and status. Verify that each returned item matches an entry in /api/proxy/history before reporting it.

Caveat. The API is unauthenticated on localhost, so any local process or open web page that can reach port 9090 can read this history.

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