Framing of Charges in Cyber Cases
"The charge is the foundation — if it's weak, the building collapses"
Charge framing is the critical gateway to trial. A well-drafted charge defines the battlefield; a defective charge can result in acquittal. Learn to draft bulletproof charges and challenge weak ones.
Charge Framing — Overview
Definition: The formal accusation read to the accused specifying the offence(s) they allegedly committed, based on material collected during investigation.
Purpose: To inform accused precisely what they're charged with, enabling preparation of defence.
Stage: After charge sheet is filed, before trial begins. Sessions cases under BNSS S.230; Magistrate cases under S.251.
Section Selection: IT Act has overlapping sections (S.66, 66C, 66D, 43). Wrong section = vulnerable charge.
Technical Elements: Charges must specify technical acts — "unauthorized access," "identity theft," not vague "hacking."
Combined Charges: Cyber crimes often need IT Act + BNS combination. Missing either weakens prosecution.
Jurisdictional Issues: Charge must align with court's territorial jurisdiction for the cyber offence.
BNSS Section 230 — Charge Framing Procedure
1. Offence Identification: Name of the offence (e.g., "identity theft under S.66C IT Act")
2. Section & Act: Specific section number and the statute
3. Time & Place: When and where the offence was committed
4. Manner of Commission: How the accused allegedly committed the offence
5. Victim/Target: Against whom/what the offence was committed
6. Role of Accused: Specific role if multiple accused (principal, abettor, conspirator)
CHARGE
I, [Judge Name], Judge, Special Court under IT Act, [City], hereby charge you, Accused Name (A1), as follows:
FIRST: That you, on or about [Date], at [Place], within the jurisdiction of this Court, did fraudulently use the electronic signature and password of the complainant [Victim Name] to gain unauthorized access to their bank account maintained with [Bank Name], and thereby committed an offence punishable under Section 66C of the Information Technology Act, 2000.
SECOND: That you, on the same date and place, did by means of a computer resource, cheat the said complainant by personating as a representative of [Bank/Organization] and dishonestly induced delivery of Rs. [Amount], and thereby committed an offence punishable under Section 66D of the Information Technology Act, 2000 read with Section 318 of Bharatiya Nyaya Sanhita, 2023.
THIRD: That you did dishonestly receive and retain stolen property knowing the same to be stolen, punishable under Section 317 BNS.
And I hereby direct that you be tried by this Court on the said charges.
Prima Facie Test in Cyber Cases
Definition: "At first appearance" — evidence that, if unrebutted, would be sufficient to prove the case.
Standard: Not proof beyond reasonable doubt, but "ground for presuming" accused committed offence.
Judge's Role: Sift evidence, not weigh it. Court acts as a "post office" — if there's a letter to deliver, deliver it.
| Prima Facie Element | Cyber Case Application | What Court Looks For |
|---|---|---|
| Actus Reus | Unauthorized access, data theft, impersonation | Evidence of the technical act (logs, screenshots, CDR) |
| Mens Rea | Dishonest intention, knowledge of wrongdoing | Pattern of conduct, multiple transactions, cover-up attempts |
| Identity | Accused is the person who committed the act | IP correlation, device seizure, confession, CDR matching |
| Jurisdiction | Offence within court's territorial jurisdiction | Victim location, server location, consequence location |
Challenge Identity: IP address alone insufficient without device seizure — argue prima facie not made out.
Challenge Technical Elements: Hash mismatch, broken chain of custody — evidence unreliable.
Challenge Jurisdiction: If acts committed entirely in another jurisdiction, seek transfer.
Challenge Section Selection: Wrong section applied — seek modification of charge.
IT Act + BNS Charge Combinations
IT Act sections often have lower punishment than BNS equivalents. Smart prosecution uses both:
• IT Act provides specific cyber elements (electronic signature, computer resource)
• BNS provides higher punishment and covers traditional offence elements
• Combined charging ensures no gaps if one set of sections fails
| Cyber Crime Type | IT Act Section | BNS Section | Combined Strategy |
|---|---|---|---|
| Phishing/Vishing | S.66C (identity theft) S.66D (personation) | S.318 (cheating) S.319 (cheating by personation) | IT Act for technical act, BNS for dishonest inducement |
| Ransomware | S.66 (hacking) S.66F (if critical infra) | S.308 (extortion) S.351 (criminal intimidation) | IT Act for access, BNS for threat/extortion |
| Data Theft | S.43 (civil) S.66 (criminal) | S.303 (theft) S.316 (criminal breach of trust) | IT Act for unauthorized access, BNS for theft/breach |
| Online Defamation | S.66A struck down | S.356 (defamation) | BNS only — IT Act has no live defamation section |
| Obscene Content | S.67 (publishing) S.67A (sexually explicit) | S.294 (obscene acts) S.296 (obscene publication) | IT Act for electronic transmission, BNS for content |
| Cyber Stalking | S.66A struck down | S.78 (stalking) S.351 (intimidation) | BNS stalking + intimidation provisions |
Facts: Accused called victim, posed as bank executive, obtained OTP, transferred ₹2 lakhs.
Charges:
• S.66C IT Act: Used victim's password/OTP (unique identification)
• S.66D IT Act: Cheated by personating as bank official via phone
• S.318 BNS: Cheated by deceiving and inducing delivery of money
• S.319 BNS: Cheated by pretending to be different person (bank official)
• S.61(2) BNS: Criminal conspiracy if multiple accused acted together
Discharge Applications — S.227 BNSS
1. No Prima Facie Case: Evidence insufficient even for presumption of guilt
2. Technical Evidence Defective: S.63 certificate missing, hash mismatch, chain broken
3. Identity Not Established: IP alone without device correlation
4. Wrong Section: Alleged acts don't constitute the charged offence
5. Jurisdictional Defect: Court has no territorial jurisdiction
6. Intermediary Safe Harbor: Accused is intermediary protected under S.79 IT Act
- Analyze charge sheet for technical evidence deficiencies
- Check S.63 BSA certificate — is it complete and from proper person?
- Verify hash values — were they calculated at seizure and verified at analysis?
- Examine identity evidence — is IP correlated with accused through device?
- Review section applicability — do facts disclose alleged offence?
- Check jurisdiction — where did cause of action arise?
- Consider intermediary defence — does S.79 apply?
- Draft application with specific grounds and supporting case law
Case Studies in Charge Framing
Charges Framed: S.67 IT Act (publishing obscene content), S.292 IPC (sale of obscene material)
Defence: No personal knowledge, intermediary platform, S.79 safe harbor
Outcome: Delhi HC held charges could not sustain against CEO personally without evidence of actual knowledge. Platform intermediary defence recognized.
Lesson: Charge framing against intermediary executives requires evidence of personal involvement or knowledge.
Charge Strategy:
• A1: S.66C, 66D IT Act + S.318, 61(2) BNS (conspiracy)
• A2: S.66D IT Act + S.319 BNS (personation) + S.61(2) BNS
• A3: S.317 BNS (receiving stolen property) + S.61(2) BNS
• A4: S.66 IT Act (hacking tools) + S.61(2) BNS
Lesson: Differentiate charges based on each accused's specific role. Common conspiracy charge binds all.
☑️ Layer the charges: Primary offence + related offences + conspiracy
☑️ Specify technical acts: Don't just say "hacking" — describe the unauthorized access
☑️ Link evidence to elements: Each charge element should map to specific evidence
☑️ Anticipate defence: Address likely technical challenges in charge narrative
🎯 Key Takeaways — Part 5.1
- Charge framing under BNSS S.230 is gateway to trial — defective charge = vulnerable prosecution
- Prima facie test: "Ground for presuming" — sift evidence, don't weigh it
- Valid charge needs: offence name, section, time, place, manner, victim, accused role
- Cyber cases need IT Act + BNS combination for complete coverage and higher punishment
- S.66C (identity theft) + S.66D (personation) + S.318/319 BNS is standard phishing combo
- Discharge under S.227 if: no prima facie, technical evidence defective, identity not established
- Intermediary safe harbor (S.79) is valid discharge ground — Bazee.com case
- Multiple accused need differentiated charges based on specific roles + common conspiracy
- Technical elements must be specified — "unauthorized access to computer resource" not just "hacking"
- Challenge wrong section selection — facts must disclose the specific offence charged