> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/hacking-wifi/wpa-wpa2-psk-network-attacks/evil-twin/evil-twin-attack.md).
# Evil Twin Attack
Understand Evil Twin wireless attacks, user impact, and practical defensive controls.
## Evil Twin: The Wi-Fi Impostor
An Evil Twin attack occurs when an attacker creates a fake Wi-Fi network. It uses the same name (SSID) as a legitimate network, such as one at a hotel or café. This tricks users into connecting to it.
### Attack process
1. **Cloning:** The attacker copies the real network's name.
2. **Disconnection:** They remove users from the legitimate network with a deauthentication attack.
3. **Connection:** The victim's device automatically reconnects to the fake Wi-Fi because it has a stronger signal.
### Main risks
By controlling the access point, the attacker intercepts all traffic in a man-in-the-middle attack. They can monitor user activity, redirect users to fake websites that steal passwords through phishing, or infect devices with malware.
### Protective measures
* Disable automatic connections to open Wi-Fi networks.
* Use a VPN when browsing on public networks.
* Be cautious if a familiar network suddenly requests credentials or personal data for access.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/hacking-wifi/wpa-wpa2-psk-network-attacks/evil-twin/evil-twin-attack.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.