Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Hashcat recovers passwords from their stored hashes using GPU acceleration, supporting hundreds of hash formats and several attack strategies far smarter than exhaustive guessing.

What Is Hashcat?
Hashcat is a password recovery tool that works offline against captured hashes. Given a file of hashes and told which algorithm produced them, it generates candidate passwords, hashes each one, and compares the result. It is open source, it runs on GPUs, and it supports several hundred hash and key derivation formats.
Everything interesting about it follows from the word offline. Online attacks against a login page are constrained by rate limiting, account lockout, and monitoring, and a few thousand attempts is a lot. Once an attacker holds the hashes, none of those constraints exist. A single consumer graphics card tests billions of candidates per second against a fast algorithm, and no log entry is generated anywhere.
Exhaustive brute force is the least important mode, because people do not choose random passwords. The modes that matter exploit that fact.
best64 and the larger community rule files encode patterns observed in hundreds of millions of cracked passwords.The gap between hash functions is the single most important fact in this area, and it is a difference of many orders of magnitude.
Running Hashcat against your own hash dump is one of the most informative security exercises available, and the results reliably contradict what the policy document claims. Typical findings: the company name with the current year, seasonal passwords matching the rotation interval exactly, the same base word across hundreds of accounts, and service accounts whose passwords have not changed since the system was commissioned.
The implications align with current NCSC guidance rather than with traditional complexity rules:
In an authorised engagement the hash dump is the most sensitive artefact produced. It should be encrypted at rest, held only for the agreed period, excluded from the report in raw form, and destroyed on a documented schedule. Under UK GDPR it is personal data, and losing it is a breach in its own right. Reports should present statistics, patterns, and the specific weak accounts, never a list of recovered plaintext passwords circulated by email.
At Privia Security, our Penetration Test Services include password audit work with agreed handling controls for the hash material.
It depends on the algorithm far more than on the password. An eight-character NTLM hash falls to exhaustive search in hours on a modest GPU rig. The same password stored with bcrypt at a reasonable cost factor could take years. Against rule-based dictionary attacks, predictability is what matters: a long passphrase built from real words still falls if it is a known phrase.
A dictionary attack with transformations applied to every candidate: capitalisation, digit and symbol appending, character substitution, reversal, and duplication. A rule file containing thousands of transformations turns a ten million word list into tens of billions of realistic candidates. The rules encode patterns observed in hundreds of millions of real cracked passwords, which is why they work so well.
Yes, as a controlled audit with written authorisation and agreed handling for the hash material. It is the only way to learn what people actually choose rather than what policy requires. Report statistics and patterns, not plaintext lists, encrypt the material at rest, and destroy it on a documented schedule. Under UK GDPR it is personal data throughout.
Less than expected, and sometimes the opposite. Prescriptive rules narrow the search space, because a known structure can be expressed as a mask, and they push users towards predictable substitutions. NCSC guidance favours length, three random words, screening against breach corpora, and rotation only on evidence of compromise, combined with multi-factor authentication to limit the damage.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.