Hashcat can crack using wordlists but not brute force?
#1
Hey all,

Having a weird issue with Hashcat. When using bruteforce, it doesn't seem to be able to come up with a matching hash.

It will only identify a matching hash through a wordlist attack.

Has anybody encountered this issue before?

EDIT: Nvm, it seems to work fine using CL or Powershell. It only seems to mess up when using Hashcat GUI
Reply
#2
Strange, i was once again not able to crack a NTLM hash using brute force, nor was i able to do it using a wordlist.

This time i tested AbcD123!

which should have used a hash of
Quote:EFEFC3E0B02E74D5B174922814073831

Interesting.
Reply
#3
Seems to work, what command did you use?
Reply
#4
(08-25-2024, 02:08 PM)lapsikmees Wrote: Seems to work, what command did you use?

Sorry for the late reply, here's a direct output from HashcatGUI:

Code:
hashcat.exe -a 3 --session=2024-09-08 -m 1000 -w 3 --status --status-timer=60 -p : -O --hwmon-temp-abort=90 -d 1 -o "\hashcat-6.2.6\Output\Test" --outfile-format=1 -t 60 -i --increment-min=6 --increment-max=12 -1 ?d?l?u?s "\hashcat-6.2.6\Input\Test.txt" ?1?1?1?1?1?1?1?1?1

I thought it was weird that the output file was put before the input so I switched them over but that didn't change the outcome.
Reply
#5
Remove `-t 60`. It makes bruteforce non-exhaustive.
Reply
#6
The md5 is incorrect.
How did you calculate it?
Try with this instead:

59b2800c6287a327eb9b311cd24e0e29
Reply
#7
(09-09-2024, 07:14 PM)b8vr Wrote: The md5 is incorrect.
How did you calculate it?
Try with this instead:

59b2800c6287a327eb9b311cd24e0e29

Nevermind. You're working on ntlm 😅 my bad
Reply