Section 65 IT Act: Tampering with Computer Source Documents

Chapter XI opens not with hacking but with a quieter wrong: destroying the recipe. Source code is the human-readable text from which software is built, and where the law requires that code to be kept, concealing, destroying or altering it defeats regulators, auditors and courts at one stroke. Section 65 makes that tampering an offence. This note takes the section apart element by element: the acts, the meaning of source code, the required-by-law condition, the mens rea, the punishment and procedure, the comparisons with Sections 43(j) and 66, and the case that stretched the section to mobile handsets, Syed Asifuddin.

1. Burning the Recipe Book

A restaurant chain can lose a dish two ways: a rival can steal tonight's plate, or someone can burn the recipe book itself. The plate is data; the recipe is source code, the instructions from which every plate is made. And where a food regulator requires the recipe to stay on file, burning, hiding or quietly rewriting it is not just the chain's loss but an offence against the system of inspection. Section 65 punishes the recipe burners of computing.

2. The Section and Its Elements

Figure 1: The five elements of Section 65

Figure 2: The prohibited acts

• Knowingly concealing. Hiding the code or putting it beyond reach, for example moving the only copy off the audited servers before an inspection. Concealment needs no destruction; making the code unavailable is enough.
• Destroying. Wiping, deleting or rendering the code unusable, whether by deletion, corruption or physical destruction of the only media.
• Altering. Changing the code in any respect, from rewriting a module to a one-line change that disables a logging function. The materiality of the change goes to sentence, not to guilt.
• Causing another to do so. The section expressly reaches the person who procures the act, so the manager who directs a programmer to delete the code is a principal offender, not merely an abettor.

3. Computer Source Code: Meaning

Figure 3: The four components in the Explanation

• Wider than programmers' usage. To a developer, source code is program text. The Explanation goes further: the listing of programmes, computer commands, design and layout, and programme analysis of the computer resource, in any form. Design documents and analyses are covered, and 'in any form' includes printouts.
• Used for a computer resource. The code must be used for a computer, programme, system or network; it is protected because a working resource depends on it.
• The required-by-law condition. The offence arises only when the source code is required to be kept or maintained by law for the time being in force: company record and audit requirements, licence conditions, sectoral regulations or court orders. Tampering with purely private code that no law requires to be kept is not a Section 65 offence, though it may be a Section 43(j) contravention or, with dishonesty, a Section 66 offence.

4. Mens Rea, Punishment and Procedure

• Mens rea under Section 65. The acts must be done knowingly or intentionally. Accidental deletion, a botched update or negligent overwriting is outside the section; the prosecution must prove the accused knew what he was doing or meant to do it.
• Punishment. Imprisonment up to three years, or fine up to ₹2 lakh, or both. The fine ceiling is the lowest in Chapter XI, a sign of the section's early drafting.
• Classification. Punishable with three years, so cognizable and bailable under Section 77B; compoundable by a court under Section 77A, subject to its exceptions; investigation by an officer not below Inspector (s.78)
• Company liability. Where a company tampers, Section 85 reaches the persons in charge of its business and consenting officers.

5. Section 65 vs Sections 43(j) and 66

Figure 4: The three source code provisions compared

• Against Section 43(j). Clause (j) is the civil cousin: stealing, concealing, destroying or altering source code with intent to cause damage, compensated before the adjudicating officer, and with no required-by-law condition. Section 65 is the crime, and it is narrower in object (code required to be kept by law) but wider in mens rea (knowledge or intention, not necessarily intent to damage)
• Against Section 66. Section 66 punishes any Section 43 act done dishonestly or fraudulently, so dishonest source code theft travels under s.66 read with s.43(j). Section 65 needs no dishonesty at all; a developer who deletes legally mandated code out of spite or to defeat an audit is guilty even if he sought no wrongful gain.
• Charging practice. The same episode can attract both: altering mandated code to siphon value is a s.65 offence (the alteration) and a s.66 offence (the dishonest s.43 act), and the ingredients differ enough for both to stand.

6. Syed Asifuddin and Software Tampering

• Modern applications. Firmware manipulation in metering and emissions devices, deletion of audit-trail code required under company law, tampering with source code escrowed under licence conditions, and alteration of tally or billing software required to be maintained under tax law.
• The proof problem. Prosecutions turn on version histories, repository logs and forensic comparison of code images, proved as electronic records under Section 63 BSA with the Examiner of Electronic Evidence (s.79A) where needed.

7. Quick Revision and Memory Aids

• 'Burning the recipe book'. What Section 65 punishes.
• 'Conceal, destroy, alter, or cause it'. The four acts.
• 'Listing, commands, design, analysis'. The Explanation's components.
• 'Only code the law makes you keep'. The limiting condition.
• 'Three years or two lakh'. The punishment.
• 'Asifuddin: a phone is a computer'. The leading case.

8. Frequently Asked Questions

What are the ingredients of the offence under Section 65?

Knowingly or intentionally concealing, destroying or altering, or causing another to conceal, destroy or alter, computer source code used for a computer resource, when that source code is required to be kept or maintained by law. Punishment is imprisonment up to three years, or fine up to ₹2 lakh, or both.

How is Section 65 different from Section 43(j)?

Section 43(j) is a civil contravention covering source code generally, requiring an intention to cause damage and leading to compensation. Section 65 is an offence, applies only to source code required by law to be kept, requires knowledge or intention but no intent to damage, and leads to prosecution and punishment.

9. Related Topics

• Topic 53: Section 43. Clause (j) and the civil track.
• Topic 58: Section 66. The general computer-related offence.