offensive-wpa3-sae skillA
offensive-wpa3-sae is agent-read markdown (skill) from miosa-osa/osa: WPA3 / SAE (Simultaneous Authentication of Equals) attack methodology — transition-mode (mixed WPA2/WPA3) downgrade, Dragonblood side-channel attacks (CVE-2019-9494, 9495, 13377, 13456), SAE auth flooding for AP CPU exhaustion, Hash-to-Element (H2E) timing analysis, group downgrade, and 6 GHz / Wi-Fi 6E spec implications (PMF mandatory, no transition mode allowed). Use when target advertises WPA3-SAE or WPA3-Personal/Enterprise, or operates in 6 GHz where WPA3 + PMF are required by spec..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# WPA3 / SAE Attacks WPA3 fixes the offline-handshake-cracking weakness of WPA2 by replacing the 4-way PSK exchange with SAE (a Dragonfly-derived password-authenticated key exchange). The straightforward offline crack disappears — but transition-mode misconfigurations and the original SAE implementation's side-channel leaks open new paths. ## Quick Workflow 1. Verify the target advertises WPA3 (RSN IE shows AKM SAE = 8) 2. Check for transition-mode (mixed WPA2 + WPA3) — easiest path 3. If pure WPA3, fingerprint the AP's hostapd version for Dragonblood applicability 4. Side-channel timing or cache attacks if reachable 5. Otherwise, accept that offline cracking isn't viable — pivot to other surfaces --- ## Transition-Mode Downgrade If the AP advertises both WPA2-PSK and WPA3-SAE (transition mode for mixed-client networks), older clients can be forced onto WPA2: ```bash # Identify transition mode in beacon frames sudo airodump-ng wlan0mon -c <ch> --bssid <BSSID> # Encryption column shows WPA2 WPA3 (both) ``` Steps: 1. Spoof a beacon advertising **only RSN-WPA2** with the same BSSID/SSID 2. Client roams to your beacon, performs WPA2 4-way handshake …
Read the whole file at its exact version.
How to install
mdr add miosa-osa/osa/offensive-wpa3-sae@git:20260913.e13b6b8mdr add miosa-osa/osa/offensive-wpa3-sae@sha256:eed114e0cab31c50Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_dnggywjcpwgt466i)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7557 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
miosa-osa/osa · 74 stars · license NOASSERTION · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dnggywjcpwgt466i GET https://markdownregistry.com/api/v1/resolve?ref=miosa-osa/osa/offensive-wpa3-sae GET https://markdownregistry.com/api/v1/blob/eed114e0cab31c5083a0e439e1a8f66a402e6d95391d48c6be05a98ecffbb3e4
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.