Saturday 22 | 08:13:PM
Hello breached forums,
Today I will be releasing my hashcat output parser POSIX tool.
Example of what this tool does.
Takes in hashcat output ( from a file after the -i flag ):
./result.txt
$2a$10$D56rqff24SXk4S5wdOIfOODctELn8tqKZj1kxXT/17kgWy4pB5FCy:123456
$2a$10$EIyWR6LQLVTuqj9SVxa.aeu3dOgbojEIJrrJMBOSp.4aloJc7SHU2:123456
$2a$10$EsW3q1CSSwdShBz.RAO/2.xEbbGdY0Po1lIGsayOu06ueEDHXALsi:123456
Then takes in a file that still has hashes ( from a file after the -b flag ):
./yourdatabreach
somename
omeemail:$2a$10$D56rqff24SXk4S5wdOIfOODctELn8tqKZj1kxXT/17kgWy4pB5FCy
somename2
omeemail2:$2a$10$EIyWR6LQLVTuqj9SVxa.aeu3dOgbojEIJrrJMBOSp.4aloJc7SHU2
somename3
omeemail3:$2a$10$S6aCPjN.93JMbmkiYZCPxutRlyLVg5/U1PddnyuWJrVt//1Ap2Ji6
somename4
omeemail4:$2a$10$EsW3q1CSSwdShBz.RAO/2.xEbbGdY0Po1lIGsayOu06ueEDHXALsi
and will replace the hash copy the line and append to a file ( -o is output name, none specified is a timestamp )
somename
omeemail:123456
somename2
omeemail2:123456
somename4
omeemail4:123456
so why should you use this? its much more consistent than you using grep which would lead to you messing up either your hashcat output the input db or your matched list and it also has various features such as:
FOSS
intuitive
duplication prevention
verbosity
runs on any linux system ( also uses grep which relies on read and write speed and not ram, this can match a new db on a pi in a few seconds assuming you have a fast connection to a fast storage device ( usb 3.0 or later will only be a few seconds )
ability to take in any db not just email:hash. Ex: ( someemail, somename, somehash ) it will still replace all hashes
PS: I am working on a program to parse any raw db not just email:hash. Ex: ( someemail, somename, somehash ) comma separated values (csv) tab separated values (tsv) JSON and more. Any donations will certainly keep this off the back burner for me
Repo here
if you would like to donate I accept XMR:42LAJKfzabr9s8UGx11qaj8bwR8wdeRGJAFzSYB5uDChTLo3nrv1K
Today I will be releasing my hashcat output parser POSIX tool.
Example of what this tool does.
Takes in hashcat output ( from a file after the -i flag ):
./result.txt
$2a$10$D56rqff24SXk4S5wdOIfOODctELn8tqKZj1kxXT/17kgWy4pB5FCy:123456
$2a$10$EIyWR6LQLVTuqj9SVxa.aeu3dOgbojEIJrrJMBOSp.4aloJc7SHU2:123456
$2a$10$EsW3q1CSSwdShBz.RAO/2.xEbbGdY0Po1lIGsayOu06ueEDHXALsi:123456
Then takes in a file that still has hashes ( from a file after the -b flag ):
./yourdatabreach
somename

somename2

somename3

somename4

and will replace the hash copy the line and append to a file ( -o is output name, none specified is a timestamp )
somename

somename2

somename4

so why should you use this? its much more consistent than you using grep which would lead to you messing up either your hashcat output the input db or your matched list and it also has various features such as:
FOSS
intuitive
duplication prevention
verbosity
runs on any linux system ( also uses grep which relies on read and write speed and not ram, this can match a new db on a pi in a few seconds assuming you have a fast connection to a fast storage device ( usb 3.0 or later will only be a few seconds )
ability to take in any db not just email:hash. Ex: ( someemail, somename, somehash ) it will still replace all hashes
PS: I am working on a program to parse any raw db not just email:hash. Ex: ( someemail, somename, somehash ) comma separated values (csv) tab separated values (tsv) JSON and more. Any donations will certainly keep this off the back burner for me
Repo here
if you would like to donate I accept XMR:42LAJKfzabr9s8UGx11qaj8bwR8wdeRGJAFzSYB5uDChTLo3nrv1K