Skip Navigation
Menu
Newsletters

Digital Forensics for Password-Protected Documents

2026.10.01

When collecting evidence for internal investigations, audits, litigation, and regulatory responses, documents may sometimes be inaccessible because they are protected by passwords set by their authors. If the employee who knows the password does not cooperate or has left the company, the client may be unable to make use of evidence that is known to exist. In this newsletter, we outline the principal methods used to remove passwords for protected documents, and introduce two matters in which our firm successfully handled such recovery.
 

1.

Common Methods for Removing Document Passwords

The two best-known password-removal methods are brute-force attack and dictionary attack.

A brute-force attack works by systematically testing every possible password combination. When a password may contain any mix of uppercase and lowercase letters, numbers, and special characters, the number of possible combinations grows roughly 90-fold with each additional character. As a result, a brute force attack becomes impractical for a password of ten or more characters with no restrictions on the permitted character composition, even with a GPU (Graphics Processing Unit), which can perform computations tens to thousands of times faster than a CPU.

A dictionary attack does not try every possible combination. Instead, it prioritizes combinations containing candidate words that are likely to relate to the password. Dictionary attacks fall into two types, depending on how the candidate-word list is constructed: (i) those that use a known password dictionary and (ii) those that use a custom dictionary. A known password dictionary draws on lists generated for research purposes or previously leaked passwords, while a custom dictionary is built from names, dates, and other terms associated with the relevant individual or matter.

The two approaches can also be combined, using candidate words for part of the password and brute-force techniques for the remaining characters.
 

2.

Cases of Removing Document Passwords
 

(1)

Company A — A Password-Protected File Discovered During an Audit

Company A discovered an Excel file with a suspicious filename on an audit subject’s PC but could not review its contents because the file was password-protected. When the client asked the subject to provide the password, he said that he could not remember it, though he recalled using a password of ten or more characters that included lowercase letters, numbers, and special characters.

The client had its own password-removal equipment, but applying it to a password of ten or more characters was difficult, and even if technically possible, testing every possible combination would have been impractical. The client therefore obtained the subject’s consent and engaged our firm to remove the password.

Designing a custom dictionary. After discussing the matter with the client, we decided to conduct a dictionary attack using a custom dictionary built from candidate words associated with the subject. For each candidate word, the dictionary included not only the word itself but a range of possible variations—its romanized form, the Korean word typed using the English keyboard layout, the word spelled in reverse, and combinations of these.

For the remaining character positions not covered by candidate words, we used brute-force techniques with numbers and special characters. This approach confirmed that a candidate word from the custom dictionary was part of the actual password, and we successfully removed the 12-character password within an hour.

This matter illustrates that a password too long for a brute force attack can still be removed within a realistic time frame through a dictionary attack, provided that the candidate words associated with the subject can be identified.
 

(2)

Company B — A Password-Protected Document Relating a Past Matter

While reviewing work it had performed in the past, Company B found that a document it had prepared was password-protected. Because a considerable amount of time had passed, none of the people involved could remember the password.

There were no clues about the length of the password or any candidate words. We advised the client that a long password might not be recoverable and proceeded with a brute-force attack.

Fortunately, the password proved to be short—six digits consisting only of numbers—and we identified it on the same day the client engaged us. This illustrates that, even without any clues, a password can be removed by brute force alone where its length is short or composition is structurally simple.
 

3.

Points to Note When Removing Passwords

Legal basis for removing a password: Because a password-protected document likely contains information the author intended to restrict from access, there should be an appropriate legal basis for removing the password. For example, the password should be removed only when the author has consented or where there is otherwise a clear legal basis for accessing the document. Password removal should also be limited to the files necessary within the confirmed scope of an internal investigation, audit, litigation, or regulatory response.

Compliance with document-handling procedures: Because a document whose password has been removed may later be used as evidence in litigation or disciplinary proceedings, the reliability of the removal process must be ensured. It is advisable to keep a reproducible record of why the password was removed, who performed the password removal and when, the method used, and how the file was secured and preserved, so that the chain of custody remains intact.

Password-removal environment: Our firm operates dedicated equipment fitted with high-performance GPUs for password analysis. Compared with CPUs, GPUs are well suited to parallel processing and can perform password-removal calculations at significantly higher speeds. When a password is too long for a simple brute force attack, however, the systematic character construction of the candidate-word list and the methodology used to test it become particularly important.

Variability in removal speed: The number of passwords that can be tried per second varies greatly with the performance of the password-removal system and the type of document. Even among Excel files, the speed can vary by thousands of times depending on whether the file is.xls or .xlsx. This is because software updates have strengthened document encryption specifications, with newer formats generally allowing fewer password attempts per unit of time on the same equipment. For this reason, the format and level of encryption of the target document must be identified first to make a realistic estimate of the time required for password removal.

Limitations: The cases described above reflect the results of individual matters, and not every password-protected document can necessarily be recovered within a practical period. Depending on the complexity of the password, a password may not be identified within a reasonable time—it may even take more than a week. It is therefore necessary to assess the complexity of the password and the characteristics of the document before deciding, on a case-by-case basis, whether to attempt password removal.

As these cases illustrate, our firm’s know-how in selecting likely candidate words and building a custom dictionary may enable recovery of even a relatively long password through a dictionary attack. A password made up of a limited character set or only a few characters can likewise be removed by brute force alone. 

Because password-protected documents often contain important information, removing the password and recovering access to those documents may provide important clues in identifying the underlying facts of a matter.

 

[Korean Version]

[Related Newsletter] Legal Tech Practical Issues Update 2026

 

Share

Close

Professionals

CLose

Professionals

CLose