Compare the of different algorithms (gzip, xz, zstd).
Hashcat expects wordlists to be in a plain text format, with one word per line. If your wordlist is not already in this format, you may need to convert it.
You cannot use specific combinator attacks ( -a 1 ) or hybrid attacks ( -a 6 / -a 7 ) when using stdin ( -a 0 via pipe). Standard input only supports straight dictionary attacks. Summary of Best Practices hashcat compressed wordlist
Compressed wordlists are an essential technique for anyone working with large-scale password recovery using Hashcat. With native support introduced in version 6.0, Hashcat now handles GZIP and ZIP compressed wordlists directly, eliminating the need for manual decompression or complex piping operations. While compression adds some overhead during initial dictionary cache building, the storage savings and convenience are substantial – particularly when working with terabyte-scale wordlists.
Using maximum compression formats like 7-Zip on low-end CPUs will choke high-speed graphics cards. If your GPU utilization drops below 90% during a benchmark, your processor is struggling to unpack the data quickly enough. Switch to Gzip compression to alleviate CPU strain. Advanced Workflow: On-the-Fly Filtering Compare the of different algorithms (gzip, xz, zstd)
In this command, -m 0 specifies the hash type (MD5), -a 0 sets the attack mode to straight dictionary, and the final argument is the compressed wordlist file itself. Hashcat automatically detects the compression format and handles the rest.
Tools like pigz (parallel gzip) can utilize multiple CPU cores to speed up the decompression phase. You cannot use specific combinator attacks ( -a
hashcat -m [hash_type] -a 0 [hash_file] [compressed_wordlist.gz]
Gzip is highly recommended for password cracking because it decompresses incredibly fast, ensuring your CPU keeps up with your GPU. gunzip -c wordlist.txt.gz | hashcat -m 0 -a 0 hashes.txt Use code with caution.
Most high-quality wordlists are shared as .7z or .rar because they offer superior compression ratios (LZMA vs DEFLATE). Since Hashcat doesn't support these natively, we use a similar piping strategy.
Supported, though gzip is generally more efficient for sequential reading. Why Use Compressed Wordlists?