wifiphisher
v1.4 open-sourceThe section your link pointed to isn't on wifiphisher's page any more, so we've brought you to the top.
Rogue Access Point framework for Wi-Fi phishing attacks, capturing credentials or delivering malware via Evil Twin, KARMA, and Known Beacons techniques.
wifiphisher --quitonsuccess -iI wlan0 wifiphisher --essid <TARGET_ESSID> wifiphisher --essid <TARGET_ESSID> --presharedkey <PASSWORD>
Summary
wifiphisher is an open-source, free command-line framework for staging rogue Wi-Fi access points, run from a laptop or a device like a Raspberry Pi against nearby wireless clients. It handles the association step itself, pushing targets onto an evil-twin or Known Beacons network, then hands off to customizable phishing pages to capture credentials or a WPAWPAA Wi-Fi authentication and encryption standard maintained by the Wi-Fi Alliance, replacing WEP; cyber tools target it to audit wireless network credentials and key exchange handshakes./WPA2 pre-shared key, with a Python extension system for writing new attack modules or scenarios. It is built for penetration testers and red teamers who need a man-in-the-middle position against Wi-Fi clients rather than the access point itself. First committed in 2014 and still maintained by 51 contributors, though it has seen only one commit in the past year, worth checking for how actively issues are handled before relying on it.
Rogue Access Point framework for Wi-Fi phishing attacks, capturing credentials or delivering malware via Evil Twin, KARMA, and Known Beacons techniques.
How wifiphisher helps
Which nearby wireless clients can be pulled onto an access point they never chose to join?
forces association through evil-twin, KARMA, or Known Beacons techniques rather than waiting for a client to connect voluntarily
Can a target's Wi-Fi password be recovered without cracking a captured handshake?
serves a customized phishing page after association and validates the WPA/WPA2 passphrase the victim types against the real network before ending the attack
What will an actual victim see when they land on the rogue portal?
ships a set of community-built phishing templates styled after router firmware updates, OAuth logins, or network manager prompts, chosen to fit the deployment scenario
Is the fake network staying connected to a moving or channel-hopping target AP?
monitors the target's channel during the engagement and adjusts so the rogue AP keeps tracking it instead of silently dropping the impersonation
Does a captured credential actually belong to the network being tested, or is it garbage a suspicious user typed in?
checks submitted WPA/WPA2 keys against the real handshake before accepting them, filtering out failed guesses
Can a one-off social-engineering scenario be built without touching the core tool?
exposes a Python extension system so new attack modules or custom phishing flows can be written and dropped in without modifying the framework itself
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 wifiphisher, 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 wifiphisher 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
4 entries
No entries match these filters.
- January 20181
- April 20171
- December 20161
- July 20151
Project health
Issue, contributor and maintainer activity in sophron/wifiphisher, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 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 14,853
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
1 article · updated Nov 4, 2026Where wifiphisher 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.
Tutorials & guides 1
-
WiFi Exploitation with WifiPhisher
Today we are going to demonstrate WIFI- Phishing attack by using the very great tool “WIFIphisher”, please read its description for more details.
2 more quotes
Wifiphisher is a security tool that mounts automated victim-customized phishing attacks against WiFi clients in order to obtain credentials or infect the victims with malware.
Wifiphisher Working After achieving a man-in-the-middle position using the Evil Twin or KARMA attack, Wifiphisher redirects all HTTP requests to an attacker-controlled phishing page.
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.