Skip to content
← RegistryDossier · 6 steps · 5 edges

WPA2-PSK handshake capture + crack → LAN access

Deauth a connected client to force re-association, capture the 4-way handshake with airodump-ng, crack the PSK offline with hashcat.

Filed by AD Knowledge Base
§ Kill-chainDrag · zoom · scroll

§ Context

Assumed environment: target Wi-Fi is WPA2-PSK (not enterprise). At least one client is currently associated. Attacker is in RF range with a monitor-mode-capable card.

§ Steps

  1. 01
    Authenticate to the networkInitial Access
    T1078Valid Accounts
  2. 02
    hashcat -m 22000 offlineCredential Access
    T1110Brute Force
  3. 03
    airodump-ng → enumerate APs + clientsReconnaissance
    N-ARP-RECONARP Sweep / LAN Discovery
  4. 04
    Internal nmap + LLMNR poisonDiscovery
    N-NMAP-INTERNALInternal Nmap Sweep
  5. 05
    Capture 4-way handshakeCredential Access
    WIFI-WPA2-PSKWPA2-PSK Handshake Capture + Crack
  6. 06
    aireplay-ng deauth a clientImpact
    WIFI-DEAUTHDeauthentication DoS

§ References

§ Frequently asked

What is the "WPA2-PSK handshake capture + crack → LAN access" attack path?
Deauth a connected client to force re-association, capture the 4-way handshake with airodump-ng, crack the PSK offline with hashcat. It chains 6 steps drawn from real-world offensive-security techniques.
What starting position does this attack require?
The first step is Authenticate to the network (T1078) — a initial access primitive. Assumed environment: target Wi-Fi is WPA2-PSK (not enterprise).
What is the final impact of this kill-chain?
The final step lands on aireplay-ng deauth a client (WIFI-DEAUTH), which falls under Impact. From here, an operator typically pivots into post-exploitation or maintains persistence.
How can defenders detect or prevent this attack?
Detection and prevention vary per step. Refer to each linked MITRE ATT&CK entry under "References" — every technique on that page lists defensive controls, detection telemetry, and known threat-actor usage.

§ Related dossiers