Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A dictionary attack guesses passwords from a curated list of likely candidates rather than every possible combination, which is why it succeeds where pure brute force would take centuries.

What Is a Dictionary Attack?
A dictionary attack is password guessing driven by a list of likely candidates rather than by exhaustive enumeration. Instead of trying every combination of characters, the attacker works through words, names, phrases, and previously breached passwords, on the sound assumption that human beings do not choose randomly.
The distinction from a brute force attack is one of strategy, not of mechanism. Brute force covers the whole keyspace and will always succeed eventually, which for anything beyond eight characters means never in practice. A dictionary attack covers a tiny fraction of the keyspace and succeeds very often, because real passwords cluster in a small region of it.
Modern wordlists are built from breaches, not from the Oxford English Dictionary. The best known, rockyou.txt, contains roughly 14 million unique passwords recovered from the RockYou breach of 2009 and is still startlingly effective. The SecLists project aggregates dozens of similar collections, and Have I Been Pwned publishes a dataset of hundreds of millions of passwords seen in breaches, distributed as hash prefixes so it can be queried without revealing anything.
Attackers then add organisation-specific material: the company name, product names, local football clubs, the town the office is in, and the current and previous month and year. A list of a few thousand such candidates will often beat a generic list of millions against a single target.
Raw wordlists are only the starting point. Cracking tools apply mangling rules that transform each candidate — capitalise the first letter, append digits, substitute characters, reverse the word, duplicate it. Hashcat ships with rule sets such as best64, and community rule sets expand a single word into hundreds of variants at negligible cost.
The consequence is worth stating plainly: P@ssw0rd2026! provides no meaningful protection over password. Every substitution a person thinks of is already encoded in a rule file, and the hybrid of dictionary word plus mask is one of the first attacks any tester runs.
The two settings behave very differently.
We run password audits against recovered hashes as part of our penetration test services, which tends to be the most persuasive way to make the case for a breach list.
Brute force tries every possible combination of characters and is guaranteed to succeed given unlimited time, which for realistic password lengths means it never finishes. A dictionary attack tries a curated list of likely candidates, usually drawn from previous breaches, plus rule-based variations. It covers far less of the keyspace but succeeds far more often, because human password choices are predictable.
Barely, when the base is a dictionary word. Cracking tools apply mangling rules that automatically capitalise, append digits and years, and substitute characters, so predictable transformations are covered at almost no extra cost. Length and unpredictability are what matter. Three random words produce far more resistance than a short word decorated with substitutions.
A slow, salted algorithm designed for the purpose: Argon2id where available, otherwise bcrypt or scrypt with parameters tuned so that a single verification takes a noticeable fraction of a second. Avoid fast general-purpose hashes such as MD5, SHA-1, or unsalted SHA-256, which modern hardware evaluates in the billions per second.
The NCSC advises against routine expiry, because it pushes people toward predictable incremental variations and offers little protection against the attacks that actually occur. Change passwords when there is a reason: a suspected compromise, an appearance in a breach dataset, or a shared credential changing hands. Pair that with breach list checking and multi-factor authentication.
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.