Hubbry Logo
Aircrack-ngAircrack-ngMain
Open search
Aircrack-ng
Community hub
Aircrack-ng
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Aircrack-ng
Aircrack-ng
from Wikipedia
aircrack-ng
Original authorChristophe Devine
DeveloperThomas d'Otreppe de Bouvette
Stable release
1.7 / May 10, 2022 (2022-05-10)[1]
Repositoryhttps://github.com/aircrack-ng/aircrack-ng
Written inC
Operating systemCross-platform
TypePacket sniffer and injector; WEP, WPA, WPA2 key recovery
LicenseGPL
Websitewww.aircrack-ng.org

Aircrack-ng is a network software suite consisting of a detector, packet sniffer, WEP and WPA/WPA2-PSK cracker and analysis tool for 802.11 wireless LANs. It works with any wireless network interface controller whose driver supports raw monitoring mode and can sniff 802.11a, 802.11b and 802.11g traffic. Packages are released for Linux and Windows.[2]

Aircrack-ng is a fork of the original Aircrack project. It can be found as a preinstalled tool in many security-focused Linux distributions such as Kali Linux or Parrot Security OS,[3] which share common attributes, as they are developed under the same project (Debian).[4]

Development

[edit]

Aircrack was originally developed by French security researcher Christophe Devine.[5] Its main goal was to recover 802.11 wireless networks WEP keys using an implementation of the Fluhrer, Mantin and Shamir (FMS) attack alongside the ones shared by a hacker named KoreK.[6][7][8]

Aircrack was forked by Thomas D'Otreppe in February 2006 and released as Aircrack-ng (Aircrack Next Generation).[9]

Wi-Fi security history

[edit]

WEP

[edit]
Basic WEP encryption: RC4 keystream XORed with plaintext.

Wired Equivalent Privacy was the first security algorithm to be released, with the intention of providing data confidentiality comparable to that of a traditional wired network.[10] It was introduced in 1997 as part of the IEEE 802.11 technical standard and based on the RC4 cipher and the CRC-32 checksum algorithm for integrity.[11]

Due to U.S. restrictions on the export of cryptographic algorithms, WEP was effectively limited to 64-bit encryption.[12] Of this, 40 bits were allocated to the key and 24 bits to the initialization vector (IV), to form the RC4 key. After the restrictions were lifted, versions of WEP with a stronger encryption were released with 128 bits: 104 bits for the key size and 24 bits for the initialization vector, known as WEP2.[13][14]

The initialization vector works as a seed, which is prepended to the key. Via the key-scheduling algorithm (KSA), the seed is used to initialize the RC4 cipher's state. The output of RC4's pseudo random generation algorithm (PRGA) follows a XOR operation in combination with the plaintext, and produces the ciphertext.[15]

The IV is constrained to 24 bits, which means that its maximum values are 16,777,216 (224), regardless of the key size.[16] Since the IV values will eventually be reused and collide (given enough packets and time), WEP is vulnerable to statistical attacks.[17] William Arbaugh notes that a 50% chance of a collision exists after 4823 packets.[18]

In 2003, the Wi-Fi Alliance announced that WEP had been superseded by Wi-Fi Protected Access (WPA). In 2004, with the ratification of the full 802.11i standard (i.e. WPA2), the IEEE declared that both WEP and WEP2 have been deprecated.[19]

WPA

[edit]

Wi-Fi Protected Access (WPA) was designed to be implemented through firmware updates rather than requiring dedicated hardware.[20] While still using RC4 at its core, it introduced significant improvements over its predecessor. WPA included two modes: WPA-PSK (WPA Personal) and WPA Enterprise.

WPA-PSK (Wi-Fi Protected Access Pre-Shared Key), also known as WPA Personal, used a variant of the Temporal Key Integrity Protocol (TKIP) encryption protocol. It improved security by implementing the following features:

TKIP allocated 48 bits to the IV compared to the 24 bits of WEP, so the maximum number is 281,474,976,710,656 (248).[22]

In WPA-PSK, each packet was individually encrypted using the IV information, the MAC address, and the pre-shared key as inputs. The RC4 cipher was used to encrypt the packet content with the derived encryption key.[22]

Additionally, WPA introduced WPA Enterprise, which provided enhanced security for enterprise-level networks. WPA Enterprise employed a more robust authentication mechanism known as Extensible Authentication Protocol (EAP). This mode required the use of an Authentication Server (AS) such as RADIUS (Remote Authentication Dial-In User Service) to validate user credentials and grant access to the network.

In 2015, the Wi-Fi Alliance recommended in a technical note that network administrators should discourage the use of WPA and that vendors should remove support for it and rely instead on the newer WPA2 standard.[24]

WPA2

[edit]

WPA2 (Wi-Fi Protected Access 2) was developed as an upgrade to the original WPA standard and ratified in 2004, and became mandatory for Wi-Fi certified products in 2006.[25] Like WPA, WPA2 provides two modes: WPA2-PSK (WPA2 Personal) and WPA2 Enterprise.[26]

Unlike WPA, WPA2-PSK uses the more secure Advanced Encryption Standard (AES) in CCM mode (Counter-Mode-CBC-MAC Protocol), instead of TKIP.[21] AES provides stronger authentication, encryption and is less vulnerable to attacks.[27][28] A backward compatible version, called WPA/WPA2 (Personal) still made use of TKIP.[29]

WPA2-PSK replaces the message integrity code Michael with CCMP.[21]

Timeline of the attacks

[edit]

WEP

[edit]

In 1995, before the WEP standard was available, computer scientist David Wagner of the Princeton University discussed a potential vulnerability in RC4.[15]

In March 2000, a presentation by Dan Simon, Bernard Aboba, and Tim Moore of Microsoft provided a summary of 802.11 vulnerabilities. They noted that denial of service deauthentication attacks are possible because the messages are unauthenticated and unencrypted (later implemented by the aireplay-ng tool).[30] In addition, they wrote that because some implementations of WEP derive the key from a password, dictionary attacks are easier than pure brute force.[31][17]

In May 2001, William A. Arbaugh of the University of Maryland presented his inductive chosen-plaintext attack against WEP with the conclusion that the protocol is vulnerable to packet forgery.[18]

In July 2001, Borisov et al. published a comprehensive paper on the status of WEP and its various vulnerabilities.[17]

In August 2001, in the paper Weaknesses in the Key Scheduling Algorithm of RC4, authors Scott Fluhrer, Itsik Mantin, and Adi Shamir performed a cryptoanalysis of the KSA, citing Wagner among others. They stated that they had not conducted an attack against WEP, and therefore couldn't claim that WEP was vulnerable.[32] However, other researchers implemented the attack and were able to demonstrate the protocol's insecurity.[33][13]

