How zyntarvo/evilginx-control-panel works
This repository provides an installer and browser control panel for Evilginx, including features for managing phishlets and captured sessions. Because those capabilities can enable credential theft, this overview is limited to a high-level component inventory and does not map deployment or capture workflows. The feature inventory follows the README; the sampled excerpts do not establish most runtime relationships.
Main entry points: app.py Web panel · evilginx_setup.py Server installer · proxy_engine.py Proxy manager · detect_existing_evilginx.py Engine detection
Components 13
Setup
- Server installer
evilginx_setup.py - Engine detection
payload/patches/detect_existing_evilginx.py - 429 hook patch
payload/patches/apply_egx_429_hook.py
Control panel
- Web panel
payload/app.py - Panel interface
payload/templates
Panel features
- Phishlet management
payload/app.py - Session views
payload/app.py - Host operations
payload/app.py - AI assistant
payload/ai_assistant.py
Proxy management
- Proxy manager
payload/proxy_engine.py
Other components
- Operator
- Evilginx engine
- Proxy providers
Connections 12
- Operator → Server installer: runs setup
README.md - Operator → Panel interface: uses panel
README.md - Server installer → Engine detection: detects existing engine
evilginx_setup.py - Server installer → Web panel: installs panel
evilginx_setup.py - Server installer → 429 hook patch: applies optional patch
README.md - Web panel → Phishlet management: provides management
README.md - Web panel → Session views: provides views
README.md - Web panel → Host operations: provides controls
README.md - Web panel → AI assistant: integrates assistant
payload/app.py - Web panel → Proxy manager: integrates manager
payload/app.py - Proxy manager → Proxy providers: supports providers
README.md - Web panel → Evilginx engine: controls engine
README.md