hashcat Forum - Beta Tester

Old restore file writed.

Sat, 24 Feb 2024 13:48:20 +0000

v6.2.6-496-gd127558bb

-w 4

Session..........: xxx
Status...........: Aborted (Checkpoint)
Hash.Mode........: 1000 (NTLM)
Hash.Target......: ntlm.txt
Kernel.Feature...: Optimized Kernel
Guess.Base.......: Mask (?a?a?a?a) [4], Left Side
Guess.Mod........: File (r_5_plus.txt), Right Side
Speed.#1.........: 14756.4 MH/s (325.65ms) @ Accel:256 Loops:1024 Thr:512 Vec:1
Speed.#2.........: 1924.7 MH/s (416.84ms) @ Accel:256 Loops:1024 Thr:32 Vec:4
Speed.#*.........: 16681.1 MH/s
Recovered........: 237/2447941 (0.01%) Digests (total), 237/2447941 (0.01%) Digests (new)
Remaining........: 2447704 (99.99%) Digests
Recovered/Time...: CUR:0,1,N/A AVG:0.35,20.92,N/A (Min,Hour,Day)
Progress.........: 448394161490000/1540882190694375 (29.10%)
Rejected.........: 6516050000/448394161490000 (0.00%)
Restore.Point....: 786439/18917991 (4.16%)
Restore.Sub.#1...: Salt:0 Amplifier:81449984-81450625 Iteration:0-1024
Restore.Sub.#2...: Salt:0 Amplifier:81449984-81450625 Iteration:0-1024
Candidate.Engine.: Device Generator
Candidates.#1....: v"~}12261954 -> ~?~7234025
Candidates.#2....: v"~}12345 -> ~?~12261959

Electrum Token length exception hashcat beta 6.1.1.136

Tue, 30 Mar 2021 16:33:37 +0000

hashcat.exe -m 21700 -a 3 electrumhash.txt ?a?a?a?a?a?a?a?a?a -i --increment-min=1 --increment-max=9 --outfile-autohex-disable -w 2

hash:
$electrum$4*0227...4bfacc8829

What am I doing wrong?

1080TI 11gb benchmark shows BCRYPT 9079h/s

Fri, 08 Jan 2021 12:21:53 +0000

Hi,

Benchmark shows 9079H/s from 3200 bcrypt.
what i actually get is only 742 H/s on Temp: 74c Fan: 54% Util:100% Core:1911MHz Mem:5005MHz Bus:16

I have read that bcrypt runs beter on CPU mode. i have dual xeon machine besides*Not using atm.

Tryed to use -D 1 commands on machine but i get this error.

hashcat -D 1 -m 3200 -a 0 -o ./UPWResults.txt -w 4 ./UPWhashes.txt c:/rockyou.txt
hashcat (v6.1.1-116-gfb219e0a6) starting...

Successfully initialized NVIDIA CUDA library.

Failed to initialize NVIDIA RTC library.

* Device #1: CUDA SDK Toolkit installation NOT detected or incorrectly installed.
CUDA SDK Toolkit installation required for proper device support and utilization
Falling back to OpenCL Runtime

No devices found/left.

Help to split list into 2 files USER:PASS

Fri, 08 Jan 2021 07:56:43 +0000

Hello guys,im trying to get ready to test Assosiations attack mode. Need to split my combo
as shows in thread example:

2. This is the point where you typically start. You have a hashlist in username:hash format. We need to split them in order to use them with the new attack-mode.

Code:
$ cut -d: -f1 < final.txt > wordlist.txt
$ cut -d: -f2 < final.txt > hashlist.txt
...........................................................................................

Im using win10.

tryed hashcat cut -d: -f1 < final.txt > wordlist.txt
RESULT: hashcat cut -d: -f1 < UPWhashes.txt > wordlist.txt
hashcat: unknown option -- f
Invalid argument specified.

tryed hashcat cut -d:-f1 < final.txt > wordlist.txt
RESULT:hashcat cut -d:-f1 < UPWhashes.txt > wordlist.txt

Invalid device_id 0 specified.

My combo list looks like this. user:bcrypt.
userplaintextnickname:$2y$10$sIgXXXxTte.v19t.QduI4mgPuC9UUxXXXXcQFvltcaqVhya

Please help novice person

6.1.1 vs 4.5.1 some modes don't work anymore

Fri, 30 Oct 2020 05:18:19 +0000

Hashcat 6.1.1 -a0 works fine, -a5,6,7 - do not, hanging on "Initializing backend runtime for device #1...", memory usage going to max (I have 10GB) then swap files gets beating. Hashcat 4.5.1 works just fine on all modes.

