60 lines
1.7 KiB
Markdown
60 lines
1.7 KiB
Markdown
---
|
|
{"publish":true,"title":"Installing Evilginx Community Edition","created":"2026-01-10T15:29:21.577-07:00","modified":"2025-06-26T12:40:30.910-06:00","tags":["phishing","evilginx","guide"],"cssclasses":""}
|
|
---
|
|
|
|
|
|
With commercialization comes the enshitification of community editions, and this is equally true for Evilginx sadly. They have made it very clear in their documentation that they no longer want to make it obvious for users to install without paying so here are my installation notes for those who follow.
|
|
|
|
>[!info]
|
|
>My install was performed on a VPS running Debian 12. YMMV if you are using a different distro
|
|
>
|
|
>This guide covers software installation only. The official Evilginx documentation for domain setup is adequate
|
|
|
|
>[!note] Prior to installing Evilginx I completed some basic server setup work that you can find [[10-19 HOBBYS/13 SECURITY/13.11 EVILGINX/basic configuration\|here]]
|
|
|
|
|
|
1. Install prerequisite packages
|
|
|
|
```
|
|
apt install git make golang tmux
|
|
```
|
|
|
|
>[!note]
|
|
>The `tmux` package is not required for the install but is highly recommended for running the service so I have included it here
|
|
>
|
|
|
|
2. Clone the git repository at the latest stable tag (3.3.0 at time of writing)
|
|
|
|
```
|
|
git clone --depth 1 --branch v3.3.0 https://github.com/kgretzky/evilginx2.git
|
|
```
|
|
|
|
3. Build the software
|
|
|
|
```
|
|
cd evilginx2
|
|
make
|
|
```
|
|
|
|
4. Create a directory for the Evilginx binary and configurations
|
|
|
|
```
|
|
mkdir ~/evilginx
|
|
```
|
|
|
|
5. Copy the binary and necessary directories to the application folder
|
|
|
|
```
|
|
cp ./build/evilginx ~/evilginx
|
|
cp -r ./phishlets/ ~/evilginx
|
|
cp -r ./redirectors/ ~/evilginx
|
|
```
|
|
|
|
6. Make sure everything is executable
|
|
|
|
```
|
|
chmod 700 ~/evilginx
|
|
```
|
|
|
|
From here you can move on to [[10-19 HOBBYS/13 SECURITY/13.11 EVILGINX/configuration]]
|