Woltlab Burning Board 3.x Hash

Technical details, regex signatures, and cracking commands for the Woltlab Burning Board 3.x algorithm.

Regex Identification Signature:
^(\$wbb3\$\*1\*)?[a-f0-9]{40}[:*][a-f0-9]{40}$
Hashcat Command (Mode: 8400):
John the Ripper Command:
← Back to Hash Identifier

What is Woltlab Burning Board 3.x?

The Woltlab Burning Board 3.x password hashing scheme is a legacy cryptographic mechanism designed for the Woltlab Burning Board forum software, primarily used between the late 2000s and early 2010s. Structurally, it employs a hybrid approach combining MD5-based hashing with a custom iteration count and a non-standard salt implementation. The algorithm begins by concatenating the user’s password with a fixed-length salt (typically 8 bytes) and a version identifier, then processes the result through a series of MD5 iterations—originally 1,000 by default, though later versions allowed configurable iterations. The output is a 32-byte (256-bit) hexadecimal string, where the first 8 characters represent the iteration count, followed by the MD5 hash of the salted password. This format was intended to mitigate brute-force attacks by increasing computational overhead, but its reliance on MD5—an outdated hash function vulnerable to collision attacks—undermines its security foundations. The scheme’s primary use-case was password storage in legacy forum systems, where simplicity and compatibility with older PHP implementations took precedence over cryptographic robustness.

The Woltlab Burning Board 3.x hashing scheme is critically vulnerable to cracking due to its fundamental design flaws and exploitable characteristics. The absence of a cryptographically secure salt (e.g., per-user salts) allows attackers to precompute rainbow tables targeting common passwords, as the same salt is often reused across users. Additionally, the MD5-based iteration mechanism is susceptible to GPU/ASIC acceleration, with tools like Hashcat achieving cracking speeds of hundreds of thousands of hashes per second using optimized kernels. The fixed iteration count (even when configurable) can be bypassed via brute-force or dictionary attacks, especially when combined with weak passwords. Furthermore, MD5’s inherent collision resistance is insufficient for password storage, enabling length-extension attacks and preimage attacks. The scheme’s reliance on a predictable salt format and its compatibility with legacy systems further exacerbates its vulnerability, making it a prime target for offline cracking campaigns.

Identifying Woltlab Burning Board 3.x Hashes

Identifying a hash blindly is often difficult because multiple algorithms can output strings of the exact same length. For example, a standard 32-character hexadecimal string could be MD5, NTLM, MD4, or LM. To definitively identify Woltlab Burning Board 3.x, security researchers analyze the hash against a strict regular expression (regex) signature (shown above) to find structural matches.

How to Crack Woltlab Burning Board 3.x

If you need to recover the plaintext password for a Woltlab Burning Board 3.x hash during a penetration test or forensics investigation, you must supply the correct module ID to your cracking software. Use the exact commands provided at the top of this page to target the hash successfully.