OpenCL API (OpenCL 2.1 AMD-APP (2906.10)) - Platform #1 [Advanced Micro Devices, Inc.]
=======================================================================
* Device #1: Pitcairn, 1984/2048 MB (1523 MB allocatable), 20MCU

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Dictionary cache built:
* Filename..: example.dict
* Passwords.: 128416
* Bytes.....: 1069601
* Keyspace..: 128416
* Runtime...: 0 secs

Hashes: 2 digests; 2 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers applied:
* Zero-Byte
* Single-Salt
* Slow-Hash-SIMD-LOOP

Watchdog: Temperature abort trigger set to 90c

Initializing backend runtime for device #1...

Running on Win7_64, hash / dict don't matter, command line:

hashcat.exe Home.hccapx -t 32 -a 7 -m2500 --self-test-disable ?a?a?a?a example.dict

Anyone seeing something like this? Should be reported long ago - pretty gross so may be something on my side

New Attack-Mode: Association Attack

Tue, 29 Sep 2020 13:59:05 +0000

With commit 04d5e5a119ba4c44bedb5bcccd5a42f82463cca3 I have added a new attack-mode called "Association Attack" (a different name could be "Context Attack"), but let's stick to "Association Attack" for reference. This attack is not yet ready to be used in a production environment, it's a very early first version, but I wanted you to play with it.

If you ever used JtR before, the "Association Attack" is somehow of what the "single mode" is in JtR. The attack-mode is strong if you have large -salted- hashlist and at the same time you have some "hint" or "information" for each of the hashes inside the hashlist. Typically the username. The username itself could be seen as a "hint", because some humans tend to use the username as a part of the password. Or the username contains parts of the password because the username is changed for the site the username is used. Then we can extract this information using rules.

