Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An evil twin is a rogue wireless access point impersonating a legitimate network, so that clients associate with the attacker and hand over traffic, credentials, or enterprise authentication material.

What Is an Evil Twin Attack?
Wi-Fi clients identify networks by name. That is the whole weakness. An evil twin attack stands up an access point broadcasting the same SSID as a network the target trusts, usually with a stronger signal, and waits for devices to associate. Once they do, the attacker is the network: every unencrypted request, every DNS lookup, and every captive portal the user sees is under their control.
The hardware cost is negligible — a laptop with a second adapter, or a purpose-built device such as a WiFi Pineapple. The skill requirement dropped years ago with tools like hostapd-wpe, eaphammer, and wifiphisher, which script the whole sequence.
A variant known as a karma attack skips the first step. Devices with saved networks broadcast probe requests asking whether a particular SSID is nearby; the rogue access point answers yes to all of them, and clients configured to auto-join connect without any user action at all.
WPA2-Enterprise with 802.1X is often assumed to solve this, and it can — but only when configured correctly. In an EAP relay, the rogue access point presents itself as the corporate network and the supplicant begins authentication against it. With PEAP-MSCHAPv2, the attacker receives the challenge-response pair, which is then cracked offline with asleap or hashcat to recover the domain password. Nothing on the client indicates anything unusual.
What prevents it is certificate validation. The supplicant must be configured to verify the authentication server’s certificate, pin the issuing certificate authority, and refuse to prompt the user for exceptions. On Windows this is set through group policy; on managed mobile devices through the configuration profile. Where the organisation deploys EAP-TLS with client certificates, there is no password to relay in the first place.
For organisations, the practical set is short. Deploy EAP-TLS or enforce server certificate validation with CA pinning across every managed device, including phones and tablets. Enable Protected Management Frames (802.11w) so clients cannot be forced off the real network. Run a wireless intrusion detection system — enterprise controllers from the major vendors will report a duplicate SSID broadcasting from an unknown radio, which is a high-fidelity alert. Use WPA3 where the estate supports it, and offer guest access as Wi-Fi Enhanced Open rather than a genuinely open network, so that traffic is encrypted even without a shared password.
For individuals, the advice is unglamorous but effective: turn off automatic connection to open networks, remove saved public SSIDs, use a VPN on untrusted Wi-Fi, and treat a portal that asks for a work password as hostile. Mobile data is almost always the safer option.
Rogue access point testing forms part of our Penetration Test Services, and in office environments it tends to be the exercise that produces the clearest evidence of how client devices are actually configured.
A rogue access point is any unauthorised access point attached to a network, often an employee’s own router plugged in for convenience. An evil twin is specifically an access point impersonating a known SSID in order to attract clients. The first is usually a governance failure; the second is a deliberate attack, although a rogue device can of course be used as one.
Largely, yes. Once the tunnel is established, traffic is encrypted and authenticated end to end, so the operator of the wireless network sees only encrypted packets and destination endpoints. The gaps are the moments before the tunnel comes up, captive portal interactions, DNS requests that leak outside the tunnel, and any client that silently falls back when the VPN fails.
Not reliably. The SSID matches, the signal is often stronger, and modern tools reproduce captive portals convincingly. Clues include an unexpected certificate warning, a login page appearing on a network that never asked for one, and a sudden disconnection followed by reconnection. Because these are weak signals, the defence belongs in device configuration rather than user vigilance.
Without it, the client authenticates to whichever server answers, which is exactly what an attacker needs for an EAP relay. With PEAP-MSCHAPv2 the captured challenge-response can be cracked offline to recover a domain password. Validating and pinning the authentication server’s certificate means the supplicant refuses to continue when the server is not yours, and the attack stops at that point.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.