PKZIP (Mixed Multi-File) Hash

Technical details, regex signatures, and cracking commands for the PKZIP (Mixed Multi-File) algorithm.

Regex Identification Signature:
^\$pkzip2?\$([2-8])\*[0-9]{1}(\*[0-9]{1}\*[0-9a-f]{1,8}\*([0-9a-f]{1,8})\*[0-9a-f]{1,8}(\*[0-9a-f]{1,8})?\*[0-9a-f]{1,8}\*[0-9a-f]+)+\*([08])\*[0-9a-f]{1,8}(\*[0-9a-f]{1,8})?\*[0-9a-f]{1,8}\*[a-f0-9]+\*\$\/pkzip2?\$$
Hashcat Command (Mode: 17225):
John the Ripper Command:
← Back to Hash Identifier

What is PKZIP (Mixed Multi-File)?

The **PKZIP (Mixed Multi-File)** hash format originates from the proprietary **PKZIP** compression algorithm developed by **Phil Katz** in the late 1980s, later standardized as part of the **ZIP file format** (RFC 1951). This hash variant was introduced as a **checksum mechanism** for verifying the integrity of archived files within ZIP archives, particularly in versions prior to the adoption of **CRC-32** as the standard. The structure of this hash is derived from a **rolling hash** technique, combining elements of **bitwise operations** and **polynomial division** to generate a 32-bit checksum for each file segment. Unlike modern cryptographic hashes, it was not designed for security but rather for **error detection** during data transmission or storage. The primary use-case was ensuring data integrity in early ZIP archives, where files were often split across multiple disks or networks, necessitating lightweight verification without full cryptographic guarantees.

The **PKZIP Mixed Multi-File** hash is vulnerable to cracking due to its **deterministic nature, lack of cryptographic properties, and computational inefficiencies**. The algorithm relies on a **fixed polynomial (0x04C11DB7)** and a **non-salted rolling checksum**, making it susceptible to **brute-force attacks** when combined with **GPU-accelerated hash cracking tools** (e.g., Hashcat). Additionally, its **32-bit output space** (4 billion possible values) is trivial to exhaust via modern hardware, especially when targeting **weak or predictable inputs** (e.g., short strings or default filenames). Unlike cryptographic hashes, PKZIP’s design lacks **avalanche effects**, meaning minor input changes rarely alter the output significantly, facilitating **collision attacks** and **rainbow table precomputation**. Furthermore, its **linear complexity** (O(n)) allows for **optimized parallel cracking**, rendering it effectively broken for any security-sensitive application.

Identifying PKZIP (Mixed Multi-File) 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 PKZIP (Mixed Multi-File), security researchers analyze the hash against a strict regular expression (regex) signature (shown above) to find structural matches.

How to Crack PKZIP (Mixed Multi-File)

If you need to recover the plaintext password for a PKZIP (Mixed Multi-File) 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.