offensive-wpa-enterprise skillA
offensive-wpa-enterprise is agent-read markdown (skill) from miosa-osa/osa: WPA/WPA2/WPA3-Enterprise (802.1X / EAP) attack methodology — EAP method identification (PEAP-MSCHAPv2, EAP-TTLS, EAP-TLS, EAP-GTC, EAP-PWD, EAP-FAST), evil-twin RADIUS attacks with eaphammer for credential capture, MSCHAPv2 challenge-response cracking, EAP-TLS client certificate theft paths (DPAPI, NDES, AD CS auto-enrollment), supplicant validation bypass (missing server cert validation, missing CN pinning, BYOD misconfigurations), and post-capture pivots into AD via cracked domain credentials..
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
# WPA-Enterprise (802.1X / EAP) Attacks Enterprise Wi-Fi delegates authentication to a RADIUS server — usually backed by AD. The PSK doesn't exist. Instead, you attack the supplicant's trust in the server certificate, the inner EAP method's crypto, or the cert-issuance path. ## Quick Workflow 1. Identify EAP method from beacons + initial EAP-Request/Identity 2. If MSCHAPv2-based (PEAP, TTLS): rogue RADIUS to capture challenge-response 3. If EAP-TLS: target the cert-issuance / cert-storage path (out of band) 4. Crack captured MSCHAPv2 offline → AD username + password 5. Pivot into the domain (see `offensive-active-directory` and `offensive-network`) --- ## EAP Method Identification ```bash # Watch 802.1X exchange in monitor mode sudo tshark -i wlan0mon -Y "eapol || eap" -V # Or capture and analyze sudo airodump-ng wlan0mon -c <ch> --bssid <BSSID> -w eap_capture # When client associates, read the EAP-Request/Identity and Type fields wireshark eap_capture-01.cap ``` | EAP Type | Identifier | Common Inner | |---|---|---| | 13 | EAP-TLS | Client + server certs | | 17 | LEAP | (legacy, weak) | | 21 | EAP-TTLS | MSCHAPv2 / PAP / CHAP / GTC | …
Read the whole file at its exact version.
How to install
mdr add miosa-osa/osa/offensive-wpa-enterprise@git:20260913.e13b6b8mdr add miosa-osa/osa/offensive-wpa-enterprise@sha256:915ea80c6ea987a6Pin 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_hawgnyae4cgh4zjs)
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 (8829 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_hawgnyae4cgh4zjs GET https://markdownregistry.com/api/v1/resolve?ref=miosa-osa/osa/offensive-wpa-enterprise GET https://markdownregistry.com/api/v1/blob/915ea80c6ea987a690464094a2e832136795dc0dff803e40327c4a90c94e8578
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.