The main idea of this attack is to not try all the different (unique) salts with all password candidates from a wordlist, but to only attack each of the hashes in the hashlist with the associated "hint". From a development perspect, we remove the loop in hashcat which iterates through the different salts. To make this attack more efficient, we typically use the "hint" in combination with rules (but that's not a requirement). Using a GPU for this task is not so easy because of the many cores that we have and that we have to give work to. That brings us to an important requirement. Your hashlist needs a large number of unique salts to make this attack efficient (to utilize the GPU fully). Ideally the number of GPU Processors * 64 (or more). You can find out about the GPU Processors of your GPU using hashcat -I. My GTX980 has 16, so I need a hashlist of at least 1024 entries to fully utilize the GPU.

Unrelated Pro-Tip: If you want to attack a slow single hash with a single word but with some rules added to it, then the capitalized -S is what you want.

When I first created this patch I was thinking of how the user could specify what is the "hint" for each of the hashes. In JtR's single mode it simply uses the username from the hashlist. This is very easy to handle, but it's not exactly what I was looking for. In hashcat we specify a hashlist as regular (with or without username) but we also provide a wordlist as regular. However, this wordlist has to have exactly the number of lines as the hashlist. This has both advantages and disadvantages, but I liked the idea to use this even with a folder with many wordlists. This is kind of the opposite of what creates the efficiency of this attack, but I think there are some situations where multiple wordlists make sense. For instance, if you have large portions of substrings which were added to a passwords afterwards, by yubikeys on keypress, by site specific pepper strings or by user using the company name. I can also try to make it 1:1 as in JtR where the username is building some sort of virtual wordlist in memory, but only if I see that you people are really interested in this attack-mode.

One of the problems I was thinking of is if it is possible to have a mixed version of this attack-mode and a regular rule-based straight attack-mode in combination with -S. That could be useful if you have let's say only 10 hashes, because this is not enough to keep the GPU busy and then combine it with rules. This is a more complicated code change and again if I see you people being interested in it.

So here's how you use it. In a first step we will build a demonstration dataset (hashlist) in username:hashlist format as you probably have it and then I show you how to split it so you can use it with the new attack-modes.

1. Build the test dataset, creating a bcrypt hashlist

Code:
$ head -10000 example.dict > wordlist.txt

$ shuf wordlist.txt | sponge wordlist.txt

$ tools/test.pl passthrough 3200 < wordlist.txt > hashlist.txt

$ perl -e 'open (IN, "wordlist.txt"); my @a = ; close (IN); open (IN, "hashlist.txt"); my @b = ; close (IN); for (my $i = 0; $i < scalar @a; $i++) { chomp $a[$i]; chomp ($b[$i]); printf ("%s:%s\n", $a[$i], $b[$i]); } print scalar @b' > final.txt

$ rm wordlist.txt hashlist.txt

The resulting "final.txt" looks like this:

Code:
$ more final.txt 

001071:$2a$05$KReyKhSyKRi0LBSwLBWyLOj88ZjDCPMD83re/SBNJ9TXJrrPLDbwW

02011511:$2a$05$LBCyKhC1MRGvLxeuLxOxMOilYzVzEnWVFr79uLTj6vTPAPO2y2tbS

01papirus:$2a$05$MB.3MBazLhW0MRKzMBSzKOsHZE77Ou9mGW88yOG2Q5TxF5yvLe48C

010108dh:$2a$05$LBGyLBeuKxavLh.3MRWyLOhOiQVGYyUBYE.rOUiRomCQFGIZfutEK

000123258:$2a$05$LxiwMR.wKhGvKBiyKxeuM.rHYpUIrIOLksCsvo//8YT5J5z28rzBW

...

2. This is the point where you typically start. You have a hashlist in username:hash format. We need to split them in order to use them with the new attack-mode.

Code:
$ cut -d: -f1 < final.txt > wordlist.txt

$ cut -d: -f2 < final.txt > hashlist.txt 

3. Here's a traditional -a 0 attack. This will work fine, but take a look at the time it takes.

Code:
$ ./hashcat -m 3200 hashlist.txt wordlist.txt -o result.txt

Code:
...

Time.Started.....: Tue Sep 29 15:38:06 2020 (2 secs)

Time.Estimated...: Tue Sep 29 18:25:37 2020 (2 hours, 47 mins)

...

Recovered........: 6/10000 (0.06%) Digests, 6/10000 (0.06%) Salts

...

In 2+ hours all the 10000 hashes will be cracked. If you know hashcat you know it will finish sooner because as soon as one unique salt has been fully cracked, it does not need to retry that salt, etc. But it will take some time, but you can't beat the -a 9 as you will see next.

4. New attack mode, the syntax is the same just add the -a 9:

Code:
$ ./hashcat -m 3200 hashlist.txt wordlist.txt -o result.txt -a 9

Code:
...

Time.Started.....: Tue Sep 29 15:40:46 2020 (2 secs)

Time.Estimated...: Tue Sep 29 15:40:48 2020 (0 secs)

...

Recovered........: 10000/10000 (100.00%) Digests, 10000/10000 (100.00%) Salts

...

So it cracked all 10000 bcrypt in just 2 seconds. This is really not black magic and only worked because we had the right password.

In reality the idea is if you have a large salted hashlist, for instance bcrypt, and you have the usernames for it. Run the -a 9 first with rules. This will crack some of the hashes in a very short time. If you then start your regular -a 0 attack you have already removed a good portion of the unique salts, so it will be a faster.

--
atom

Any hashcat user with AMD cards on macOS wanted for troubleshooting

Fri, 08 May 2020 08:45:08 +0000

Unfortunately, the developer team has no such hardware (new Apple iMac or iMac pro or any new high-end macbook with AMD cards) to test some problems with macOS (we believe only latest version and/or new AMD driver).

We get complains about not being able to compile latest hashcat with error:

Code:
fatal error: 'inc_vendor.h' file not found

#include "inc_vendor.h"

              ^

see https://github.com/hashcat/hashcat/issue...-625173962 and other reports here:
https://github.com/hashcat/hashcat/searc...ype=Issues

It would be nice if we could get some help from hashcat users that have such a hardware to test and want to play around a little bit with the changes/code etc:
1. does this happen only with a specific macOS/driver version
2. when was this introduced ? already available with release versions , which commit introduced this error: https://github.com/hashcat/hashcat/commits
3. why does it happen ? any clue about why the file can't be found ? maybe related to some paths etc (we already have some other problems with compiler include problems with AMD/ROCm using paths with -I ).
etc etc etc

it would be great if somebody could play around a little bit with latest git code (master branch) and try also older commits or versions of hashcat to see when this was introduced and if it even has something to do with hashcat or is ... as very often .. just a driver problem.

Our current educated guess is that it is a specific new AMD include problem (using the JiT compilers -I include paths) and that this problem is related to some (new) AMD driver version etc...

Thank you very much

It is needless to say, that first you need to be able to reproduce/see this "file not found" error, otherwise you might not be able to help much... but any feedback (even saying "it works with AMD card with macOS version XYZ") could help to pinpoint it

(you could of course contact us here below, or via PM, or on #hashcat IRC, freendode etc)

5.1.0-91+ needed (I think)

Wed, 06 May 2020 17:15:42 +0000

I'm using an RX580 AMD card to try and use a combination attack on a hccapx file and I'm getting this error

* Device #1: ATTENTION! OpenCL kernel self-test failed.

Your device driver installation is probably broken.
See also: https://hashcat.net/faq/wrongdriver

Aborting session due to kernel self-test failure.

You can use --self-test-disable to override this, but do not report related errors.n.

I have been doing some reading around the forums and came across some people that said 5.1.0 has issues with AMD cards and that beta 91 or higher fixes the problem. Where can I find this download, I've searched everywhere. Perhaps someone can email it to me? Or perhaps someone knows how to fix this issue. My card is updated to the latest driver by the way

3rd GPU will not run in betas

Sun, 05 Apr 2020 03:11:12 +0000

I've been running 2 1080ti's on 5.1-1733 using cygwin. Occasionally it will start and show copying on both devices then stop. I recently added another gpu and it will run any 2 of them together, but when all 3 are selected it usually shows copying and stops. Rarely it will run 1 device and show the other 2 copying. I have also tried it on 5.1-1772 with the same results. It works fine on 5.1, but I lose mode 22000. I Have also removed and reinstalled drivers.

Hashcat freezes

Sun, 29 Mar 2020 10:58:16 +0000

Hi!
I have Ubuntu 16 with installed Cuda 10.2 and Last Nvidia drivers - geforce 440.64
The system has 16 gb RAM , Core i3 and 7x1080ti
I compiled Hashcat from last github source. And have a strange bug:

CUDA API is using.

- I have dictionary splitted on files by 512mb.
- If i using -m 21700 or -m 21800 - hashcat always freezes on 70-86% progress in same files (for example always on dict4 and dict9). When i press S for status it just print in cmd line and nothing happend. Then i should use cntrl-c to stop proccess. (look attachment)
- If i use ./hashcat --restore after abort. It freezes too.
- I tried to use different hash's - but no results.
- If i using -m 11300 - i haven't any problems.

./hashcat -a 0 -m 21700 /mnt/hdd/hash/ehash.txt /mnt/hdd/pass.txt.004

How can i catch where the bug ?

hashcat.jpg (Size: 81.71 KB / Downloads: 4)

Electrum 4 and 5 Token length exception (ver 5.1.0+1736)

Sun, 08 Mar 2020 23:20:24 +0000

Hello, i wanted to test feature to brute electrum 4 and 5 salt, but have such error

Hashfile 'e_hash.txt' on line 1 ($elect...f899539ae96be83fa8bb91c6bf230ba0): Token length exception
No hashes loaded.

Test Hash of EMPTY electrum in attachments

5.1.0+1394 not processing LM hashes

Wed, 28 Aug 2019 16:07:57 +0000

I'm not for sure if I am supposed to report bugs for beta versions, but it seems the latest beta will not load any LM hashes for processing.

CUDA Installation not detected

Sat, 27 Jul 2019 10:13:44 +0000

Hi, I have a problem. I'm using freshly compiled version of hashcat from github. There is CUDA support, and I've installed CUDA Toolkit 10.1 and the latest display driver. However, hashcat doesn't detect CUDA. Here is the output

Code:
* Device #1: CUDA SDK Toolkit installation NOT detected.

            CUDA SDK Toolkit installation required for proper device support and utilization

            Falling back to OpenCL Runtime

* Device #1: WARNING! Kernel exec timeout is not disabled.

            This may cause "CL_OUT_OF_RESOURCES" or related errors.

            To disable the timeout, see: https://hashcat.net/q/timeoutpatch

OpenCL API (OpenCL 1.2 CUDA 10.1.152) - Platform #1 [NVIDIA Corporation]

But the weird thing is, that it says OpenCL 1.2 CUDA 10.1.152, but still uses OpenCL. What can be the problem?

hashcat beta - supported CUDA version?

Fri, 19 Jul 2019 20:40:53 +0000

Code:
NVIDIA-SMI 418.56      Driver Version: 418.56      CUDA Version: 10.1

Code:
hashcat (v5.1.0-1223-ga7fd1e40) starting...

Outdated NVIDIA CUDA Toolkit version '10010' detected!

See hashcat.net for officially supported NVIDIA CUDA Toolkit versions.

but i don't see CUDA versions advertised anywhere on hashcat.net :/

compiling makefile github

Mon, 08 May 2017 20:04:09 +0000

how do i compile a program from source?

i see a make file but i get errors when i try for example executing the make file (after chmod'ing the make file to make it executable)

anyone know the commands to build from a source code?

i am on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) linux witch is based on debian.