https://github.com/kgretzky/evilginx2
Important Assumptions
Installed on Ubuntu 22.04 Desktop
Public DNS Records point to your asset
Assumes you have a separate, reverse proxy to manage incoming requests from different targets
https://github.com/vnhacker1337/evilgophish-custom
https://github.com/An0nUD4Y/Evilginx2-Phishlets
https://www.kitploit.com/2022/11/evilgophish-evilginx2-gophish.html
Video Reference# Have a wildcard DNS record point to your asset from a provider. This example used Cloudflare to point to an NGINX Reverse Proxy configured with SSL certs.
*.attck.community
$attck-sub1.attck.community
# example
join.attck.community
logon.attck.community
cd /opt/
git clone <https://github.com/fin3ss3g0d/evilgophish.git>
cd evilgophish
./setup.sh $threat-domain.root "$attck-sub1 $attck-sub2" false $target-sub1.domain.root true user_id false
./setup.sh attck.community "attck-sub1 attck-sub2" false "<https://target-sub1.c3s.community>" true user_id false
# example of what to execute in a different terminal window
certbot certonly --manual --preferred-challenges=dns --email [email protected] --server <https://acme-v02.api.letsencrypt.org/directory> --agree-tos -d 'attck-sub1.attck.community' -d 'attck-sub2.attck.community'
# example of what to paste in terminal at prompt
Path to Certs: /etc/letsencrypt/live/attck.community/
Certificate is saved at: /etc/letsencrypt/live/attck.community/fullchain.pem
Key is saved at: /etc/letsencrypt/live/attck.community/privkey.pem
#For setting up HTTPS Listeners in MSFConsole
cat /etc/letsencrypt/live/attck.community/fullchain.pem /etc/letsencrypt/live/attck.community/privkey.pem /opt/ssl/attck-certkey.pem
(Under Development: Use Cases)