Yesterday, 06:14 AM
Hashcat 6.2.6 in up to date The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) rolling release.
a simple test command like:
hashcat -m 0 -a 0 -o <output_file> <md5_hash_file> <word_list> -O
reports that no hashes have been cracked even if they are simple password hashes (of the correct, in this case MD5, hash type) and are definitely in (or some of them are in) the <word_list> given. (I'm using rockyou.txt).
Here's my <md5_hash_file> :
5965bb7474aadec148948f466568c612
bf6efae04d1872ebb42da1601e53e20d
8bd9b031dd34e106134612f7fb400df1
6fceec81e47c744c4552f26767853881
These are the MD5 hashes for these passwords:
Davey
MaryJane
Password234
squirrel87654^&%$£"ujhtdcCDSA
So the first 3 should be cracked and the 4th probably not but when I run:
hashcat -m 0 -a 0 -o cracked.txt hashesonly.txt rockyou.txt -O
I get the result:
Session..........: hashcat
Status...........: Exhausted
Hash.Mode........: 0 (MD5)
Hash.Target......: hashesonly.txt
Time.Started.....: Thu Sep 11 05:12:35 2025 (4 secs)
Time.Estimated...: Thu Sep 11 05:12:39 2025 (0 secs)
Kernel.Feature...: Optimized Kernel
Guess.Base.......: File (rockyou.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 3677.3 kH/s (0.59ms) @ Accel:1024 Loops:1 Thr:1 Vec:8
Recovered........: 0/4 (0.00%) Digests (total), 0/4 (0.00%) Digests (new)
Progress.........: 14344385/14344385 (100.00%)
Rejected.........: 3094/14344385 (0.02%)
Restore.Point....: 14344385/14344385 (100.00%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: $HEX[21217265626f756e642121] -> $HEX[042a0337c2a156616d6f732103]
Hardware.Mon.#1..: Temp: 70c Util: 66%
The <output_file> is empty:
wc cracked.txt
0 0 0 cracked.txt
The potfile is also empty ( ~/.local/share/hashcat/hashcat.potfile )
Same results (no hashes cracked) if I don't specify any output file.
So have I broken my hashcat? Am I making some basic mistake that I just can't see? (I pretty new to hashcat but have had results from basic commands like the above before.)
That line:
Candidates.#1....: $HEX[21217265626f756e642121] -> $HEX[042a0337c2a156616d6f732103]
should be the cracked passwords, right?, but it's in hex . . ?
Perhaps I've set something inadvertently? I found no .config files anywhere or are they called something else?
Maybe I'd be better off just upgrading to version 7.1? I already uninstalled and re-installed hashcat 6.2.6. . . . ?
Any thoughts or advice gratefully accepted, thanks.
a simple test command like:
hashcat -m 0 -a 0 -o <output_file> <md5_hash_file> <word_list> -O
reports that no hashes have been cracked even if they are simple password hashes (of the correct, in this case MD5, hash type) and are definitely in (or some of them are in) the <word_list> given. (I'm using rockyou.txt).
Here's my <md5_hash_file> :
5965bb7474aadec148948f466568c612
bf6efae04d1872ebb42da1601e53e20d
8bd9b031dd34e106134612f7fb400df1
6fceec81e47c744c4552f26767853881
These are the MD5 hashes for these passwords:
Davey
MaryJane
Password234
squirrel87654^&%$£"ujhtdcCDSA
So the first 3 should be cracked and the 4th probably not but when I run:
hashcat -m 0 -a 0 -o cracked.txt hashesonly.txt rockyou.txt -O
I get the result:
Session..........: hashcat
Status...........: Exhausted
Hash.Mode........: 0 (MD5)
Hash.Target......: hashesonly.txt
Time.Started.....: Thu Sep 11 05:12:35 2025 (4 secs)
Time.Estimated...: Thu Sep 11 05:12:39 2025 (0 secs)
Kernel.Feature...: Optimized Kernel
Guess.Base.......: File (rockyou.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 3677.3 kH/s (0.59ms) @ Accel:1024 Loops:1 Thr:1 Vec:8
Recovered........: 0/4 (0.00%) Digests (total), 0/4 (0.00%) Digests (new)
Progress.........: 14344385/14344385 (100.00%)
Rejected.........: 3094/14344385 (0.02%)
Restore.Point....: 14344385/14344385 (100.00%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:0-1
Candidate.Engine.: Device Generator
Candidates.#1....: $HEX[21217265626f756e642121] -> $HEX[042a0337c2a156616d6f732103]
Hardware.Mon.#1..: Temp: 70c Util: 66%
The <output_file> is empty:
wc cracked.txt
0 0 0 cracked.txt
The potfile is also empty ( ~/.local/share/hashcat/hashcat.potfile )
Same results (no hashes cracked) if I don't specify any output file.
So have I broken my hashcat? Am I making some basic mistake that I just can't see? (I pretty new to hashcat but have had results from basic commands like the above before.)
That line:
Candidates.#1....: $HEX[21217265626f756e642121] -> $HEX[042a0337c2a156616d6f732103]
should be the cracked passwords, right?, but it's in hex . . ?
Perhaps I've set something inadvertently? I found no .config files anywhere or are they called something else?
Maybe I'd be better off just upgrading to version 7.1? I already uninstalled and re-installed hashcat 6.2.6. . . . ?
Any thoughts or advice gratefully accepted, thanks.