Section 65 of the Information Technology Act, 2000 criminalizes knowingly or intentionally concealing, destroying, altering, or causing another to alter computer source code required to be maintained by law, prescribing imprisonment up to three years, a fine up to two lakh rupees, or both.
Statutory Definition and Meaning of Computer Source Code
The statutory explanation appended to Section 65 defines computer source code as the listing of programmes, computer commands, design and layout, and programme analysis of computer resources in any form. Source code represents the human-readable architectural blueprint of software systems, applications, operating routines, and firmware before compilation into executable binary machine code.
For the offense under Section 65 to be established, two fundamental conditions must co-exist: first, the offender must act knowingly or intentionally; second, the targeted source code must be required to be kept or maintained by law for the time being in force. This includes source codes preserved under statutory record-keeping regulations, intellectual property protections, banking software compliance norms, and corporate governance mandates.
Essential Ingredients and Criminal Liability
To sustain a conviction under Section 65 of the Information Technology Act, the prosecution must establish the following essential legal ingredients beyond reasonable doubt:
- Knowledge or Intention: The act of concealing, destroying, modifying, or altering the source listing must be deliberate and purposeful rather than accidental or the result of inadvertent system errors.
- Prohibited Actions: The perpetrator must have actively concealed, destroyed, altered, or intentionally caused another person to alter any computer source code.
- Statutory Requirement of Maintenance: The computer source code in question must be legally required to be maintained or preserved under an existing statute, rule, license condition, or regulatory framework.
- Target System Scope: The source code must pertain to a computer, computer programme, computer system, or computer network as defined under Section 2(1) of the Information Technology Act.
Digital Forensics and Evidentiary Requirements
Prosecuting or defending a charge under Section 65 hinges upon meticulous digital forensics. Digital investigators must preserve system integrity using write-blocking hardware, calculate cryptographic hash values (such as SHA-256), and analyze source repositories, commit histories, version control logs, and server access trails.
In corporate environments, establishing unauthorized source code alteration requires correlation of developer identities, access control lists, timestamp logs, and deployment pipelines. Modern organizations integrate cybersecurity threat detection mechanisms to flag anomalous modifications and ensure strict chain of custody for electronic records admissible under Section 65B of the Indian Evidence Act.
Judicial Interpretations and Key Case Law
The scope of Section 65 has been interpreted in significant Indian judicial decisions. In the landmark case of Syed Asifuddin and Others v. State of Andhra Pradesh (2005), the Andhra Pradesh High Court held that altering the electronic serial number (ESN) and internal code programmed into mobile handsets constitutes an offense under Section 65, confirming that embedded firmware and operating commands fall squarely within the definition of computer source code.
Similarly, courts have distinguished Section 65 from Section 43 (civil damages for unauthorized access) and Section 66 (general computer-related offenses and hacking). While Section 66 penalizes dishonestly or fraudulently causing damage to computer systems, Section 65 specifically safeguards the intellectual and structural integrity of source listings. Counsel advising tech enterprises often address these nuances across specialized cyber law practice areas to structure IP safeguards and employee compliance policies.
Penalties and Procedural Status
An offense under Section 65 is cognizable, bailable, and triable by a Magistrate of the First Class or Metropolitan Magistrate. The punishment extends to imprisonment for a term up to three years, or a fine up to two lakh rupees, or both. Understanding these statutory boundaries is essential for software enterprises, digital forensics examiners, and legal practitioners managing source code integrity.