How ninja-yubaraj/sql-injection-payloads-list works
Intruder is a payload-list repository, not an executable scanner: it organizes SQL injection probes and exploitation payloads by technique and database. The documented user workflow is to choose payloads for a target and observe responses; the repository provides no runtime orchestration. The README describes generic error-, union-, and blind-SQLi approaches, while the tree adds database-specific detection and exploitation sets. Relationships from an attacker to the payload collections are shown as unverified because no source excerpts establish how users consume them.
Main entry points: detect Generic probes · MSSQL MSSQL probes · MySQL MySQL probes · NoSQL NoSQL probes
Components 14
Detection Payloads
- Generic probes
Intruder/detect - MSSQL probes
Intruder/detect/MSSQL - MySQL probes
Intruder/detect/MySQL - NoSQL probes
Intruder/detect/NoSQL - Oracle probes
Intruder/detect/Oracle - Cross-platform probes
Intruder/detect/xPlatform
Exploitation Payloads
- Auth bypass
Intruder/exploit/Auth_Bypass.txt - DB2 enumeration
Intruder/exploit/DB2/db2-enumeration.txt - MSSQL enumeration
Intruder/exploit/MSSQL/ms-sql-enumeration.txt - MySQL exploits
Intruder/exploit/MySQL - Postgres enumeration
Intruder/exploit/PostgresSQL/postgres-enumeration.txt
Blind Payloads
- MSSQL blind sets
Intruder/payloads-sql-blind/MSSQL - MySQL blind sets
Intruder/payloads-sql-blind/MySQL
Other components
- Tester
Connections 13
- Tester → Generic probes: selects probes
- Tester → MSSQL probes: selects probes
- Tester → MySQL probes: selects probes
- Tester → NoSQL probes: selects probes
- Tester → Oracle probes: selects probes
- Tester → Cross-platform probes: selects probes
- Tester → Auth bypass: selects payloads
- Tester → DB2 enumeration: selects payloads
- Tester → MSSQL enumeration: selects payloads
- Tester → MySQL exploits: selects payloads
- Tester → Postgres enumeration: selects payloads
- Tester → MSSQL blind sets: selects payloads
- Tester → MySQL blind sets: selects payloads