tools-burp-suite
Drive Burp Suite for web/API testing — proxy history triage, Repeater, Intruder enumeration, Collaborator OOB, active scanning — manually or agent-driven through a Burp MCP extension on 127.0.0.1:9876. Load for any HTTP-target deep testing: "burp", proxy history analysis, repeater replay, intruder b
v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tools-burp-suiteScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto6684e126…53038568
6684e126b311…53d6530385682 file · 5.4 KBScansioneMedio3 segnalazioni
- Link a un indirizzo IP direttoSKILL.md:38
- Link a un indirizzo IP direttocheatsheet.md:6
- Link a domini esterni
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/tools/tools-burp-suite@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
You're web/API testing an in-scope target (tradecraft-scope-roe; load web-testing-checklist or
api-testing-checklist as the coverage map) and need the core manual-testing platform: intercept,
modify/replay, targeted enumeration, OOB detection, or an active scan. Burp is name-dropped across
many skills as "send it to Repeater" — this one is how to operate it, including agent-driven
operation through an MCP extension so the AI can read proxy history and fire Intruder itself.
Why it works
Every request the browser makes flows through Burp's proxy into a searchable history; Repeater gives byte-exact replay, Intruder turns one request into a thousand enumerated variants, Collaborator provides OOB callbacks that prove blind bugs, and the MCP extensions expose all of it as tools — so an agent can triage hundreds of captured requests and only escalate the interesting ones.
Method
- Set up agent access (MCP). Burp must be running with an MCP extension loaded:
- Official: Extensions → BApp Store → "MCP Server" (PortSwigger) → Enable (~20 core tools).
- Community full-coverage extensions expose ~78 tools (full inventory:
cheatsheet.md) via an HTTP API on127.0.0.1:9876plus a stdio bridge for MCP clients. Health check:curl http://127.0.0.1:9876/health. - Never load cracked/repackaged Burp builds — official PortSwigger releases only (Community is fine but rate-limits Intruder hard).
- Triage proxy history first. Browse the app through the proxy (login, exercise every feature),
then work the history: filter by host/path, pull full request/response detail on candidates,
regex-search history for secrets (
Authorization: Bearer,api_key, JWT shapes). This turns "click around" into a coverage map for the checklist skills. - Verify by replay (Repeater). Modify one thing at a time and diff responses — auth headers
removed, HTTP method swapped (GET→PUT/DELETE), IDs incremented for
web-idor, extra JSON fields forapi-mass-assignment,X-Forwarded-For/X-Original-URLfor 403 bypasses, path case/traversal variants (/Admin→/admin,..;/). - Enumerate with Intruder. Numeric ranges (OTP/ID enum:
code=@@from 000000–999999), wordlist attacks, cluster-bomb for multi-param cartesian products. Identify hits by response-length difference (e.g.success when length ≠ <error length>) or response time for blind injections. On Community, keep threads low — it throttles to ~1 req/s. - Prove blind bugs with Collaborator. Generate a payload, inject it into URL/webhook/redirect
params, poll for DNS/HTTP interactions after a few seconds — a callback confirms SSRF/XXE/blind
injection that no response diff ever would (
web-ssrf). - Active scan + targeted fuzzing. Add the target to scope, crawl, then active-scan key requests;
treat scanner output as candidates — every issue gets a manual Repeater confirmation
(
reporting-triage-validation) before it becomes a finding. - Automate repetitive transforms with HTTP handlers / match-and-replace: auto-attach auth
headers, re-sign requests after reverse-engineering a client signature scheme
(
web-client-side-signing-bypass), or route through an upstream proxy pool for IP rotation.
Gotchas
- Extension won't load — community MCP extensions are typically compiled for JDK 21+; check Burp's Java version first. Port 9876 already bound = another extension instance running.
- Community Edition throttles Intruder and has no active scanner — plan around it (small targeted lists, manual Repeater loops) or use Pro.
- High thread counts DoS the target and trip WAFs — cap threads, respect
roe.mdrate limits, and prefersuccess_length_not-style discrimination over reading every response. - History ≠ evidence — a suspicious request in proxy history is a lead, not a finding; the finding is the Repeater replay that proves impact.
- Encrypted/signed params — don't fuzz ciphertext; extract or re-implement the transform first, then register it as an auto-handler so Intruder works on plaintext.
- Scope discipline — Burp will happily scan whatever you crawl; keep
add_to_scopealigned withscope.txtand never point the active scanner out of scope.
Verify success
Each candidate from history/scanner/Intruder either reproduces in Repeater with a visible impact (diff, data, OOB callback) or is ruled out with the variation matrix worked (per House rules). Confirmed issues are written up per the engagement's findings format with the exact replayed request as proof.
References
PortSwigger Web Security Academy & Burp docs; BApp Store "MCP Server". Tool-by-tool inventory and
per-scenario workflows: cheatsheet.md.
Portions adapted from reverse-skill by zhaoxuya520, MIT License.
File di questa versione
- cheatsheet.md6.9 KB
- SKILL.md5.6 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | Sì | Sì |
| Usa i connettori | Sì | Sì |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaLink · Link a un indirizzo IP direttoSKILL.md:38
- MediaLink · Link a un indirizzo IP direttocheatsheet.md:6
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 6684e126 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Web e bug bounty
Vai alla categoria- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login