evilginx2
v3.3.0 open-sourceThe section your link pointed to isn't on evilginx2's page any more, so we've brought you to the top.
Evilginx2 is a man-in-the-middle attack framework used for phishing login credentials along with session cookies, bypassing 2-factor authentication.
lures pause <id>
# In phishlet config:
intercept:
- match:
url: ".*?/api"
respond:
status: 200
body: "Custom Response"
phishlet unauth_url <phishlet> <url>
config ipv4 bind 192.168.1.50
config ipv4 external 203.0.113.10
evilginx2 phishlet <phishlet>
evilginx2 phishlet create <phishlet>
lures edit <id> hostname evil-login.example.com
lures edit <id> ua_filter "Mozilla/5.0.*"
proxy socks5://127.0.0.1:9050
Summary
evilginx2 is an open-source man-in-the-middle phishing framework that captures login credentials and session cookies to defeat two-factor authentication, and it costs nothing to use. It runs as a standalone Go binary on a server you control, implementing its own HTTP and DNS handling so it can sit between a victim's browser and the real login page, proxying traffic through phishlets configured for specific targets. It is built for red teamers and penetration testers running authorized phishing engagements rather than for defenders, and the project explicitly restricts legitimate use to assignments with written permission. A commercial successor, Evilginx Pro, now exists alongside it for those wanting maintained phishlets and evasion features. The open-source project dates to 2018 with 31 contributors, but activity has slowed to just 3 commits in the past year and no release in over two years.
Evilginx2 is a man-in-the-middle attack framework used for phishing login credentials along with session cookies, bypassing 2-factor authentication.
How evilginx2 helps
Can a target's login page be reproduced closely enough to capture what they type into it?
proxies live traffic between the victim's browser and the real site using a phishlet configured for that target, forwarding requests both ways so the real content is served while credentials are captured in transit
Will a captured login survive the target's two-factor prompt?
passes the session cookies issued after the victim completes authentication back out through the proxy, so the operator holds a token that represents an already-authenticated session
Can this run without owning a nginx setup or a separate DNS server?
ships as a single Go binary with its own HTTP and DNS handling built in, so it can be pointed at a domain and terminate TLS itself rather than depending on external server infrastructure
Will a phished domain get flagged the moment someone probes it directly?
configuring an unauthorized-request response and enabling blacklisting on proxied hosts stops the framework from behaving differently for scanners than for real visitors, closing off one way it was previously fingerprinted
Can real certificates be used instead of relying on automatic issuance?
reads a certificate and private key pair placed under the site's hostname directory, so a custom TLS certificate can be loaded in place of the automatic LetsEncrypt retrieval
Will requests sitting behind a load balancer show the wrong source address in the logs?
recognizes the originating client IP forwarded by common reverse proxies, so the logged address reflects the actual visitor rather than the proxy in front of the server
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for evilginx2, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail evilginx2 puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
7 entries
No entries match these filters.
- April 20241
- August 20231
- July 20231
- May 20231
- September 20201
- January 20191
- November 20181
Project health
Issue, contributor and maintainer activity in kgretzky/evilginx2, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 +1 vs prior 12 months
- Maintainers 0 +1 joined · −1 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog not measured open issues today
- Issues opened / month not measured
- Open backlog not measured
- Contributors / month 0
- Commits / month 0
- Stars 15,654
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
2 articles · updated Nov 4, 2026Where evilginx2 turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.