How mohammedraouf99/evil-ap works
Evil-AP is documented as a command-line Evil Twin automation tool with customizable web pages. The documented user workflow is to run the shell script; the README and sampled files do not reveal how it orchestrates the page directories or attack stages. The page families show credential-check endpoints and success/failure responses, but their runtime wiring is not established by the available evidence.
Main entry points: pages Failure responses · evil-ap.sh Evil-AP launcher · Arabic/index.html Arabic portal · Cisco/index.html Cisco portal
Components 12
Command-line entry
- Evil-AP launcher
evil-ap.sh
Web portal pages
- Arabic portal
pages/Arabic/index.html - Cisco portal
pages/Cisco/index.html - D-Link portal
pages/D-link/index.html - English portal
pages/English/index.html - Huawei portal
pages/Huawei/index.html - TP-Link portal
pages/TP-link/index.html - Credential check endpoints
pages
Credential responses
- Success responses
pages - Failure responses
pages - Password list
password_list.txt
Other components
- Operator
Connections 7
- Operator → Evil-AP launcher: runs
README.md - Failure responses → Arabic portal: redirects to index
pages/Arabic/wrong.php - Failure responses → Cisco portal: redirects to index
pages/Cisco/wrong.php - Failure responses → D-Link portal: redirects to index
pages/D-link/wrong.php - Failure responses → English portal: redirects to index
pages/English/wrong.php - Failure responses → Huawei portal: redirects to index
pages/Huawei/wrong.php - Failure responses → TP-Link portal: redirects to index
pages/TP-link/wrong.php