In 2004, a hacker using the pseudonym KoreK posted a series of attacks on the NetStumbler.org forum, which were incorporated into the original aircrack 1.2 by Christophe Devine.[34][35] That same month, aircrack began supporting replay attacks against WEP, which use ARP requests to generate more IVs and make key recovery easier.[36]

Later that year, KoreK released the Chopchop attack, an active packet injector for WEP.[37] The name of the attack derives from its inherent working: a packet is intercepted, "chops" off a part of it and sends a modified version to the Access Point, who will drop it if not valid. By repeatedly trying multiple values, the message can gradually be decrypted.[37][38][39] The Chopchop attack was later improved by independent researchers.[40]

In 2005, security researcher Andrea Bittau presented the paper The Fragmentation Attack in Practice. The homonymous attack exploits the fact that WEP splits the data into smaller fragments, which are reassembled by the receiver. Taking advantage of the fact that at least part of the plaintext of some packets may be known, and that the fragments may have the same IV, data can be injected at will, flooding the network to statistically increase the chances of recovering the key.[15]

In April 2007 a team at the Darmstadt University of Technology in Germany presented a new attack, named "PTW" (from the researchers' names, Pyshkin, Tews, Weinmann). It decreased the number of initialization vectors or IVs needed to decrypt a WEP key and has been included in the aircrack-ng suite since the 0.9 release.[41][42]

Evolution of the attacks/vulnerabilities
Date Author/s Attack name/type Packets needed Implemented in Source
2001 A. Stubblefield et al. FMS: Passive partial key exposure attack 1,000,000 (optimized from 5,000,000 to 6,000,000) - [33][43]
2001 W. Arbaugh Inductive chosen plaintext - [18]
2002 David Hulton Practical Exploitation of RC4 Weaknesses in WEP Environments 500,000-2,000,000 - [44]
2003 Andrea Bittau Expansion of FMS classes - [45]
2004 KoreK FMS: Passive partial key exposure attack 700,000 (about 50% success probability) aircrack 1.2 [46]
2004 KoreK Chopchop aircrack 2.2-beta1 [37][35]
2006 A. Klein Attacks on the RC4 stream cipher - [47]
2007 Tews, Weinmann, Pyshkin PTW 35,000 to 40,000 (about 50% success probability) aircrack-ng 0.9 [46]
2007 S. Vaudenay and M. Vuagnoux VX: Passive key recovery 45'000 - [48]

WPA

[edit]

The first known attack on WPA was described by Martin Beck and Erik Tews in November 2008. They described an attack against TKIP in the paper Practical Attacks Against WEP and WPA. The proof of concept resulted in the creation of tkiptun-ng.[46] In 2009, their attack was improved and demonstrated by a research group from Norway.[47]

Features

[edit]

The aircrack-ng software suite includes:

aircrack-ng

[edit]

aircrack-ng supports cracking WEP (FMS, PTW, KoreK and dictionary attacks), WPA/WPA2 and WPA2 keys (using dictionary attacks).[49] While it doesn't support direct attacks on WPA3 (introduced in 2018), it has been used successfully in combination with a downgrade attack.[50]

airbase-ng

[edit]

airbase-ng incorporates techniques for attacking clients, instead of Access Points. Some of its features include an implementation of the Caffe Latte attack (developed by security researcher Vivek Ramachandran)[51] and the Hirte attack (developed by Martin Beck).[52] The WEP Hirte attack is a method of creating an Access Point with the same SSID of the network to be exploited (similar to an evil twin attack).[53] If a client (that was previously connected to the victim's access point) is configured to automatically reconnect, it will try the rogue AP. At this point, ARP packets are sent in the process of obtaining a local IP address, and airbase-ng can collect IVs that can later be used by aircrack-ng to recover the key.[54]

Execution of a fragmentation attack against WEP with aireplay-ng.

aireplay-ng

[edit]

aireplay-ng is an injector and frame replay tool.[49][55] Deauthentication attacks are supported.[30] Deauthentication refers to a feature of IEEE 802.11 which is described as "sanctioned technique to inform a rogue station that they have been disconnected from the network".[56] Since this management frame doesn't need to be encrypted and can be generated knowing only the client's MAC address, aireplay-ng can force a client to disconnect and capture the handshake (or to perform a Denial of service attack). In addition, a client deauthentication and subsequent reconnection will reveal a hidden SSID.[30]

Other features include the ability to perform fake authentification, ARP request replay, fragmentation attack, the Caffe Latte and Chopchop attacks.[57]

airmon-ng

[edit]

airmon-ng can place supported wireless cards in monitor mode.[49] Monitor mode refers to a provision in the IEEE 802.11 standard for auditing and design purposes,[58] in which a wireless card can capture packets in air range.[59] It is able to detect potential programs that could interfere with proper operation and kill them.[citation needed]

A Linux terminal shows the airmon-ng command running twice. The first time to show the available adapters, and the second time to set the monitor mode with the correct interface name.
Setting monitor mode using airmon-ng.

airodump-ng

[edit]
A Linux terminal shows the airodump-ng command running. It shows a single Access Point named Wikimedia Commons Demo.
A network scan is performed using airodump-ng.

airodump-ng is a packet sniffer.[49] It can store information in various formats, making it compatible with software other than the aircrack-ng suite. It supports channel-hopping.[60]

airserv-ng

[edit]

airserv-ng is a wireless card server, which allows multiple wireless programs to use a card independently.[61]

airtun-ng

[edit]

Virtual tunnel interface creator. Its main uses are monitoring the traffic as an intrusion detection system, and inject arbitrary traffic in a network.[62]

besside-ng

[edit]

A tool to automatize WEP cracking and logging of WPA handshakes.

easside-ng

[edit]

easside-ng is an automated tool which attempts connection to a WEP Access Point without knowing the encryption key. It uses the fragmentation attack and a remote server (which can be hosted with the tool buddy-ng) in the attempt to recover an encrypted packet, exploiting the AP which will decrypt it for the attacker.[63]

tkiptun-ng

[edit]

tkiptun-ng is a WPA/TKIP attack tool developed by Martin Beck.

wesside-ng

[edit]

wesside-ng is a proof of concept based on the tool wesside, originally written by Andrea Bittau to demonstrate his fragmentation attack. It is a tool designed to automate the process of recovering a WEP key.[15]

airdecap-ng

[edit]

airdecap-ng decrypts WEP or WPA encrypted capture files with known key.[36] It was formally known as airunwep and 802ether.[35]

airdecloak-ng

[edit]

airdecloak-ng can remove WEP cloaked frames from pcap files. Cloaking refers to a technique for use by wireless intrusion prevention systems (which rely on WEP encryption) to inject packets encrypted with random keys into the air, in the attempt to make cracking more difficult.[64]

airolib-ng

[edit]

airolib-ng can create a database of pre-computed hash tables by computing the Pairwise Master Keys (PMK) captured during the 4-way handshaking process.[65] In WPA and WPA2, the PMK are derived from the password selected by the user, the SSID name, its length, the number of hashing iterations, and the key length.[66][6] During the 4-way handshaking process, the PMK is used, among other parameters, to generate a Pairwise Transient Key (PTK), which is used to encrypt data between the client and Access Point.[67][68]

The hash tables can be reused, provided the SSID is the same.[69] Pre-computed tables for the most common SSIDs are available online.[70]

besside-ng-crawler is seen filtering files in a directory.

besside-ng-crawler

[edit]

Performs operations on a directory to search for pcap files and filter out relevant data.

buddy-ng

[edit]

buddy-ng is a tool used in conjunction with the tool easside-ng, running on a remote computer. It is the receiving end that allows a packet decrypted by the access point to be captured.[63]

ivstools

[edit]

ivstools can extract initialization vectors from a capture file (.cap).

kstats

[edit]

kstats is a tool for displaying the Fluhrer, Mantin and Shamir attack algorithm votes[note 1] for an IVS dump with a given WEP key.

makeivs-ng

[edit]

makeivs-ng is a testing tool used to generate an IVS file with a given WEP key.

packetforge-ng

[edit]
wpaclean in use.

packetforge-ng can create and modify packets for injection. It supports packets such as arp requests, UDP, ICMP and custom packets.[71] It was originally written by Martin Beck.[72]

wpaclean

[edit]

wpaclean reduces the contents of the capture file (generated by airodump-ng) by keeping only what is related to the 4-way handshake and a beacon. The former refers to a cryptographic process that establishes encryption without publicly revealing the key.[73] Meanwhile, the beacon frame is sent by the Access Point to announce its presence and other information to nearby clients.[74][75]

airventriloquist-ng

[edit]

airventriloquist-ng is a tool that can perform injection on encrypted packets.

Version history

[edit]
Aircrack changelog[35]
Version Date Notable changes
1.0 July 29, 2004
1.1 August 11, 2004 Implementation of ARP replay attack.
1.2 August 17, 2004 First implementation of KoreK attacks.
1.3 August 19, 2004
1.4 August 26, 2004
2.0 September 3, 2004
2.0.1 September 21, 2004
2.0.2 September 24, 2004
2.1 October 1, 2004 Added support for longer WEP keys (256 and 512 bit).
2.2-beta1 June 22, 2005 Chopchop attack is implemented. WPA-PSK support is added.
2.2-beta2 June 27, 2005 The aireplay tool implements automated replay, deauthentication attacks, and fake authentication.
2.2-beta3 June 28, 2005
2.2-beta4 July 3, 2005
2.2-beta5 July 10, 2005 WPA2 support is added.
2.2-beta6 July 12, 2005
2.2-beta7 July 14, 2005
2.2-beta8 and 2.2-beta9 July 21, 2005
2.2-beta10 July 23, 2005
2.2-beta11 July 27, 2005
2.2-beta12 July 30, 2005
2.2 August 3, 2005
2.21 August 9, 2005
2.22 August 14, 2005
2.23 August 28, 2005
2.4 November 12, 2005
2.41 November 22, 2005
Aircrack-ng changelog[72]
Version Date Notable changes
0.1 Unknown Forked from aircrack 2.41.
0.2 March 19, 2006
0.2.1 March 20, 2006
0.3 March 30, 2006 The tool ivstools is introduced, merged from two other software.
0.4 April 16, 2006
0.4.1 April 19, 2006
0.4.2 April 20, 2006
0.4.3 and 0.4.4 April 24, 2006
0.5 May 5, 2006 Further optimization of the Chopchop code.
0.6 June 23, 2006
0.6.1 August 27, 2006
0.6.2 October 1, 2006 packetforge-ng is introduced.
0.7 January 20, 2007
0.8 April 25, 2007
0.9 April 13, 2007 First implementation of PTW attack.
0.9.1 June 25, 2007
1.0-beta1 October 1, 2007 PTW attack supersedes KoreK attack as the default. The tools airdriver-ng, wesside-ng, easside-ng, buddy-ng, airserv-ng and airolib-ng are introduced.
1.0-beta2 February 1, 2008 Reduced number of packets needed for WPA attacks.
0.9.2 February 5, 2008
0.9.3 February 24, 2008
1.0-rc1 June 9, 2008 airbase-ng is introduced. Caffe latte and CFrag attacks are implemented.
1.0-rc2 January 22, 2009 tkip-tun is introduced.
1.0-rc3 March 26, 2009
1.0-rc4 July 27, 2009
1.0 September 8, 2009
1.1 April 24, 2010 airdrop-ng is introduced.
1.2-beta1 May 25, 2013 wpaclean is introduced. Migration mode attack is added in aireplay-ng.
1.2-beta2 November 30, 2013
1.2-beta3 March 31, 2014
1.2-rc1 October 31, 2014
1.2-rc2 April 10, 2015
1.2-rc3 November 21, 2015
1.2-rc4 February 14, 2016
1.2-rc5 April 3, 2018 airventriloquist-ng is introduced.
1.2 April 15, 2018
1.3 July 10, 2018
1.4 September 29, 2018
1.5.2 December 9, 2018
1.6 January 25, 2020 airodump-ng supports viewing WPA3 networks.
1.7 May 10, 2022

See also

[edit]

Notes

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia
from Grokipedia
Aircrack-ng is a complete suite of command-line tools designed to assess the security of networks, with a focus on monitoring, attacking, testing, and cracking capabilities for 802.11 wireless LANs. The suite enables packet capture and export for analysis, replay and deauthentication attacks through , testing of card and driver capabilities for capture and injection, and recovery of WEP keys using methods like PTW (introduced in 2007) or FMS/KoreK, as well as WPA/WPA2-PSK keys via dictionary attacks on captured handshakes. It supports optimizations such as , AVX, AVX2, and for accelerated processing, and is compatible with platforms including , Windows, macOS, , , , Solaris, and eComStation 2. Originating as an evolution of the earlier Aircrack project, Aircrack-ng was developed starting around 2005 by Christophe Devine and a community of contributors, with key advancements like the PTW method enhancing WEP cracking efficiency by extending statistical analysis. The project has seen active open-source development on , amassing over 4,000 commits by its 1.7 release in May 2022 (as of November 2025, the latest stable version), which added support for 6E, WPA3/OWE detection, and compatibility. Recognized by authoritative bodies like the (CISA) for evaluating wireless password strength, Aircrack-ng emphasizes ethical use in security auditing while warning against unauthorized access.

Development and History

Origins and Fork

The original Aircrack tool was developed by French security researcher Christophe Devine and first published in July 2003. It primarily focused on recovering (WEP) keys from captured wireless packets using statistical attacks, such as the Fluhrer-Mantin-Shamir (FMS) method, which exploited weaknesses in the initialization. This tool emerged amid growing awareness of vulnerabilities following the 2001 publication of the FMS attack paper, enabling practical demonstrations of WEP's insecurity for educational and auditing purposes. By 2005, the original Aircrack had reached version 2.41 but exhibited limitations, including poor code modularity, lack of support for emerging protocols like WPA, and restricted platform compatibility primarily to . In response, Thomas d'Otreppe de Bouvette initiated a in 2006, creating Aircrack-ng (Aircrack Next Generation) to address these issues through improved maintainability, modular design, addition of new features such as WPA-PSK cracking, and broader multi-platform support including Windows and BSD variants. The fork aimed to evolve the suite into a more comprehensive, community-driven toolkit for wireless security assessment while preserving the core WEP cracking capabilities. Early development of Aircrack-ng was led by d'Otreppe, with significant contributions from David Adams and a growing community of developers collaborating via hosting. This open-source effort transitioned under the GNU General Public License (GPL) version 2, facilitating ongoing enhancements and distribution across hacking distributions like . In 2018, the project migrated to , further enabling collaborative governance and integration of optimizations like the KoreK and PTW attacks for faster key recovery.

Version History

Aircrack-ng's development began with its initial release as version 0.9 on May 13, 2007, following the project's from the original Aircrack in February 2006. This version introduced a modular structure for the suite of tools, along with basic support for WPA cracking and enhancements such as the PTW attack for WEP key recovery, injection testing in aireplay-ng, and decryption of IEEE 802.11e headers via airdecap-ng. Early versions like 0.9 also supported foundational attacks such as the Fluhrer-Mantin-Shamir (FMS) method for exploiting WEP vulnerabilities. Subsequent milestone releases built on this foundation with performance improvements and expanded compatibility. Version 1.0, released on September 7, 2009, improved airserv-ng compatibility across 32/64-bit OSes, added support for PPI (Per-Packet Information) capture formats, and fixed issues in WPA handshake detection and cross-platform compatibility, including . Version 1.1, released on April 24, 2010, introduced airdrop-ng for remote packet dropping and addressed buffer overflows in several tools, enhancing overall stability for WPA cracking workflows. Later versions focused on speed optimizations and modern hardware support. Version 1.2, released on April 15, 2018, significantly improved WPA cracking speeds (up to 3x faster in some cases) through better CPU utilization, added support for 802.11n/ac in airodump-ng, and included an autotools-based build system for easier compilation across platforms. Version 1.4, released on September 29, 2018, enhanced packet capture handling with AVL trees for efficient processing of large files, introduced PMKID clientless cracking, and integrated hwloc for optimized performance on multi-core systems, alongside initial WPA3 compatibility. The latest stable release, version 1.7 on May 10, 2022, incorporated over 400 commits addressing bug fixes, , and optimizations for modern hardware, including better error handling in airmon-ng for and newer chipsets, Python 3 support for scripting tools, and improved static analysis for security. As of November 2025, no major releases have followed 1.7, with development emphasizing ongoing maintenance through minor patches on for compatibility with updated systems, such as the Fedora 1.7-9 rebuild in January 2025. Development practices shifted in the 2010s, notably with the full migration from SourceForge to GitHub on March 11, 2018, to facilitate better collaboration, issue tracking, and continuous integration. The project has since prioritized security auditing features over introducing new exploits, aligning with its role in Wi-Fi penetration testing.

Wi-Fi Security Protocols and Vulnerabilities

WEP

Wired Equivalent Privacy (WEP) was standardized in 1997 as part of the original IEEE 802.11 standard to provide basic confidentiality for wireless local area networks, equivalent to that of a wired network. It employs the RC4 stream cipher for encryption, using a shared secret key of either 40 bits or 104 bits, concatenated with a 24-bit initialization vector (IV) to generate a per-packet keystream. The protocol appends a CRC-32 checksum as an integrity check vector (ICV) to each packet before encryption, aiming to protect against eavesdropping and unauthorized access. However, WEP's design was rushed and lacked robust cryptographic review, leading to fundamental flaws that rendered it insecure from the outset. Key weaknesses in WEP include the use of a short, static IV that is sent in , enabling rapid exhaustion of the 24-bit IV space (approximately 16 million possible values) and key reuse across packets, which exposes the keystream to XOR-based attacks. The CRC-32 integrity mechanism is a non-cryptographic vulnerable to bit-flipping attacks, where an adversary can alter bits and recompute the ICV without knowledge of the key, allowing packet modification. Additionally, WEP provides no replay protection, permitting attackers to resend captured packets indefinitely without detection. These issues, combined with RC4's key scheduling vulnerabilities, facilitate both passive and active exploitation. Major attacks exploiting these flaws began with the Fluhrer-Mantin-Shamir (FMS) attack in 2001, which recovers the key by collecting weak IVs that bias RC4's initial keystream output, typically requiring around 5 million IVs for a 40-bit key. In 2004, KoreK's statistical attacks improved on FMS by leveraging additional IV correlations, reducing the required IVs to approximately 500,000 for reliable key recovery. The same year, KoreK's Chopchop attack enabled byte-by-byte decryption of a single packet by iteratively truncating it, guessing the last byte, and verifying via ICV, exploiting RC4's malleability and the weak integrity check—one byte per successfully injected packet. By 2007, the Pyshkin-Tews-Weinmann (PTW) attack further optimized key recovery, succeeding with about 85,000 IVs at 95% probability, independent of weak IV reliance. The declared WEP insecure in 2004 due to these vulnerabilities, recommending immediate transition to WPA. By 2006, with WPA2 certification becoming mandatory, WEP was fully deprecated in standards, prohibiting its use in new certified devices. Despite this, legacy hardware may still support WEP, perpetuating risks. Aircrack-ng tools target WEP by capturing IVs and applying these statistical methods or dictionary attacks on weak keys, demonstrating the protocol's practical breakability in educational and testing contexts.

WPA and WPA2

Wi-Fi Protected Access (WPA) was introduced in 2003 by the as an interim enhancement to address the severe vulnerabilities in the (WEP) protocol. It employs the (TKIP), which builds on the used in WEP but incorporates per-packet key mixing and a 48-bit to prevent key reuse and improve resistance to certain attacks. WPA supports (PSK) mode, allowing straightforward deployment in home and small office environments without requiring enterprise authentication infrastructure. WPA2, formally ratified in 2004 as part of the IEEE 802.11i standard, became mandatory for all certified devices starting March 13, 2006. It introduces the Counter Mode with Cipher Block Chaining Protocol (CCMP), which uses the (AES) in for robust , , and , effectively replacing TKIP as the preferred method while maintaining with legacy devices. This shift to AES-CCMP provided significantly stronger cryptographic protections compared to TKIP's RC4-based approach. Despite these advancements, both protocols retain exploitable weaknesses relevant to tools like Aircrack-ng. In WPA with TKIP, the Beck-Tews attack, disclosed in 2008, exploits weaknesses in the protocol's Michael message integrity check and key derivation to decrypt broadcast packets such as ARP requests and inject forged packets, potentially enabling further network reconnaissance or disruption without full key recovery. For WPA2, the Key Reinstallation Attack (KRACK), revealed in 2017, targets flaws in the 4-way handshake process by forcing nonce reuse through manipulated packet retransmissions, allowing attackers to replay encrypted frames, decrypt select traffic like content, and potentially hijack sessions. Both protocols in PSK mode are also susceptible to offline or brute-force attacks on weak passphrases, which require capturing the authentication handshake to test candidate keys computationally. WPA3, announced by the in June 2018, advances security further by mandating (SAE) for PSK authentication, which resists offline attacks through a dragonfly key exchange that protects even weak passwords. However, Aircrack-ng's capabilities remain centered on exploiting WPA and WPA2-PSK vulnerabilities via handshake capture and cracking, with no native support for WPA3's enhanced mechanisms.

Timeline of Cracking Attacks

The timeline of cracking attacks on Wi-Fi security protocols highlights key vulnerabilities exploited by researchers, with Aircrack-ng playing a pivotal role in implementing and refining these techniques for auditing purposes. In 2001, the Fluhrer, Mantin, and Shamir (FMS) attack was published, revealing weaknesses in the key scheduling algorithm used in WEP, allowing key recovery through the collection of weak initialization vectors (IVs) from broadcast packets. This statistical attack laid the foundation for practical WEP cracking tools, and Aircrack-ng incorporated an of FMS from its early versions to enable passive key recovery with sufficient captured traffic. By 2004, refinements to WEP cracking emerged alongside the introduction of WPA. The KoreK attacks, developed by an anonymous researcher known as KoreK, optimized the FMS method by identifying additional weak IV classes, significantly reducing the number of packets needed for key recovery to around 500,000–1,000,000. Concurrently, the Chopchop attack, detailed on security forums, enabled interactive decryption of WEP packets byte-by-byte without the full key, exploiting the protocol's CRC-32 checksum vulnerability. That same year, the Wi-Fi Alliance introduced WPA with TKIP to mitigate WEP flaws, but early analyses revealed TKIP's Michael MIC weaknesses, paving the way for future exploits. Aircrack-ng integrated both KoreK optimizations and Chopchop support in subsequent releases, enhancing its efficiency for WEP audits. In 2007, the PTW attack further accelerated WEP key recovery, requiring as few as 40,000 packets for a 104-bit key with 50% success probability, by improving statistical biases in keystreams and incorporating ARP replay techniques. Developed by Erik Tews, Ralf-Philipp Weinmann, and Andrey Pyshkin, PTW addressed limitations in prior methods under noisy conditions. Aircrack-ng version 1.0, released that year, adopted PTW as its default WEP cracking algorithm, marking a major update in performance. The first practical attacks on WPA via TKIP vulnerabilities appeared in , extending WEP techniques like Chopchop to decrypt packets and forge traffic, though limited by TKIP countermeasures such as extended IVs and MIC extensions. Researchers Erik Tews and demonstrated these in a whitepaper, enabling partial but not full key recovery without additional flaws. Aircrack-ng updated its suite to support TKIP-specific replay and fragmentation attacks, aligning with these discoveries for testing WPA deployments. A significant WPA2 vulnerability emerged in 2017 with the disclosure of the Key Reinstallation Attack (), which exploited flaws in the 4-way handshake to reinstall encryption keys, allowing nonce reuse and decryption of traffic or injection of malicious packets. Discovered by Mathy Vanhoef, affected nearly all WPA2 devices but did not compromise the pairwise master key itself, prompting widespread patches. While Aircrack-ng did not directly implement due to its active nature requiring client-side manipulation, the suite's tools like aireplay-ng facilitated demonstrations and defenses against such reinstallation risks. Into the 2020s, cracking efforts shifted toward offline dictionary and brute-force attacks on WPA2-PSK, leveraging captured handshakes without new protocol-level exploits by 2025, as WPA3 adoption grew. Optimizations focused on GPU acceleration, with tools processing billions of password guesses per second using frameworks like , emphasizing the importance of strong passphrases over inherent protocol weaknesses. Aircrack-ng continued evolving with support for WPA/WPA2 handshakes and integrations for GPU offloading via external libraries, maintaining its relevance for assessments amid these computational advances.

Core Tools

aircrack-ng

Aircrack-ng is the flagship tool in the Aircrack-ng suite, designed primarily for recovering WEP encryption keys through statistical attacks such as FMS, KoreK, and PTW, as well as cracking WPA/WPA2 (PSK) passphrases using or brute-force methods on captured handshakes. It processes offline packet captures to exploit weaknesses in the stream cipher used by WEP and the key derivation in WPA/WPA2-PSK, enabling key extraction without real-time network interaction. The tool requires input in the form of .cap files containing sufficient captured packets, typically generated by airodump-ng; for WEP cracking, this includes a minimum number of initialization vectors (IVs) paired with encrypted data packets, while WPA/WPA2 cracking needs at least the four-way (such as EAPOL messages 2/3 or 3/4). The FMS algorithm identifies weak IVs that allow setting up a over GF(2) to solve for the key bytes, exploiting predictable states from specific IV sequences. KoreK builds on this by applying statistical correlations derived from empirical analysis of biases, resembling a approach to refine key candidates and accelerate recovery. The PTW method enhances efficiency by leveraging bitwise correlations in keystream bytes conditioned on known like ARP packets, reducing the required packet count for high success probability. For WPA/WPA2-PSK, aircrack-ng tests candidate passphrases by computing the pairwise master key (PMK) via PBKDF2-HMAC-SHA1 iterations using the network SSID and passphrase, deriving the pairwise transient key (PTK), and verifying the message integrity code (MIC) against the captured . Upon successful cracking, aircrack-ng outputs the recovered WEP key in format (e.g., for 40/104-bit keys) or the WPA/WPA2 in ASCII, along with derived keying material if applicable. For example, the PTW method achieves approximately 50% success probability with around 40,000 IVs for 104-bit keys, requiring about 85,000 IVs for 95% success; fewer IVs suffice for 64-bit keys. WPA/WPA2 success depends heavily on the strength and quality, with no guaranteed recovery for complex keys. Limitations include high computational demands, particularly for exhaustive WPA/WPA2 searches on modern hardware, and lack of support for WPA3, which employs (SAE) instead of PSK handshakes.

aireplay-ng

Aireplay-ng is a command-line tool within the Aircrack-ng suite designed for injecting and replaying wireless frames to facilitate the assessment of . It primarily generates artificial traffic to accelerate the capture of data needed for cracking encryption keys, such as WEP initialization vectors (IVs) or WPA handshakes, by exploiting vulnerabilities in 802.11 protocols. The tool operates in on compatible wireless interfaces, allowing it to forge and transmit packets without association to the target network. The core functions of aireplay-ng include for forging frames and replaying captured packets to amplify network traffic. It supports deauthentication and disassociation attacks, which send forged management frames to disconnect clients from an access point, forcing reconnections that reveal WPA/WPA2 handshakes for offline cracking. For WEP networks, aireplay-ng enables ARP replay attacks by capturing and reinjecting ARP request packets, which generates a high volume of encrypted traffic containing unique IVs essential for key recovery. Additionally, it performs chopchop attacks, which decrypt WEP packets byte-by-byte through repeated injection and analysis, though this method is slower and requires no prior knowledge of IP addresses. Usage of aireplay-ng requires a wireless interface in , typically enabled via airmon-ng, to transmit frames effectively. Common command options include -0 or --deauth for deauthentication floods (e.g., aireplay-ng -0 5 -a <BSSID> -c <client MAC> mon0 to send five deauth packets), and -3 or --arpreplay for ARP-based traffic amplification (e.g., aireplay-ng -3 -b <BSSID> -h <client MAC> mon0 using a captured ARP packet). Other parameters control injection rate with -x (packets per second) and target specifics like BSSID (-b) or client MAC (-c), ensuring precise attacks while minimizing detection. Interactive packet selection is available in -2 mode for manual replay, and -9 tests injection capability before full attacks. Aireplay-ng significantly accelerates WEP cracking by increasing the rate of IV collection through active injection, reducing the time from hours of passive sniffing to minutes of targeted replay. For WPA/WPA2, its deauthentication capability is essential to capture the four-way required for or brute-force attacks in aircrack-ng. Effectiveness depends on the wireless card's injection rate, which can be optimized by setting higher transmission rates (e.g., via iwconfig). Hardware compatibility is crucial, as aireplay-ng requires cards supporting raw packet injection and . Atheros chipsets, such as the AR9271 found in USB adapters like the ALFA AWUS036NHA, provide reliable performance with kernel/mac80211 drivers, enabling high injection rates up to 500 packets per second. Other supported examples include RT3070 and certain Qualcomm Atheros variants, though success varies by driver version and firmware.

airodump-ng

Airodump-ng is a packet sniffer and analyzer within the Aircrack-ng suite, designed for passive monitoring and capture of traffic to support network . It operates by capturing raw 802.11 frames, including beacons, packets, and management frames such as probe responses and association requests, while monitoring 2.4 GHz channels by default with automatic hopping to scan multiple frequencies. The tool displays real-time information on access points (APs) and clients, including ESSIDs, BSSIDs, signal strength (PWR), receive quality (RXQ), number of beacons and packets, channel, and connected clients' MAC addresses, power levels, probe requests, and rates. It also detects types, such as WEP, WPA, WPA2, or WPA3, along with ciphers (e.g., TKIP, CCMP) and methods (e.g., PSK). The captured data is saved in multiple formats for further analysis, with pcap-compatible .cap files providing full packet captures suitable for tools like . Other outputs include .csv files detailing AP and client information, .kismet.csv for compatibility with Kismet wireless intrusion detection systems, and .ivs files exporting only initialization vectors (IVs) for WEP analysis. Additional formats encompass .gps for location data and .kismet.netxml for exports. These files enable offline examination of network structures and traffic patterns. Key command-line options allow customization of airodump-ng's behavior, such as --channel (or -c) to fix monitoring on specific channels (e.g., -c 1,6,11) or enable hopping intervals via -f <msecs>, --bssid to filter captures to a single AP's (e.g., --bssid 00:14:6C:7A:41:20), and --write (or -w) to specify a prefix for output files (e.g., -w capture). The --ivs option streamlines WEP IV collection by saving only relevant , reducing file sizes for targeted . Enhancements include GPS integration through --gpsd, which logs coordinates from a GPS receiver into .gps files for mapping network locations, and automatic detection of WPA handshakes in real-time console output (e.g., alerting "WPA handshake: "). Common use cases involve identifying potential targets by listing nearby networks and clients, capturing sufficient IVs for WEP or handshakes for WPA/WPA2 analysis, and providing live assessments via interactive console features like sorting columns with [s]. Captured .cap or .ivs files from airodump-ng can subsequently be processed by aircrack-ng for key cracking.

Attack and Automation Tools

airbase-ng

airbase-ng is a versatile tool within the Aircrack-ng suite designed to create rogue access points (APs) that simulate legitimate networks, thereby luring client devices to associate with them for the purpose of conducting targeted attacks on those clients rather than the AP itself. By emulating various network configurations, including open , WEP-encrypted networks, and WPA/WPA2 setups, airbase-ng enables the generation of deceptive beacons and probe responses to attract clients, even those configured for hidden SSIDs via the -X option. This client-focused approach facilitates the capture of authentication materials and traffic without directly targeting an existing AP, distinguishing it from tools that inject packets into live networks. The tool supports several specific attacks that exploit client vulnerabilities to recover keys or data. For WEP networks, airbase-ng implements the Caffe Latte attack using the -L option, which leverages gratuitous ARP requests from associating clients to generate sufficient initialization vectors (IVs) for key recovery, even without access to the original AP. Similarly, the Hirte attack, enabled by the -N option, extends this by amplifying weak IVs through fragmentation of any captured ARP or IP packets from the client, allowing key extraction in scenarios where the AP is unavailable. For WPA/WPA2, airbase-ng can force client associations to capture the four-way by configuring appropriate tags (e.g., -z 2 for WPA-TKIP or -Z 4 for WPA2-CCMP), generating the necessary traffic to prompt re-authentication. Key command-line options allow precise control over the rogue AP's behavior, such as -e <ESSID> to set the network name, -c <channel> to specify the operating channel, -w <WEP key> for in WEP mode, and -a <BSSID> to define the fake AP's . Additional parameters like -s enforce shared for WEP, while -P enables responses to all probe requests to increase client attraction, and -x <nbpps> sets the packet transmission rate (default 100 packets per second) to simulate active traffic. Usage typically involves running airbase-ng <options> <monitor interface>, such as airbase-ng -c 9 -e "teddy" -W 1 mon0, which creates a WEP-enabled rogue AP on channel 9 named "teddy". Output from airbase-ng includes real-time console displays of client associations, probe requests, and encryption details, alongside the creation of a tap interface (e.g., at0) for handling decrypted or routed packets. Captured frames, including handshakes and attack-generated traffic, can be saved to .cap files using the -F <prefix> option for subsequent analysis or cracking with other Aircrack-ng tools. Advanced features extend airbase-ng's utility for complex scenarios, including support for multiple APs via --bssids <file> to load a list of BSSIDs for simultaneous emulation, and beacon flooding for denial-of-service (DoS) effects by overwhelming clients with fake network advertisements using options like -P combined with -C <seconds> to and beacon multiple ESSIDs. It also supports ad-hoc mode (-A) for simulations and external packet processing (-Y) to integrate with custom scripts or tools for enhanced traffic manipulation.

airmon-ng

airmon-ng is a command-line utility within the Aircrack-ng suite designed to manage network interfaces, primarily by enabling and disabling to facilitate auditing. It also handles the detection of interfering processes and provides diagnostic information about supported s and drivers. Without arguments, running airmon-ng displays the current status of interfaces, including their mode, details, and driver information. The core function of airmon-ng is to start or stop on a specified interface, which allows the interface to passively capture all traffic without associating with a network. For instance, executing airmon-ng start wlan0 creates a new virtual monitor interface named wlan0mon (or mon0 in some configurations), enabling raw 802.11 frame capture. It automatically checks for and warns about processes that may interfere with , such as or dhclient, which can disrupt or capture. To mitigate these, airmon-ng can kill such processes upon request. Additionally, it detects common chipsets, including Atheros (e.g., AR9271 with ath9k driver) and (e.g., RT3070 with rt2800usb driver), ensuring compatibility before mode switching. Key commands include airmon-ng start <interface> [channel] to initiate monitor mode on the specified channel, airmon-ng stop <interface> to revert to managed mode and remove the monitor interface, and airmon-ng restart <interface> for a full cycle of stopping and restarting. The airmon-ng check command lists potentially problematic processes like , while airmon-ng check kill terminates them automatically to prevent conflicts. For debugging, options such as --verbose or --debug provide detailed output on interface operations and errors. airmon-ng requires root privileges to modify kernel-level interface settings and relies on compatible wireless drivers that support monitor mode, such as ath9k for Atheros chipsets or rtl8187 for devices. Without these, attempts to enable will fail, often indicated by error messages in the output. In troubleshooting scenarios, airmon-ng addresses common issues by automatically killing interfering daemons like during mode activation. It also supports the creation and deletion of virtual interfaces; lingering monitor interfaces can be removed manually using iw dev <interface> del if needed. For driver-related problems, reloading modules (e.g., rmmod ath9k; [modprobe](/page/Modprobe) ath9k) may resolve detection failures. As a foundational tool in the Aircrack-ng suite, airmon-ng serves as a prerequisite for all packet capture and injection operations, preparing interfaces for use by subsequent tools in assessments.

besside-ng

Besside-ng is an automated tool within the Aircrack-ng suite designed to crack WEP-encrypted networks and capture WPA/WPA2 handshakes without requiring manual intervention from the user. Developed by Andrea Bittau, it builds on concepts from earlier tools like Wesside-ng but extends support to WPA encryption, enabling it to target both legacy and modern security protocols in range. It is an experimental tool that requires enabling experimental features during compilation (e.g., using --with-experimental flag). It requires a compatible interface capable of . The workflow of besside-ng begins with scanning for nearby access points (APs) using the specified wireless interface in . Upon detecting a WEP network, it automatically associates with the AP, injects packets to generate initialization vectors (IVs), and accumulates sufficient data for on-the-fly cracking using integrated aircrack-ng algorithms. For WPA/WPA2 networks, it monitors for clients, performs deauthentication attacks to force exchanges, and logs the resulting 4-way handshakes. The tool handles association, injection, and capture seamlessly, directing output to log files and packet captures while continuing to scan other networks in parallel. This automation reduces the need for separate commands, making it suitable for penetration testing in dynamic environments. It internally leverages aireplay-ng for and deauthentication tasks. Besside-ng operates in two primary modes: full automatic mode, which targets both WEP and WPA networks by default, and WPA-only mode activated via the -W option to focus exclusively on capture without attempting WEP cracks. In WPA mode, it can optionally upload captured handshakes to a remote server like wpa.darkircop.org for dictionary-based cracking and feasibility analysis, providing statistics on strength. These modes allow users to tailor the tool for specific assessments, such as rapid WEP exploitation or offline WPA analysis preparation. Key command-line options include:
  • -b <target mac>: Specifies a target BSSID to focus attacks on a single AP.
  • -s <WPA server>: Defines the upload server for WPA handshake processing (default: wpa.darkircop.org).
  • -c <chan>: Locks scanning to a specific channel to optimize for known networks.
  • -p <pps>: Sets the packets-per-second rate for injection, balancing speed and detectability.
  • -W: Enables WPA-only mode.
  • -v: Activates verbose logging for detailed output.
  • -h: Displays the help screen.
Usage follows the syntax besside-ng [options] <interface>, where the interface must be pre-configured in via airmon-ng. Output from besside-ng includes a primary log file named besside.log, which records details such as SSID, recovered WEP keys in and ASCII formats, BSSID, channel, and type for each cracked network. For WPA captures, it generates .cap files containing handshakes, suitable for later processing with tools like aircrack-ng or external dictionaries. Successful WEP cracks can occur in minutes under good signal conditions and sufficient client traffic, often yielding keys after capturing 10,000–50,000 IVs depending on the network's activity. WPA outputs are stored for offline use, with upload results providing estimated cracking times based on passphrase complexity. Limitations of besside-ng include its dependence on hardware supporting reliable , such as certain Atheros or chipsets, which may fail on incompatible devices leading to incomplete captures. For WPA2 networks with strong passphrases (e.g., 12+ characters mixing cases and symbols), capture succeeds but cracking remains computationally intensive and often requires substantial resources or GPU acceleration beyond the tool's scope. It performs less effectively in low-traffic environments where client associations are sparse, and the optional upload service may introduce concerns or downtime risks.

Supporting Utilities

airolib-ng

Airolib-ng is a utility in the Aircrack-ng suite that facilitates the precomputation and management of Pairwise Master Keys (PMKs) for accelerating WPA/WPA2-PSK dictionary-based attacks on captured handshakes. It operates by storing lists of network identifiers (ESSIDs) and potential passphrases in a database, then deriving PMKs for each ESSID-password pair to enable rapid verification during cracking without recomputing expensive hashes on demand. This tool addresses the computational bottleneck in WPA/WPA2 cracking, where generating PMKs traditionally slows down brute-force or dictionary attempts. The core process begins with importing ESSID and password lists into the database using the import command, such as airolib-ng <database> import passwd <wordlist_file> for passphrases or import essid <essid_file> for network names. PMKs are then computed via the batch subcommand, which applies the PBKDF2-HMAC-SHA1 with 4096 iterations per pair—a standard derived from the WPA2-PSK protocol—to produce 256-bit keys. Users can verify the integrity of these precomputed PMKs using the test command, optionally with the all flag to delete invalid entries and optimize the database. Additional operations include cleaning the database with clean to reduce size and check consistency, exporting to formats like coWPAtty via export cowpatty, or querying statistics with info. For storage, airolib-ng employs an SQLite3 database (requiring version 3.3.17 or later), which efficiently handles large collections of ESSID-password combinations and their associated PMKs with minimal overhead across platforms. The ESSID serves as the salt in the derivation, allowing support for custom or multiple network-specific tables within a single database. This structure enables distributed precomputation, where PMKs can be generated on multiple systems and merged. By precomputing PMKs, airolib-ng significantly reduces cracking times; for instance, it enables aircrack-ng to test over 50,000 passwords per second against a captured , transforming what might take hours into seconds for common passphrases. It integrates seamlessly with aircrack-ng by specifying the database path with the -r option, such as aircrack-ng -r <database> <capture_file>, allowing direct use of the rainbow tables for efficient dictionary attacks on WPA/WPA2 handshakes.

packetforge-ng

Packetforge-ng is a utility within the Aircrack-ng suite designed to forge custom 802.11 packets, particularly for use in penetration testing and assessments. It enables the creation of encrypted packets from templates or modifications to existing captures, ensuring they mimic legitimate traffic to facilitate injection attacks. By leveraging pseudorandom generation algorithms (PRGA) derived from prior captures, such as those obtained via fragmentation or chop-chop attacks, packetforge-ng produces packets that appear authentic to target networks, including proper 802.11 headers, MAC addresses, and flags. The tool's core capabilities include generating specific packet types: ARP requests (mode -0 or --arp), UDP packets (mode -1 or --udp), ICMP packets (mode -2 or --icmp), null packets (mode -3 or --null), and custom packets (mode -9 or --custom) based on user-defined payloads or modified input files. For custom packets, it can alter existing captures by applying PRGA keystreams to encrypt or re-encrypt payloads while preserving or adjusting layer 2 and 3 details. It supports fragmentation by utilizing PRGA files from aireplay-ng's fragmentation mode, allowing the creation of fragmented packets that can solicit responses from access points. This precision in handling frame control words, FromDS/ToDS bits, and WEP options ensures the forged packets integrate seamlessly with 802.11 protocol requirements. Usage of packetforge-ng follows the syntax packetforge-ng <mode> <options>, where modes specify the packet type and options configure details like MAC addresses (-a for BSSID, -h for source MAC, -c for destination MAC), IP addresses (-k for destination IP:port, -l for source IP:port), TTL (-t), and file inputs/outputs (-r for reading from a raw or pcap file, -y for PRGA file, -w for writing to a pcap output file). The -e option disables WEP encryption if needed, while -p sets the frame control word in hexadecimal for fine-tuned header manipulation. For example, to forge an ARP request packet, one might use: packetforge-ng -0 -a 00:14:6C:7E:40:80 -h 00:0F:B5:AB:CB:9D -k 192.168.1.100 -l 192.168.1.1 -y fragment-0124-161129.xor -w arp-request.cap, which sets the AP and source MACs, destination and source IPs, applies the PRGA keystream, and outputs a pcap file. Similarly, for a custom packet from an input capture: packetforge-ng -9 -r input.cap -y keystream.xor -w output.cap. These commands allow users to build packets with tailored payloads, such as short null packets for deauthentication testing (packetforge-ng -3 -s 42 -a BSSID -h SMAC -w short-packet.cap -y fragment.xor). In attack applications, packetforge-ng is primarily used to craft requests that provoke responses from target devices, thereby generating initialization vectors (IVs) for WEP key cracking or for further analysis. For instance, forged ARP requests can elicit ARP replies from clients or access points, accelerating IV collection in WEP networks by injecting the packets via aireplay-ng. It supports scenarios requiring authenticated-looking , such as replaying modified captures to test network defenses or simulate client associations. The resulting forged files are directly compatible with injection tools like aireplay-ng for transmission over monitored interfaces. Output files can be inspected with utilities like to verify structure before deployment. Note that packetforge-ng is optimized for WEP-encrypted environments and requires a valid PRGA file for ; it avoids unnecessary bit manipulations like FromDS/ToDS toggles unless specified.

wpaclean

wpaclean is a utility within the Aircrack-ng suite designed to filter and clean wireless packet capture files, specifically targeting WPA/WPA2 handshake data for subsequent analysis and cracking processes. It processes input .cap files by extracting only the essential packets required for WPA key recovery, namely the 4-way EAPOL packets and associated frames from the access point, while discarding irrelevant traffic such as data frames, management frames unrelated to , duplicates, and general noise. This selective extraction ensures that the output file contains streamlined data, making it suitable for input into cracking tools like aircrack-ng. The process begins with providing one or more input capture files obtained from tools like airodump-ng, along with a specified output filename, using the basic syntax: wpaclean <output.cap> <input1.cap> [input2.cap ...]. wpaclean automatically detects and isolates complete or partial 4-way handshakes by analyzing the EAPOL sequence between the client and access point, as well as relevant beacons that provide network parameters like SSID and settings. It handles multiple input files by merging and filtering them into a single, cleaned output file, which significantly reduces the overall file size—often by a substantial margin, as extraneous packets are removed—thereby optimizing storage and for resource-constrained environments. For instance, in scenarios involving large captures from prolonged monitoring sessions, this filtering can eliminate gigabytes of irrelevant , focusing solely on authentication-related elements. By preparing cleaned capture files, wpaclean facilitates faster execution of dictionary or brute-force attacks on WPA2 pre-shared keys in aircrack-ng, as the reduced minimizes overhead and potential errors from noisy inputs. This preprocessing step is particularly valuable in penetration testing workflows, where post-capture refinement ensures that only viable proceeds to cracking, allowing users to verify the presence of necessary EAPOL messages (messages 1 through 4) without sifting through voluminous raw traffic. In practice, after capturing potential handshakes during a deauthentication attack, running wpaclean on the resulting files prepares them directly for key recovery attempts, enhancing the overall efficacy of security assessments.

References

Add your contribution
Related Hubs
User Avatar
No comments yet.