b2KIT

Hash Cracker Simulator

Educational tool demonstrating dictionary and brute-force hash cracking techniques against common hash types.

Tested tool guide Tested browser tools Checked August 16, 2026

What Hash Cracker Simulator does, with a checked example

Given a hash, this tool tries to recover the plaintext behind it. You choose a hash type, supply a hash (or let the tool generate one), then run a dictionary attack over a built-in list of common and leaked passwords, or a brute-force attack that generates every combination up to a short length. Each candidate is hashed and compared against the target. The surprise most people hit: cracking never reverses a hash. Every attempt is a fresh guess, so a match proves only that the password was in the tested set, and a miss proves nothing about the password's real strength.

Worked example

A concrete input and expected output from the current implementation.

Input

5f4dcc3b5aa765d61d8327deb882cf99 (MD5, dictionary attack)

Expected output

Match found: password (recovered by dictionary attack)

5f4dcc3b5aa765d61d8327deb882cf99 is the MD5 hash of the string 'password'. The tool hashes each dictionary candidate with MD5 and compares the result to the target; 'password' appears on any common-password list, so the dictionary sweep ends with a match.

How the result is produced

1

Dictionary attack

The dictionary attack hashes every entry in a built-in list of common, reused, and previously leaked passwords using the selected algorithm, and compares each result to the target hash. A counter tracks how many candidates have been tried, and the search stops at the first match or when the list runs out. If the list is exhausted without a match, the password is simply not in the list.

2

Brute-force attack

Brute force abandons the wordlist. The tool generates every combination over a chosen alphabet (for example lowercase letters plus digits), starting at one character and growing in length, hashing and comparing each one exactly as the dictionary attack does. Candidate count grows exponentially, so the work roughly multiplies by the alphabet size for every extra character. That is why the search stops after a few characters: longer passwords make it take effectively forever.

Good uses

  • Learning, or teaching, how cracking actually works: run both attacks on hashes you create, watch the counters, and see which passwords fall in seconds.
  • Stress-testing a password you are about to adopt: if the dictionary finds it, any attacker with the same list would too.
  • Comparing hash types side by side: the same plaintext under MD5, SHA-1, and SHA-256 shows that a weak password stays weak no matter which algorithm hides it.

Limits and checks

  • Algorithm and salt mix-ups: the same password produces a different hash under each algorithm, and a salted hash (salt mixed into the input before hashing) cannot match any candidate computed from the bare password. Choose the wrong algorithm or ignore salt and the tool can never match, even with the password in its dictionary.
  • 'Not found' is a statement about the candidate set, not the password: a dictionary miss only says the password was not on that list, and brute force never reaches long passwords. The tool cannot certify strength.
  • Speed numbers are the simulator's own: the candidates-per-second figure and any elapsed-time estimate belong to this tool, not to real hardware. Real cracking rigs differ by orders of magnitude, so treat results as a demonstration of growth, not a benchmark.

Common questions

Can I paste in any hash and get the password back?

No. It only recovers plaintexts that sit in its dictionary or fit inside its short brute-force length limit, which is exactly the lesson: real cracking succeeds against weak choices, not arbitrary ones. If the search gives up, that tells you nothing about the password except that it was not among the tested candidates.

Does this actually attack a real system, and does my hash leave the browser?

No to both. The search runs entirely in your browser: the tool generates its own candidates and compares them locally, so nothing is uploaded and no system is touched. The target hash exists only in your session. The tool demonstrates the technique, and gives you the vocabulary to judge real cracking tools without running them.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools