Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/tools-sqlmapWeb e bug bounty

tools-sqlmap

⁨Operate sqlmap to confirm and exploit SQL injection — target selection from Burp requests, level/risk tuning, tamper scripts for WAF evasion, DB enumeration, and safe dump discipline. Load after a manual SQLi probe shows promise, or when automating confirmation across parameters. Signals: sqlmap, --⁩

v2026.10.14-ee0e0c52 installazioni+2 in 7 giorni27 StelleMITsincronizzato 23 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-sqlmap

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
wIYQ4n+HiM…gYvnI4Bg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto9d415327…7f77e881
9d4153277439…630c7f77e8811 file · ⁦2.5 KB⁩
ScansioneMedio2 segnalazioni
  • Link a un indirizzo IP direttoSKILL.md:63
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/tools/tools-sqlmap@ee0e0c5

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

When it applies

Manual testing (web-sqli) has produced a suspicious parameter on an in-scope target (tradecraft-scope-roe), or you have many in-scope parameters and need automated triage. sqlmap takes over the tedious part — confirming the injection type, fingerprinting the DBMS, enumerating schema, and extracting proof data. It is an exploitation accelerator, not a discovery substitute: feed it a real request, not a bare URL you have never looked at.

Why it works

sqlmap automates the full injection matrix per parameter — boolean-based, error-based, UNION query, stacked queries, and time-based blind (--technique=BEUST) — with per-DBMS dialects and a tamper pipeline that rewrites payloads to slip past filters. Because it replays a captured request, it tests exactly the auth state, headers, and body the app expects.

Method

  1. Start from a captured request, not a URL — save a working authenticated request from Burp and run sqlmap -r req.txt --batch. URL-mode equivalents:
    bash
    sqlmap -u "http://target/page?id=1" --batch
    sqlmap -u "http://target/login" --data="user=admin&pass=test" --batch
    sqlmap -u "http://target/page?id=1" --cookie="PHPSESSID=xxx" --batch
  2. Aim it. -p id to test one parameter; mark the injection point inline with * (works in --data and --cookie too): --data="a=1&b=2*&c=3". If you already know the backend, --dbms=mysql skips fingerprinting.
  3. Turn up coverage deliberately: --level=5 --risk=3 tests more (headers at level 3+, heavier payloads at higher risk) — but each step multiplies request count and, at risk 3, adds OR-based payloads that can UPDATE whole tables. Escalate only after the default pass fails.
  4. Evade filters with tamper scripts (see payloads-waf-bypass for the manual matrix):
    bash
    sqlmap -u "http://target/page?id=1" --tamper=space2comment,between --random-agent
    Tamper Effect
    space2comment spaces → /**/
    between > → BETWEEN
    randomcase random keyword casing
    charencode URL-encode every char
    equaltolike = → LIKE
    base64encode Base64 the payload
  5. Enumerate only what proves impact: --dbs → -D db --tables → -D db -T table --columns → -D db -T table -C col1,col2 --dump. Dump the minimum rows that demonstrate access (a few users, not the whole table).
  6. Watch it work — --proxy="http://127.0.0.1:8080" routes everything through Burp so you can see exactly what was sent and learn why a run failed.
  7. --os-shell only when the engagement explicitly includes code execution — it writes a file to the server (into the webroot); record the path and delete it during cleanup.

Gotchas

  • No cookies/session = scanning a login page — if the request needs auth, give sqlmap the exact cookie/token from a live session, or every response is the same 302 and it reports nothing.
  • "not injectable" after defaults is not "not vulnerable" — work the matrix: raise --level, try --technique=T alone for pure time-based, add tamper scripts, test other parameters. Only then mark the lead failed (House rules).
  • False positives happen — confirm the extracted data is real (does the "user" exist in the UI?) before writing the finding (reporting-triage-validation).
  • WAF/rate-limit bans mid-run — symptoms: responses suddenly all identical/blocked. Slow down (--delay), rotate UA (--random-agent), and check roe.md request-rate limits first.
  • Interrupted runs resume — sqlmap keeps session state in its output dir; rerun the same command instead of starting over.
  • --risk=3 can modify data — OR-true payloads against UPDATE contexts rewrite rows. On production-scope targets, stay at risk 1–2 unless the RoE says otherwise.

Verify success

sqlmap names the injection type and DBMS, and you hold minimal extracted proof (e.g. one row from a table you should not reach) plus the exact -r request and flags — enough for another tester to reproduce the finding verbatim.

References

sqlmap docs and tamper script list. Detection theory and manual payloads: web-sqli and its cheatsheet; WAF evasion matrix: payloads-waf-bypass.


Portions adapted from reverse-skill by zhaoxuya520, MIT License.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaLink · Link a un indirizzo IP direttoSKILL.md:63
  2. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.10.14-ee0e0c513 nov 2026ee0e0c59d415327Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login