AI prompts
base on 802.11 Attack Tool # AngryOxide š”
![Logo](death.png)
### A 802.11 Attack tool built in Rust š¦ !
[![Builds and Release](https://github.com/Ragnt/AngryOxide/actions/workflows/ci.yml/badge.svg?branch=master)](https://github.com/Ragnt/AngryOxide/actions/workflows/ci.yml) ![GitHub commit activity](https://img.shields.io/github/commit-activity/m/Ragnt/AngryOxide) [![Discord](https://img.shields.io/discord/1194365883099922643)](https://discord.gg/QsEgaFndsQ)
**This tool is for research purposes only. I am not responsible for anything you do or damage you cause while using AngryOxide. Only use against networks that you have permission.**
AngryOxide was developed as a way to learn Rust, netlink, kernel sockets, and WiFi exploitation all at once.
You can get information about how to use AngryOxide in the [User Guide](https://github.com/Ragnt/AngryOxide/wiki/1.-User-Guide).
NOTE: This project is under HEAVY development and you can expect a very fast release cycle.
The overall goal of this tool is to provide a single-interface survey capability with advanced automated attacks that result in valid hashlines you can crack with [Hashcat](https://hashcat.net/hashcat/).
This tool is heavily inspired by [hcxdumptool](https://github.com/ZerBea/hcxdumptool) and development wouldn't have been possible without help from ZerBea.
If you have questions or any issues, you can reach me on the [AngryOxide Discord](https://discord.gg/QsEgaFndsQ)
## I wanna use it!
You can download pre-compiled binaries of AngryOxide in the [releases](https://github.com/Ragnt/AngryOxide/releases/latest).
```bash
tar -xf angryoxide-linux-x86_64.tar.gz # Untar
chmod +x install.sh # Make executable
sudo ./install.sh # Install (as root, including zsh/bash completions)
```
You can get information about how to use AngryOxide in the [User Guide](https://github.com/Ragnt/AngryOxide/wiki/1.-User-Guide).
#### Uninstalling:
```bash
sudo ./install.sh uninstall # Uninstall
```
## Features
- Active state-based attack engine used to retrieve relevent EAPOL messages from Access Points and clients.
- Target option that accepts MAC (aabbcc..., aa:bb:cc...) and SSID "Test_SSID" to limit attack scope.
- Whitelist option to protect specific networks from attacks. Useful if not using targets.
- Auto Hunt capability to find all target channels and hop between them.
- A Terminal-UI that presents all relevent data while still living in the terminal for easy usage over SSH.
- A grepable "Headless" operation mode that simply prints status output, ready to be redirected to a log file.
- Limits DEAUTHENTICATION frames that can cause more damage than good to the authentication sequence.
- EAPOL 4-Way-Handshake validation using Nonce Correction, Replay Counter validation, and Temporal validation.
- Automatically elicits PMKID from access points where available.
- Utilizes GPSD with ability to set remote GPSD service address.
- Ability to enable geo-fencing to force AO to only run when inside a geometric area specified by a latitude, longitude, and radius.
- Provides pcapng files with embedded GPS using the [Kismet Format](https://www.kismetwireless.net/docs/dev/pcapng_gps/).
- Provides a kismetdb file with all frames (with GPS) for post-processing.
- Wraps all output files in a gzipped tarball.
- Bash autocompletions for easy interface selection provided.
## Attacks
Will by default attack ALL access points in range, unless atleast one target is supplied, at which point the tool will only transmit against defined targets. (But will still passively collect on other access points).
- Attempts authentication/association sequence to produce EAPOL Message 1 (PMKID Collection)
- Attempts to retrieve hidden SSID's with direct probe requests.
- Utilizes Anonymous Reassociation to force Access Points to deauthenticate their own clients (MFP Bypass)
- Will attempt to send Channel Switch Announcement to send clients to adjacent channels.
- Attempts to downgrade RSN modes to WPA2-CCMP (Probe Response Injection via RogueM2)
- Attempts to collect EAPOL M2 from stations based solely on Probe Requests (RogueM2)
- Attempts to disassociate clients using WiFi 6e codes that prevent blacklisting
- All attacks can be manually disabled.
All of these attacks are rate-controlled both to prevent erroneous EAPOL timer resets and to maintain some level of operational security.
## Help
```
āÆ angryoxide --help
Does awesome things... with wifi.
Usage: angryoxide [OPTIONS] --interface <INTERFACE>
Options:
-i, --interface <INTERFACE> Interface to use
-c, --channel <CHANNEL> Optional - Channel to scan. Will use "-c 1,6,11" if none specified
-b, --band <2 | 5 | 6 | 60> Optional - Entire band to scan - will include all channels interface can support
-o, --output <Output Filename> Optional - Output filename
-h, --help Print help
-V, --version Print version
Targeting:
-t, --target-entry <Target MAC/SSID>
Optional - Target (MAC or SSID) to attack - will attack everything if none specified
-w, --whitelist-entry <WhiteList MAC/SSID>
Optional - Whitelist (MAC or SSID) to NOT attack
--targetlist <Targets File>
Optional - File to load target entries from
--whitelist <Whitelist File>
Optional - File to load whitelist entries from
Advanced Options:
-r, --rate <Attack Rate> Optional - Attack rate (1, 2, 3 || 3 is most aggressive) [default: 2]
--combine Optional - Combine all hc22000 files into one large file for bulk processing
--noactive Optional - Disable Active Monitor mode
--rogue <MAC Address> Optional - Tx MAC for rogue-based attacks - will randomize if excluded
--gpsd <GPSD Host:Port> Optional - Alter default HOST:Port for GPSD connection [default: 127.0.0.1:2947]
--autohunt Optional - AO will auto-hunt all channels then lock in on the ones targets are on
--headless Optional - Set the tool to headless mode without a UI. (useful with --autoexit)
--autoexit Optional - AO will auto-exit when all targets have a valid hashline
--notransmit Optional - Do not transmit - passive only
--notar Optional - Do not tar output files
--disablemouse Optional - Disable mouse capture (scroll wheel)
--dwell <Dwell Time (seconds)> Optional - Adjust channel hop dwell time [default: 2]
Geofencing:
--geofence
Optional - Enable geofencing using a specified latlng and distance
--center <CENTER>
Lat,Lng for geofencing (required if geofence is enabled)
--distance <DISTANCE>
Distance in meters from the center (required if geofence is enabled)
--geofence-timeout <GEOFENCE_TIMEOUT>
Timeout to disable geofence if GPS is lost. (default 300 seconds) [default: 300]
Attacks:
--disable-deauth Optional - Do NOT send deauthentication attacks
--disable-pmkid Optional - Do NOT attempt to associate for PMKID
--disable-anon Optional - Do NOT send anonymous reassociation attacks
--disable-csa Optional - Do NOT send Channel Switch Announcment attacks
--disable-disassoc Optional - Do NOT send disassociation attacks
--disable-roguem2 Optional - Do NOT attempt rogue M2 collection
```
## Building from source
If you want to build from source instead of using precompiled binaries, these are the basic instructions:
```
# Install Rust
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
# Clone this repo
git clone --recurse-submodules https://github.com/Ragnt/AngryOxide.git
# Build/Install
cd AngryOxide
make
sudo make install
```
This will build from source, install into /usr/bin/angryoxide, and install the bash completions for you.
### Cross compiling:
I use [cross](https://github.com/cross-rs/cross) to cross compile to embedded architectures.
Here is MIPS (mips-unknown-linux-musl) as an example.
```
# make sure you have the nightly installed
rustup install nightly
# dynamically linked & soft-float
cross build +nightly --target mips-unknown-linux-musl --release -Zbuild-std
```
### Completions script:
These make using AngryOxide with bash and zsh a bit more fluid, automatically finding your wireless interfaces for you and showing you the arguments in a tab-completable way.
## Screenshots!
![Access Points Page](screenshots/ap_tab.png)
![Handshakes Page](screenshots/handshakes_tab.png)
", Assign "at most 3 tags" to the expected json: {"id":"7125","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"