Case Report | The “Hacking Tool” Allegation and a Breakthrough on Day 37: How Did an Installer Hash Mismatch Help Secure Bail?
Basic case information
| Charge | Suspected provision of programs or tools for intrusion into or unlawful control of computer information systems |
|---|---|
| Client’s role | Provider of the software program in question |
| Stage at which counsel took over | During criminal detention, with submissions at the arrest review stage |
| Outcome | On day 37 of criminal detention, the procuratorate declined to approve arrest and the police arranged release on bail |
I. The predicament: A serious cybercrime allegation amid technical uncertainty and a 37-day deadline for arrest approval
Amid the current crackdown on online offences and illicit or grey-market activity, the offence of “providing programs or tools for intrusion into or unlawful control of computer information systems” is one of the most technically demanding and easiest to misclassify.
Under Article 285(3) of the Criminal Law and related judicial interpretations, providing programs or tools specifically designed to intrude into or unlawfully control computer information systems, or providing them to someone known to be engaged in such conduct, constitutes an offence once the statutory threshold for quantity or unlawful proceeds is met. If the circumstances are particularly serious, the baseline sentence rises to three to seven years’ imprisonment.
In this case, L had provided a particular software program to other people. The police took the view that it could bypass security measures and unlawfully control information systems. They placed L in criminal detention on suspicion of providing programs or tools for intrusion into or unlawful control of computer information systems.
In cases that depend heavily on technical examination and electronic evidence, the authorities often place considerable trust at the outset in an Electronic Data Examination Report or a Judicial Appraisal Opinion from a third party. Once a report concludes that “the program is capable of intrusion or unlawful control”, investigators often form a view of guilt quickly and proceed to request approval of arrest.
The countdown in criminal detention made the situation more dangerous still.
Under China’s Criminal Procedure Law, the maximum period in criminal detention for seeking and deciding on arrest approval is 37 days for major suspects in offences committed in multiple locations, offences committed repeatedly or offences committed in groups. With the examination report already characterising the program’s functions, day 37 was effectively the point at which continued detention would be locked in.
When lawyer Zhang Fan took the case, counsel faced a race against time in a technically opaque case. The task was clear. The defence had to move beyond accepting the technical report at face value and trace the underlying code, installer files and communications about the transaction to establish whether the program in the report and the program L delivered were actually the same.
II. The opening: The hashes in the examination report and the chat attachment did not match
In cybercrime defence, the “identity” of electronic evidence is vital to the facts of the case. Whether calculated using MD5 or SHA, a file’s hash is its digital fingerprint. Even the slightest alteration, replacement or corruption of the original file will fundamentally change its hash.
After taking the case, lawyer Zhang Fan went beyond reading the examination report’s conclusions. Counsel led the team in comparing the hashes using the original examination data submitted by the prosecution and the original files from the messages between the client and the customer about the transaction.
This review at byte level revealed a crucial gap in the facts presented in the case file.
The third-party examiner’s report listed the hash, or MD5 checksum, of the installer identified as capable of intrusion and unlawful control. It was entirely different from the hash of the installer file the client had actually sent to the customer in the transaction messages!
The discovery directly undermined the allegation.
The hash of the “hacking program” tested in the report did not match the hash of the program the client had actually delivered to the buyer.
This meant that the sample the authorities submitted for testing, and on which the incriminating finding rested, might well have been mixed up during collection, preservation or transfer. It could have been a derivative version that a third-party customer had modified or loaded with other malicious modules, or an entirely different version of the program.
How could the prosecution use a report based on the “wrong sample” to prove that L had “provided” a program with unlawful functions?
III. Looking beneath the surface: Challenging the case through version differences, the tool’s purpose and the provider’s knowledge
Having found the critical mismatch between the installer hashes, lawyer Zhang Fan moved from responding to the allegation to challenging it in detail on three fronts: whether the programs were the same, what kind of tool it was and what it was intended to be used for.
-
Document the differences between the samples and seek a fresh examination of the version actually delivered.
The defence team put the version notes, file sizes, creation times, timestamps from the messages in which the installers were sent, and receipt records for the two installers into a clear Electronic Data Sample Comparison Table.
Counsel told the authorities that the sample tested in the report and the file L had actually delivered differed materially in ways that could not be reconciled. Counsel formally applied in writing to exclude the disputed report as proof and to conduct a new examination of the functions of the version L actually delivered, in accordance with the law. This would establish whether the original version had the intrusion and control functions described in the report.
-
Examine the nature of the tool to determine whether it was “specifically designed” for unlawful use.
Under the relevant judicial interpretations, programs or tools giving rise to criminal liability must be “specifically designed for intrusion or unlawful control” or must themselves be capable of bypassing security measures and obtaining data without authorisation.
Drawing on the development documentation and version notes, counsel argued that many network tools are neutral technologies with dual uses, including lawful network maintenance, performance load testing and joint testing of interfaces. If the delivered version performed only routine automated interaction or testing and did not contain malicious code to bypass security protections or defeat system defences, its technical capabilities alone could not justify treating it as a “dedicated hacking tool”.
-
Examine knowledge by reconstructing the actual circumstances from the delivery instructions and messages.
Did the provider “know that another person would use the program to commit unlawful acts or crimes”?
The defence team obtained all the earlier communications between L and the customer, the agreed requirements and the delivery instructions. The evidence clearly showed that the customer had requested custom work for routine technical support and day-to-day monitoring of systems. L expressly included ordinary instructions for use on delivery. No communication in the case indicated that L knew of or knowingly allowed the customer to use the software to intrude unlawfully into other people’s servers. This rebutted the inference that L had a shared intent to commit an offence.
Lawyer Zhang Fan compiled the hash comparison, the application for a new examination, the analysis of whether the tool was specifically designed for unlawful use, and the arguments on knowledge into a detailed written legal opinion. Counsel submitted it urgently to the prosecutor handling the case before the procuratorate’s deadline for reviewing and deciding on approval of arrest.
IV. Breaking the deadlock: Bail on day 37 of criminal detention, before the deadline for arrest approval
Under China’s criminal procedure, day 37 of criminal detention is the statutory deadline by which the prosecutor handling the case must decide whether to “approve arrest” or “decline to approve arrest”.
In light of counsel’s precise table of the differing hashes, the explanation of the doubts about the source of the sample, and the application to re-examine the program’s key functions, the prosecutor carefully reassessed the evidentiary weight of the electronic records as a whole.
The authorities recognised substantial and reasonable doubt about the identity of the sample tested in the examination report on which the allegation relied. The facts remained unclear and the evidence insufficient as to whether the program had dedicated intrusion functions. Without a complete chain corroborating the key evidence, the statutory evidentiary standard for approving arrest was not met.
On day 37 of criminal detention, the procuratorate lawfully declined to approve arrest and the police granted L bail!
As L walked out of the detention centre, personal liberty had been regained just as the detention period was about to expire. This contest over code and hashes achieved a breakthrough against the odds before the door to arrest closed.
【Case notes】
In cybersecurity and computer crime cases, the prosecution’s evidence is often wrapped in layers of technical terms and expert findings. A detailed defence in such cases depends on three indispensable checks.
-
The “hash value”, or checksum, is the first means of testing the authenticity of electronic data.
In cases involving the provision of programs or tools, counsel should not accept the written conclusions of an examination report without checking them. The hashes (MD5 or SHA) of the program submitted for testing, the program seized, and the program the client actually delivered must be set out in one table and compared closely. A mismatch between digital fingerprints or versions can undermine the prosecution’s claim that the files are the same at the source of the evidence chain.
-
Scrutinise the legal line between “dedicated functions” and “neutral technology”.
Computer tools often have dual uses. Web crawlers, load testing tools, remote support software and port scanners are widely used for lawful day-to-day network maintenance and cybersecurity defence. Counsel must focus on concrete technical features, such as whether the program can “bypass or defeat security measures” or “gain control without authorisation”. This prevents the authorities from interpreting legitimate neutral tools too broadly as “tools exclusively for hackers”.
-
Distinguish “how often the tool was provided”, “version updates” and “the actual purpose of its use”.
When alleging a number of instances or an amount of unlawful proceeds, the prosecution can easily add together a customer’s “repeat downloads” or “patch updates” as separate instances of provision, or even count ordinary development fees in full as unlawful proceeds. Counsel must match the communications about each transaction, the delivery instructions, the circumstances of the customer’s request and the movement of funds. This can show that the client knew nothing of any downstream unlawful use and separate updates from independent criminal acts, reducing or even removing the basis for the amount and scale of the alleged offence.