42 lines
1.1 KiB
Markdown
42 lines
1.1 KiB
Markdown
---
|
|
{"publish":true,"title":"Evilginx Configuration","created":"2025-06-26T12:16:40.875-06:00","modified":"2025-06-26T15:12:06.592-06:00","tags":["evilginx","guide","phishing"],"cssclasses":""}
|
|
---
|
|
|
|
>[!info]
|
|
>These are my notes on my specific steps to configure Evilginx. I have tried to highlight things that you would need to change for your deployment scenario but no guarantees!
|
|
|
|
1. Start a new tmux session for Evilginx
|
|
|
|
```
|
|
tmux new-session -A -s evilginx
|
|
```
|
|
|
|
>[!note]
|
|
>This command will attempt to attach (the `-A` argument) to an existing session called evilginx (specified by `-s evilginx`) before creating a new one
|
|
|
|
2. Launch Evilginx
|
|
|
|
```
|
|
~/evilginx/evilginx
|
|
```
|
|
|
|
3. At the Evilginx prompt set your domain and IP
|
|
|
|
```
|
|
config domain philsphishpharm.click
|
|
config ipv4 external 80.78.25.193
|
|
config ipv4 bind 80.78.25.193
|
|
```
|
|
|
|
4. You will need to restart Evilginx to apply the configuration
|
|
```
|
|
(At the Evilginx prompt)
|
|
exit
|
|
|
|
(At the system prompt)
|
|
~/evilginx/evilginx
|
|
```
|
|
|
|
At this point Evilginx should be configured at ready for you to [[10-19 HOBBYS/13 SECURITY/13.11 EVILGINX/phish setup\|start phishing]]!
|
|
|