Source code theft is the act of stealing proprietary software code — either by a dishonest employee, a contractor, or an external hacker — and claiming or using it without authorization. In India, it is a criminal offense punishable under the Information Technology Act, 2000 (Sections 43, 65, 66, 66B) and Section 63 of the Copyright Act, 1957. If your source code has been stolen, you must act fast: preserve evidence, file an FIR, and engage a cyber forensics expert to trace the breach.
What Is Source Code?
Source code is a set of instructions written in a programming language that directs a device — computer or smartphone — to perform a specific function. For software companies, source code is the core intellectual property: built over years of engineering effort, it powers financial systems, communication platforms, and business-critical applications.
When a competitor steals and deploys your source code, the damage goes far beyond financial loss. It undermines years of R&D, exposes business logic, and strips the company of its competitive edge. Protecting source code is not optional — it is a business survival requirement.
What Is Source Code Theft?
Source code theft occurs when someone gains unauthorized access to a company’s proprietary codebase and copies, modifies, or distributes it without permission. Attackers may edit the stolen code to disguise its origins, then deploy it as their own product or sell it to a competitor.
Once a hacker gains illegal access to the source code, they also gain insight into the software’s architecture — creating further risk of data exfiltration, backdoor installation, and long-term system compromise. This is also closely related to software piracy.
How Is Source Code Stolen?
Source code theft typically happens through one of three routes:
- Insider theft: A current or former employee — developer, manager, or contractor — who has legitimate access copies the code and sells or transfers it to a third party.
- External hacking: Attackers exploit vulnerabilities in version control systems (GitHub, Bitbucket), CI/CD pipelines, or developer workstations to access and exfiltrate the codebase.
- Vendor or partner breach: Third-party vendors with access to your development environment leak or steal code, knowingly or through their own security failures.
Insider theft is the most common. Employees leaving for a competitor often take code samples, libraries, or full repositories with them — sometimes without realizing it constitutes a criminal act.
What Is the Legal Punishment for Source Code Theft in India?
Source code theft is prosecutable under multiple Indian laws. Here is a breakdown of the applicable provisions:
Information Technology Act, 2000
- Section 43 — Damage to computer systems: Allows claims up to Rs. 5 crore before an Adjudicating Officer (the IT Secretary of each state). Claims above Rs. 5 crore require filing before a Competent Court.
- Section 65 — Altering computer source documents: Imprisonment of up to 3 years, or a fine of up to Rs. 2 lakh, or both.
- Section 66 — Computer-related offenses: If committed dishonestly or fraudulently, imprisonment of up to 3 years, or a fine of up to Rs. 5 lakh, or both.
- Section 66B — Receiving stolen computer resources: If a person knowingly retains stolen source code, imprisonment of up to 3 years, or a fine of Rs. 1 lakh, or both.
Copyright Act, 1957
- Section 63 — Copyright infringement: Intentional infringement of software copyright carries imprisonment from 6 months to 3 years, plus a fine of Rs. 50,000 to Rs. 2 lakh.
Electronic evidence submitted in court under these sections must comply with Section 65B of the Indian Evidence Act for admissibility.
How to Investigate a Source Code Theft Case
A source code theft investigation requires forensic analysis of developer machines, version control access logs, email communications, and data transfer records. The investigation process typically involves:
- Preserve evidence immediately. Do not wipe or reset any system. Take forensic images of developer workstations, servers, and laptops involved.
- Audit version control logs. Check Git commit history, branch access logs, and clone/download events for unauthorized activity.
- Review access controls. Identify who had access to the repository at the time of the breach and map activity against timelines.
- Analyze file transfer records. Check USB logs, cloud sync activity (Dropbox, Google Drive, OneDrive), and email attachments for outbound transfers.
- Engage a source code investigation expert. Specialist tools can detect code similarity across stolen derivatives and trace digital fingerprints back to the original repository.
- File an FIR. Report to the cyber crime investigation unit with all digital evidence preserved and documented.
How to Prevent Source Code Theft
Prevention is far cheaper than investigation. Apply these controls before a breach happens:
- Register copyright for your source code, software, and documentation — this establishes legal ownership and strengthens your case in court.
- Implement role-based access control (RBAC) in your version control system. No developer should have access to code outside their immediate project scope.
- Use signed commits and audit trails in your Git repositories.
- Have a Non-Disclosure Agreement (NDA) signed by every employee, contractor, and vendor with access to the codebase.
- Have a License Agreement in place with all clients who receive any portion of your source code.
- Train your development team on email security and social engineering attacks — most data exfiltration starts with a phishing email.
- Monitor outbound data transfers, especially large file uploads to cloud services or external USB devices.
If you suspect your source code has already been stolen or are concerned about ongoing corporate espionage, contact Anuraag Singh for an urgent forensic investigation.
