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 instalaciones+2 en 7 días27 EstrellasMITsincronizado hace 23 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tools-sqlmapEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete9d415327…7f77e881
9d4153277439…630c7f77e8811 archivo · 2.5 KBEscaneoMedio2 hallazgos
- Enlace a una IP directaSKILL.md:63
- Enlaces a dominios externos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/tools/tools-sqlmap@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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
- 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 - Aim it.
-p idto test one parameter; mark the injection point inline with*(works in--dataand--cookietoo):--data="a=1&b=2*&c=3". If you already know the backend,--dbms=mysqlskips fingerprinting. - Turn up coverage deliberately:
--level=5 --risk=3tests 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. - Evade filters with tamper scripts (see
payloads-waf-bypassfor the manual matrix):bash sqlmap -u "http://target/page?id=1" --tamper=space2comment,between --random-agentTamper Effect space2commentspaces → /**/between>→BETWEENrandomcaserandom keyword casing charencodeURL-encode every char equaltolike=→LIKEbase64encodeBase64 the payload - 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). - 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. --os-shellonly 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=Talone 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 checkroe.mdrequest-rate limits first. - Interrupted runs resume — sqlmap keeps session state in its output dir; rerun the same command instead of starting over.
--risk=3can 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.
Archivos de esta versión
- SKILL.md5.0 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaEnlace · Enlace a una IP directaSKILL.md:63
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 9d415327 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Web y bug bounty
Ver la categoría- 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
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login