In modern litigation, electronic records—ranging from WhatsApp chats, emails, and call detail records (CDRs) to CCTV footage and social media posts—frequently form the core of the prosecution or plaintiff’s case. However, unlike physical documents, digital files are inherently malleable, vulnerable to unauthorized modification, and easily fabricated.

Asserting that electronic evidence is “tainted” or “tampered with” requires a systematic technical and legal attack at the trial court stage.

1. Grounds to Prove Electronic Evidence is Tainted:

To persuade a trial court that digital evidence presented by the opposing party is compromised, defence counsel or opposing litigants must target specific technical and procedural failures:

A. Non-Compliance with Mandatory Certification (Section 65B Evidence Act / Section 63 BSA):

Under Indian law (Anvar P.V. v. P.K. Basheer and Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal), secondary electronic evidence (e.g., printouts, hard drives containing copies, CD-ROMs) is inadmissible without a mandatory statutory certificate under Section 65B of the Indian Evidence Act, 1872 (now Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 – BSA).

• Defective Certification:A certificate issued by an unauthorized person, one lacking contemporaneous details, or one signed long after the secondary device was created raises serious doubts about authenticity.

 

B. Broken Chain of Custody & Lack of Hash Value Verification:

Every digital file possesses a unique cryptographic fingerprint known as a Hash Value (e.g., SHA-256 or MD5).

• Hash Discrepancy:If the hash value of the seized original device does not match the hash value of the electronic file produced in court, the file has been altered or corrupted.
• Unsealed Seizure:Failure of investigative agencies or parties to seal digital devices immediately upon seizure creates a direct window for tampering or inserting retrospective files.

 

C. Absence of System Logs and Metadata Manipulation:

Every file carries metadata—hidden records showing creation dates, modification timestamps, author credentials, and device details.

• Altered Timestamps:Exploit discrepancies between the content timestamp (what the image/text shows) and the file’s file-system metadata (when the file was actually written to disk).
• Missing Server Logs:In chat logs or emails, presenting isolated screenshots without corresponding server logs or original export files (.pst, .eml, or raw JSON data) indicates potential selective editing or spoofing.

 

D. Fabricated Screenshots and Deepfakes:

• Plain printouts of chat transcripts or static screenshots can easily be generated using online fake-chat generators or basic image editing tools. Without raw log files, live device inspection, or telecom provider validation, standalone screenshots carry low evidentiary weight when contested.

 

2. Strategic Legal Remedies & Procedural Steps to Prove Tainting:

Uncovering tainted evidence requires leveraging procedural rights before the Trial Court to compel production, force expert evaluation, and cross-examine technical witnesses.

Remedy 1: Application for Production of Original Source Device:

• Mechanism:File an application under Section 91 CrPC (Section 94 BNSS) in criminal matters or Order 11 of the CPC in civil disputes.
• Objective:Compel the producing party to submit the actual primary device (the mobile phone, server, or DVR drive) to inspect whether the original file exists and matches the version produced in court.

 

Remedy 2: Requisition Forensic Examination (Section 45A Evidence Act / Section 39 BSA):

• Mechanism:Move an application under Section 45A of the Indian Evidence Act (Section 39 BSA) requesting the court to send the electronic record to a government-notified Examiner of Electronic Evidence (Central Forensic Science Laboratory / Forensic Science Laboratory).
• Objective:Obtain an independent forensic audit report analyzing:
  • Bit-stream images of the device.
  • Integrity of Hash values.
  • Deleted file recovery or evidence of anti-forensic software (e.g., wipe tools, date-spoofing utilities).

 

Remedy 3: Summoning Nodal Officers & Network Logs:

• Mechanism:Exercise rights under Section 233 CrPC (Section 256 BNSS) or Order 16 CPC to summon the Nodal Officer / System Administrator of telecom service providers or web platforms.
• Objective:Compare the opponent’s private electronic records against official Call Detail Records (CDRs), IPDRs (Internet Protocol Detail Records), and tower location logs retained by service providers. Discrepancies conclusively prove fabrication.

 

Remedy 4: Pinpoint Cross-Examination of Technical and Seizure Witnesses:

During trial, use targeted cross-examination questions aimed at the Investigating Officer, computer operator, or private party who extracted the data:

1. Did you record the MD5/SHA-256 Hash Value at the exact time of seizure?
2. Was the hard drive/mobile phone kept in a Faraday bag to block remote modification or wipe commands?
3. Did you personally generate the Section 65B/63 certificate, and were you in lawful control of the server when the record was created?
4. Can you confirm that no third-party software was utilized during extraction that could alter file headers?

 

Technical Checklist for Trial Lawyers:

Stage	Key Verification Point	Red Flag / Evidence of Tainting
Seizure & Extraction	Chain of Custody & Hash Values	No hash value mentioned in seizure memo; device unsealed during transit.
Certification	Section 65B / Section 63 BSA Compliance	Certificate missing, signed by an unqualified individual, or issued retroactively without system access.
Forensic Audit	Metadata & System Logs	Created date is after the alleged event date; missing EXIF data on photos; mismatched header lines in emails.
Corroboration	Third-Party Telecom / ISP Data	Private chat history does not match official CDR / IPDR logs provided by the ISP.

 

Conclusion:

Trial Courts cannot accept digital evidence at face value merely because it is printed or loaded onto a flash drive. Electronic records are only as reliable as the security protocols followed during their creation, extraction, and custody. By challenging certification early, demanding raw source files, securing forensic analysis under Section 45A / Section 39 BSA, and executing rigorous technical cross-examination, litigants can effectively demonstrate that tainted electronic evidence is inadmissible and legally void.

 

Disclaimer: This summary is for informational purposes and does not constitute formal legal advice. The interpretation of these grounds is highly dependent on judicial precedent and the specific facts of your case. Always consult with a qualified advocate regarding the strategy for your petition.