The section your link pointed to isn't on wifipumpkin3's page any more, so we've brought you to the top.
wifipumpkin3 is a Python framework for rogue access point attacks that allows security researchers to mount a wireless network and conduct man-in-the-middle attacks.
curl http://localhost:8080/api/v1/attack/start wifipumpkin3 -m custom_captiveflask wp3 > dhcpconf wp3 > hostapd_config curl http://localhost:1337/api/v1/status dhcp server=dnsmasq modules load dns_spoof kill 12345 proxy --ssid 'Café_Network'
wifipumpkin3 is an open-source command-line framework for staging rogue access point attacks, free to use, run from a Linux machine with hostapd installed. It lets an operator stand up a fake WiFi network and sit in the middle of a victim's traffic, adding modules for deauthentication, captive-portal phishing, DNS spoofing, and credential harvesting, with QR-code and MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. phishing variants layered on top. It has been maintained since 2018 by 13 contributors, though there have been no commits in the past year, so anyone shortlisting it should check whether the current release still fits their hardware and OS before relying on it.
wifipumpkin3 is a Python framework for rogue access point attacks that allows security researchers to mount a wireless network and conduct man-in-the-middle attacks.
shows connected clients in a real-time logger view, so the operator can see who joined the rogue access point as it happens
captures credentials submitted through the captive portal templates and surfaces them through the harvesting module
intercepts and monitors DNS requests through the rogue DNS server, giving a live view of the domains a client is resolving
routes the victim through a captive-portal flow built for MFA phishing, walking them past a login step so an operator can capture the follow-on code
swaps in the QR-phishing proxy variant, generating a scannable code tied to the same phishing backend as the captive portal
offers a forced-redirect option that sends the user on to a chosen website once login has been recorded, keeping the interception invisible after the fact
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.
Nine scores for wifipumpkin3, 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 →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.
See how much detail wifipumpkin3 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…
17 entries
No entries match these filters.
Issue, contributor and maintainer activity in P0cL4bs/wifipumpkin3, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
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
Where wifipumpkin3 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.
Wifipumpkin3 is a framework built on Python to give rogue access point attacks to red teamers and reverse engineers.
In this article, we will explore how to use Wifipumpkin3 to create a bogus Wi-Fi access point for our victims to connect.
Table of Content Overview Installing Wifipumpkin3 Using captive portal attack Generating Custom Captiveflask Writing pulp file for Wifipumpkin One-liner attack DNS Spoof with Wifipumkin Overview wifipumpkin3 is a…
pyjwt 2.1.0 in its imagecritical
wifipumpkin3 1.1.7 builds its image from requirements.txt, which locks pyjwt 2.1.0. That version has GHSA-ffc3-869f-jxw9 and 5 other high or critical flaws.
Fixed in pyjwt 2.14.0. No wifipumpkin3 release includes it yet.
GHSA-ffc3-869f-jxw9 advisory Checked Nov 3 against wifipumpkin3 1.1.7
dnspython 1.16.0 in its imagehigh
wifipumpkin3 1.1.7 builds its image from requirements.txt, which locks dnspython 1.16.0. That version has GHSA-45c3-73f7-pv4m.
Fixed in dnspython 2.9.0. No wifipumpkin3 release includes it yet.
GHSA-45c3-73f7-pv4m advisory Checked Nov 3 against wifipumpkin3 1.1.7
We check the lockfiles its release builds images from: 1 Python. Go modules, other lockfiles and vendored code aren't checked.
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →