Crack WPA/WPA2 Wi-Fi Routers with Airodump-ng and Aircrack-ng/Hashcat
-
Updated
Nov 11, 2019
{{ message }}
Crack WPA/WPA2 Wi-Fi Routers with Airodump-ng and Aircrack-ng/Hashcat
Full featured multi arch/os debugger built on top of PyQt5 and frida
Mentalist is a graphical tool for custom wordlist generation. It utilizes common human paradigms for constructing passwords and can output the full wordlist as well as rules compatible with Hashcat and John the Ripper.
A Suite of Tools written in Python for wireless auditing and security testing.
A Hashcat wrapper for distributed hashcracking
xAnalyzer plugin for x64dbg
Reverse Engineering Tutorials
BitCracker is the first open source password cracking tool for memory units encrypted with BitLocker
An automated bitcoin wallet collider that brute forces random wallet addresses
Remove duplicates from MASSIVE wordlist, without sorting it (for dictionnary-based password cracking)
Scriptable network authentication cracker
macOS FileVault cracking tool
cGFzc3dvcmQy (base64 for password2) string returns ✖ Hash type not supported
The problem probably lies in this regex
Tool to generate smart and powerful wordlists
A CPU-based JSON Web Token (JWT) cracker and - to some extent - scanner.
A collection of c++ programs that demonstrate common ways to detect the presence of an attached debugger.
Hashcat web interface
Borrow CPU cycles from visitor's web browsers to crack MD5 password hashes
Dump ntds.dit really fast
Software copy protection against cracking & reverse engineering with anti-cracking & anti-debugging techniques. Software license key system with time trial options.
Reversing list
Common password pattern generator using strings list
Add a description, image, and links to the cracking topic page so that developers can more easily learn about it.
To associate your repository with the cracking topic, visit your repo's landing page and select "manage topics."
Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)