AngryOxide
v0.8.20 open-sourceThe section your link pointed to isn't on AngryOxide's page any more, so we've brought you to the top.
AngryOxide is an 802.11 attack tool built in Rust that performs automated Wi-Fi attacks to collect hashlines crackable with Hashcat.
# Commented out target #192.168.1.100 192.168.1.101 # Active scan this one # Whitelisted BSSID AA:BB:CC:DD:EE:FF # Allowed access point 11:22:33:44:55:66 # Another allowed AP angryoxide -b 2,5 angryoxide --channel <target_channel> --lock angryoxide --dwell-time <seconds> angryoxide --targets <path_to_targets_file> angryoxide --combine angryoxide --auto-hunt
Summary
AngryOxide is an open-source command-line tool for attacking 802.11 wireless networks, written in Rust and free to use. It runs directly on a wireless interface from the terminal (including over SSH, via its terminal UI), actively engaging access points and clients to capture EAPOL handshakes and PMKIDPMKIDA 128-bit identifier derived from a PMK, the access point MAC, and the client MAC in WPA2 handshakes, allowing offline cracking of Wi-Fi passwords without capturing a full four-way handshake. hashes that feed into Hashcat for offline cracking, with target and whitelist options to scope or protect specific networks and an auto-hunt mode to sweep channels. It's aimed at penetration testers and wireless security researchers rather than defenders, and the README credits hcxdumptool as its inspiration, positioning AngryOxide as a Rust-based alternative for the same handshake-capture workflow. First committed in 2023, it has seen 340 commits and 10 releases in the past year, with the maintainers describing it as under heavy, active development.
AngryOxide is an 802.11 attack tool built in Rust that performs automated Wi-Fi attacks to collect hashlines crackable with Hashcat.
How AngryOxide helps
Which access points and clients in range have a handshake worth capturing?
actively engages targeted access points and their associated clients over the interface, forcing the exchange of EAPOL messages so a valid handshake can be captured rather than waiting passively for one to occur
Can I get a crackable hash from a network without ever seeing a client connect?
grabs the PMKID from the access point directly during the state-based attack, giving a hash line for Hashcat even when no client handshake is observed
Which of the networks I'm surveying should never be touched during a test?
checks every target against a whitelist of MACs or SSIDs before attacking, so networks named there are left alone while the rest of the sweep continues
Am I only capturing traffic from the specific network I'm authorized to test?
restricts all active attacks to the MAC addresses or SSIDs given as targets, so hosts outside that scope are observed but not engaged
How do I cover every channel in range without manually retuning the radio?
auto-hunt sweeps and hops across all channels holding targets, keeping the interface on each long enough to catch the relevant EAPOL exchange before moving on
Can I run a survey and watch results live over a remote session?
presents captured handshakes, PMKIDs, and target status in a terminal UI that updates as it runs, staying usable over an SSH session rather than requiring a local desktop
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for AngryOxide, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail AngryOxide puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
10 entries
No entries match these filters.
- August 20241
- May 20241
- March 20241
- February 20244
- January 20243
Project health
Issue, contributor and maintainer activity in Ragnt/AngryOxide, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 −1 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 0.1 hours
- Open backlog 17 of 48 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 17
- Contributors / month 0
- Commits / month 0
- Stars 1,956
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →