⚠️ ARCHIVED: This repository is no longer actively maintained for public use. However, a maintained version may still be available exclusively for sponsors (depending on when you are reading this). Become a sponsor to gain access.

• evilgophish
  • Credits
  • Prerequisites
  • Disclaimer
  • Why?
  • Background
  • Infrastructure Layout
  • setup.sh
  • replace_rid.sh
  • Email Campaign Setup
  • SMS Campaign Setup
  • Live Feed Setup
  • A Word About The Evilginx3 Update
  • Debugging
  • Apache2 Customiization
  • Installation Notes
  • A Note About Campaign Testing And Tracking
  • A Note About The Blacklist and Tracking
  • Changes to GoPhish
  • Changelog
  • Issues and Support
  • A Word About Sponsorship
  • Future Goals
  • Contributing

Combination of evilginx3 and GoPhish.

Before I begin, I would like to say that I am in no way bashing Kuba Gretzky and his work. I thank him personally for releasing evilginx3 to the public. In fact, without his work this work would not exist. I must also thank Jordan Wright for developing/maintaining the incredible GoPhish toolkit.

You should have a fundamental understanding of how to use GoPhish, evilginx3, and Apache2.

I shall not be responsible or liable for any misuse or illegitimate use of this software. This software is only to be used in authorized penetration testing or red team engagements where the operator(s) has(ve) been given explicit written permission to carry out social engineering.

As a penetration tester or red teamer, you may have heard of evilginx3 as a proxy man-in-the-middle framework capable of bypassing two-factor/multi-factor authentication. This is enticing to us to say the least, but when trying to use it for social engineering engagements, there are some pain points.

1. Lack of tracking - evilginx3 does not provide unique tracking statistics per victim (e.g. opened email, clicked link, etc.), this is problematic for clients who want/need/pay for these statistics when signing up for a social engineering engagement.

2. Not a full social engineering toolkit - evilginx3 only provides proxy man-in-the-middle capabilities, it does not provide all of the functionality required for a social engineering campaign via email/SMS. For example, it does not send emails to targets or provide this functionality.

3. No GUI - do we really need to explain this one further? We all love our GUIs and the visual representation of data for a social engineering campaign is invaluable. Operators can really get a thorough understanding as to the success of their social engineering campaigns by being able to view a visual representation of the data.

In this setup, GoPhish is used to send emails and provide a dashboard for evilginx3 campaign statistics, but it is not used for any landing pages. Your phishing links sent from GoPhish will point to an evilginx3 lure path and evilginx3 will be used for landing pages. This provides the ability to still bypass 2FA/MFA with evilginx3, without losing those precious stats. Apache2 is simply used as a proxy to the local evilginx3 server and an additional hardening layer for your phishing infrastructure. Realtime campaign event notifications have been provided with a local websocket/http server I have developed and full usable JSON strings containing tokens/cookies from evilginx3 are displayed directly in the GoPhish GUI (and feed):

• evilginx3 will listen locally on port 8443
• GoPhish will listen locally on port 8080 and 3333
• Apache2 will listen on port 443 externally and proxy to local evilginx3 server
  • Requests will be filtered at Apache2 layer based on redirect rules and IP blacklist configuration
    • Redirect functionality for unauthorized requests is still baked into evilginx3 if a request hits the evilginx3 server

setup.sh has been provided to automate the needed configurations for you. Once this script is run and you've fed it the right values, you should be ready to get started. Below is the setup help (note that certificate setup is based on letsencrypt filenames):

Usage:
./setup <root domain> <subdomain(s)> <root domain bool> <redirect url> <feed bool> <rid replacement> <blacklist bool>
 - root domain                     - the root domain to be used for the campaign
 - subdomains                      - a space separated list of evilginx3 subdomains, can be one if only one
 - root domain bool                - true or false to proxy root domain to evilginx3
 - redirect url                    - URL to redirect unauthorized Apache requests
 - feed bool                       - true or false if you plan to use the live feed
 - rid replacement                 - replace the gophish default "rid" in phishing URLs with this value
 - blacklist bool                  - true or false to use Apache blacklist
Example:
  ./setup.sh example.com "accounts myaccount" false https://redirect.com/ true user_id false

Redirect rules have been included to keep unwanted visitors from visiting the phishing server as well as an IP blacklist. The blacklist contains IP addresses/blocks owned by ProofPoint, Microsoft, TrendMicro, etc. Redirect rules will redirect known "bad" remote hostnames as well as User-Agent strings.

In case you ran setup.sh once and already replaced the default RId value throughout the project, replace_rid.sh was created to replace the RId value again.

Usage:
./replace_rid <previous rid> <new rid>
 - previous rid      - the previous rid value that was replaced
 - new rid           - the new rid value to replace the previous
Example:
  ./replace_rid.sh user_id client_id

Once setup.sh is run, the next steps are:

1. Start GoPhish and configure email template, email sending profile, and groups
2. Start evilginx3 and configure phishlet and lure (must specify full path to GoPhish sqlite3 database with -g flag)
3. Ensure Apache2 server is started
4. Launch campaign from GoPhish and make the landing URL your lure path for evilginx3 phishlet
5. PROFIT

An entire reworking of GoPhish was performed in order to provide SMS campaign support with Twilio. Your new evilgophish dashboard will look like below:

Once you have run setup.sh, the next steps are:

1. Configure SMS message template. You will use Text only when creating a SMS message template, and you should not include a tracking link as it will appear in the SMS message. Leave Envelope Sender and Subject blank like below:

2. Configure SMS Sending Profile. Enter your phone number from Twilio, Account SID, Auth Token, and delay in between messages into the SMS Sending Profiles page:

3. Import groups. The CSV template values have been kept the same for compatibility, so keep the CSV column names the same and place your target phone numbers into the Email column. Note that Twilio accepts the following phone number formats, so they must be in one of these three:

4. Start evilginx3 and configure phishlet and lure (must specify full path to GoPhish sqlite3 database with -g flag)
5. Ensure Apache2 server is started
6. Launch campaign from GoPhish and make the landing URL your lure path for evilginx3 phishlet
7. PROFIT

Realtime campaign event notifications are handled by a local websocket/http server and live feed app. To get setup:

1. Select true for feed bool when running setup.sh

2. cd into the evilfeed directory and start the app with ./evilfeed

3. When starting evilginx3, supply the -feed flag to enable the feed. For example:

./evilginx3 -feed -g /opt/evilgophish/gophish/gophish.db

4. You can begin viewing the live feed at: http://localhost:1337/. The feed dashboard will look like below:

IMPORTANT NOTES

• The live feed page hooks a websocket for events with JavaScript and you DO NOT need to refresh the page. If you refresh the page, you will LOSE all events up to that point.

On May 10, 2023 Kuba Gretzky updated evilginx 2.4.0 to version 3.0.0. You can find a detailed blog post about changes to the tool here: evilginx3+mastery. Most notably, changes to the phishlet file format will most likely break phishlets before version 3.0.0 and they will have to be rewritten. While it may be work to rewrite them, there are added benefits with the new phishlet file format. Documentation on the phishlet format for version 3.0.0 can be found here: Phishlet Format v3.0.0. Phishlets in the legacy format will still be kept in this repository in the folder evilginx3/legacy_phishlets. Phishlets compatible with version 3.x.x will be stored in evilginx3/phishlets in the private version of this repository for sponsors. Please refer to: A Word About Sponsorship

Since Apache2 is the initial proxy used in this project, all requests ever made to the phishing server will be logged to /var/log/apache2/access_evilginx3.log*. These logs can be viewed to show all access to the phishing server and assist in troubleshooting issues. Running evilginx3 with the -debug flag will show cookies, URLs, and contents of incoming/outgoing requests.

You can modify how Apache2 operates by modifying /etc/apache2/sites-enabled/000-default.conf. You can serve content from a static directory to host payloads, configure different proxies, etc. You can make any change Apache2 supports. Restarting the server is mandatory for changes to take effect.

The installation script was tested on Ubuntu Focal/Jammy and installs the latest version of Go from source. Binaries may fail to build depending on your Go environment and what you have installed i.e. installing the original versions this project combines then trying to install this version of them. It also makes changes to DNS so evilginx3 can take it over. You should understand the implications of this and review it. A fresh environment is recommended and other operating systems haven't been tested.

It is not uncommon to test the tracking for a campaign before it is launched and I encourage you to do so, I will just leave you with a warning. evilginx3 will create a cookie and establish a session for each new victim's browser. If you continue to test multiple campaigns and multiple phishing links within the same browser, you will confuse the tracking process since the RId value is parsed out of requests and set at the start of a new session. If you are doing this, you are not truly simulating a victim as a victim would never have access to another phishing link besides their own and goes without saying that this will never happen during a live campaign. This is to fair warn you not to open an issue for this as you are not using the tool the way it was intended to be used. If you would like to simulate a new victim, you can test the tracking process by using a new browser/tab in incognito mode.

The Apache blacklist is now optional. If you decide to use it, it may cause some clients to get blocked and disrupt the tracking process. The reason being is organizations may request links through a proxy falling in blocked ranges. It is up to you to perform test campaigns and verify if any blocking will disrupt your campaign tracking. A blocked client will receive a 403 Forbidden error. /var/log/apache2/access_evilginx3.log* can be viewed for remote IP addresses accessing the phishing server. You can remove entries in the /etc/apache2/blacklist.conf file that are causing a tracking issue and restart Apache. Or you can remove the Location block in the /etc/apache2/sites-enabled/000-default.conf file and restart Apache to remove IP blacklisting altogether. Users have also reported issues with setting evilginx3's built-in blacklist feature to unauth.

GoPhish is never used in any of your actual phishing pages and email headers have been stripped, so there's no need to worry about IOCs within it.

1. Default rid string in phishing URLs is chosen by the operator in setup.sh
2. Added SMS Campaign Support
3. Added additional Captured Session campaign event for captured evilginx3 sessions/tokens

See the CHANGELOG.md file for changes made since the initial release.

I have become extremely busy with work, private development projects, and research. The likelihood of receiving support for this project is extremely low. Issues without output are highly likely to be ignored/deleted.

On July 15, 2023 I decided to make some changes to the project. After this date, this project will always be kept one version behind the private version for sponsors. So this means the private version will contain additional features that Kuba Gretzky decides to add in upcoming version releases and I have pulled into my project as well as additional bug fixes. I will also not be updating the legacy phishlets in the public release here but will be maintaining them and updating them in the private release for sponsors. Be sure to sponsor me for access to the latest features of evilginx3, bug fixes, and phishlets. By sponsoring me in this tier, you will also get access to additional private repositories I have not released to the public!

• Additions to IP blacklist and redirect rules
• Continue to incorporate updates and bug fixes for evilginx3

I would like to see this project improve and grow over time. If you have improvement ideas, new redirect rules, new IP addresses/blocks to blacklist, phishlets, or suggestions, please open a pull request.