Mis-citation of Section 66B Not Fatal: Unauthorised Recording/Sharing of Official Calls Attracts Section 66 r/w Section 43(b) IT Act; Official Secrets Act Section 3 Inapplicable Absent “Prohibited Place”/State-Security Nexus

Case: PRAVIN SHYAMRAO SAMARTH v. STATE OF MAH., THR. PSO PS SADAR NAGPUR
Court: Bombay High Court (Nagpur Bench)
Coram: Urmila Joshi Phalke, J.
Date: 08-04-2026
Proceeding: Application to quash FIR (Crime No.305/2019) and Charge-sheet No.246/2020

1. Introduction

The applicant (Pravin Shyamrao Samarth), an employee of Maharashtra Metro Rail Corporation Limited, sought quashing of an FIR and charge-sheet registered for offences under Section 66B of the Information Technology Act, 2000 (“IT Act”) and Section 3(1)(c) of the Official Secrets Act, 1923 (“OSA”).

The prosecution case was that the applicant, whose duty included connecting conference calls for senior officials, recorded an internal call involving Metro officials and shared the recording and related communications with another employee (Vishwaranjan Beora) in a different department. Cyber forensic analysis indicated call logs and recordings on seized devices, and additional digital material suggesting internal data movement.

The principal legal issues were:

  • Whether the allegations and collected material make out an offence under the IT Act (especially when the FIR invoked Section 66B).
  • Whether the allegations amount to “spying” or otherwise attract Section 3(1)(c) of the OSA.
  • Whether the FIR/charge-sheet should be quashed applying the settled principles on quashing at the threshold.

2. Summary of the Judgment

The High Court partly allowed the quashing application:

  • Quashed the FIR/charge-sheet to the extent of the offence under Section 3(1)(c) of the Official Secrets Act, 1923, holding that the Metro office was not a “prohibited place” and the alleged act did not amount to “spying” or an act prejudicial to State safety/sovereignty.
  • Refused to quash the IT Act prosecution, holding that the allegations and cyber material prima facie disclose misconduct of the kind covered by Section 43(b) and therefore punishable under Section 66 IT Act; the Court further held that mere wrong mention of Section 66B is not, by itself, a ground to quash the FIR.

3. Analysis

3.1 Precedents Cited

(a) State of Haryana and others v. Bhajanlal and others (1992 Supp(1) Supreme Court Cases 335)

This decision supplied the governing framework for quashing. The Court reproduced the well-known Bhajanlal categories, focusing on whether, on an assumption that allegations are true, an offence is disclosed, and whether continuation would be an abuse of process.

In application, the Court treated the OSA charge as falling within the Bhajanlal-type situation where the allegations, even if accepted, do not constitute the offence; but treated the IT Act allegations as disclosing an offence, hence not fit for quash at the threshold.

(b) Gagan Harsh Sharma v. State of Maharashtra and others (2019) Cri.L.J. 1398

Although the applicant cited other authorities, the Court’s substantive IT Act reasoning drew from Gagan Harsh Sharma for two propositions:

  • Acts like unauthorised access/downloading/extraction of data fall within Section 43; when done “dishonestly” or “fraudulently” they attract criminality under Section 66.
  • Section 43 is broad enough to capture technology-enabled equivalents of traditional property/entrustment wrongs; the Court used this to frame the applicant’s conduct (recording and sharing official communications without authorisation) as falling within the Section 43/66 architecture.

(c) Applicant’s cited cases: treatment in the judgment

The applicant relied on:

However, the Court did not expressly analyse or apply these authorities in its reasoning; instead, it anchored the quashing test in Bhajanlal and the IT Act interpretive approach in Gagan Harsh Sharma. The implicit outcome is that whatever general quashing propositions were sought to be drawn from the applicant’s cases, the Court found a prima facie IT Act offence on the record, thereby foreclosing quash on that leg.

3.2 Legal Reasoning

(i) Why the IT Act prosecution was not quashed

The Court’s reasoning proceeds in three steps:

  • Factual foundation: The applicant’s assigned role was to connect conference calls. Cyber forensic material indicated (a) call recordings of conference communications between Metro officials, and (b) call logs/communications between the applicant and a co-employee in another department, supporting the allegation of recording plus onward sharing.
  • Normative backdrop (internal rules): The Court relied on Maharashtra Metro Rail Corporation Limited Rules, especially:
    • Rule 11 (Unauthorised communication of information) prohibiting direct/indirect communication of official documents/information to unauthorised persons.
    • Rule 34 (Integrity and confidentiality of data) requiring confidentiality and prohibiting transfer outside normal operations without approval.
    These rules were used not as the source of criminality, but as context to infer that the applicant’s act was not a benign/authorised discharge of duties, and to support a prima facie inference of dishonest intention in unauthorised extraction/communication.
  • Statutory fit (Section 43(b) → Section 66): The Court held the conduct fits Section 43(b)—unauthorised downloading/copying/extracting of data/information—when done without permission of the owner/in-charge of the system. When coupled with dishonest/fraudulent intent, it becomes punishable under Section 66.

Key doctrinal move: The Court treated an internal telecommunication recording and its electronic retention/transfer as “data/information” extraction/handling in a “computer system/network/resource” ecosystem, thereby placing it within the Section 43/66 framework rather than limiting the analysis to purely disciplinary misconduct.

(ii) “Wrong section” (Section 66B) and quashing

A central holding is that mere application of an incorrect penal section (here, invocation of Section 66B) is not by itself a ground to quash the FIR if the allegations disclose commission of an offence under the correct provision (here, Section 66 read with Section 43(b)).

This is significant because Section 66B targets dishonestly receiving/retaining a stolen computer resource or communication device, whereas the Court found the factual gravamen to be unauthorised copying/extraction/recording and sharing (Section 43(b) read with Section 66). The Court thus preserved the prosecution on the IT Act limb, leaving issues of exact charge-framing to subsequent stages.

Note on the operative order: While the reasoning emphasises Section 66 (and says 66B was wrongly applied), the final order states that prosecution would continue “as far as offence under Sections 66 and 66(B) of the Information Technology Act is concerned.” Read harmoniously with the reasoning, the order reflects refusal to quash the IT Act prosecution at large, even if the most accurate fit is Section 66 r/w 43(b), with the precise section to be addressed in trial/cognizance/charge.

(iii) Why the Official Secrets Act charge was quashed

For Section 3(1)(c) OSA, the Court held the ingredients were not satisfied:

  • No “prohibited place” nexus: Relying on the statutory definition context (Section 2(8) OSA), the Court found the Metro office/control room was not shown to be a “prohibited place”.
  • No “spying”/State-security character: Section 3 is aimed at conduct prejudicial to “safety or interests of the State” or likely to affect sovereignty/integrity/security/friendly relations. Recording an internal organisational call (even if wrongful) was held not to be “spying” and not shown to have the required State-security prejudice.

Accordingly, applying the quashing test, the OSA invocation was characterised as misconceived and was quashed to prevent continuation of a legally untenable charge.

3.3 Impact

(a) On IT Act prosecutions for workplace data/communication misuse

The judgment strengthens the prosecutorial path of treating unauthorised recording/retention/transfer of internal electronic communications as potential Section 43(b) + Section 66 conduct, especially where:

  • the accused had legitimate access for limited purposes (e.g., “connect the call”), but exceeded authority by copying/recording;
  • the act is supported by forensic recovery (call logs, recordings, device extractions); and
  • organisational confidentiality rules help contextualise “permission” and “dishonesty”.

(b) On charging errors and quashing

A practical precedent emerges: incorrect section-labelling in the FIR is not determinative if the core allegations disclose an offence under another provision. This reduces the likelihood of threshold quashing solely on “wrong section” arguments, shifting focus to whether facts disclose any cognizable offence.

(c) On misuse/overreach of the Official Secrets Act

By quashing the OSA charge, the Court signals that employment-related confidentiality breaches should not be automatically escalated into “spying” absent a clear statutory fit—particularly lacking “prohibited place” linkage and demonstrable prejudice to State security/sovereignty. This may serve as a restraint against routine invocation of the OSA in organisational information disputes.

4. Complex Concepts Simplified

  • Quashing an FIR/charge-sheet: A High Court’s power to stop criminal proceedings at an early stage when, even if allegations are assumed true, no offence is made out, or continuation would be an abuse of process.
  • Prima facie case: A threshold showing that the basic ingredients of an offence appear from the allegations/material—without deciding guilt.
  • Section 43(b) IT Act: Civil-penalty provision describing unauthorised acts like downloading/copying/extracting data from a computer/system/network; when done dishonestly/fraudulently, it becomes criminal via Section 66.
  • Section 66 IT Act: Criminalises dishonest or fraudulent commission of acts listed in Section 43 (unauthorised access/copying/data interference, etc.).
  • Section 66B IT Act: Targets receiving/retaining a “stolen” computer resource/device with knowledge/reason to believe it is stolen—conceptually closer to “receiving stolen property” than to unauthorised copying.
  • Official Secrets Act “spying” (Section 3): Requires a State-security/safety prejudice element; it is not a general “confidentiality law” for all institutions.
  • Forensic “imaging”: Creating a verified bit-by-bit copy of a storage device so analysis occurs on the copy, preserving original evidence integrity.

5. Conclusion

The Bombay High Court drew a clear line between (i) unauthorised electronic copying/recording and dissemination within an organisation—which can sustain an IT Act prosecution under Section 66 read with Section 43(b)—and (ii) the far more serious “spying” offence under the Official Secrets Act, which requires a demonstrable State-security statutory fit and cannot be invoked merely because information was internal or sensitive.

Equally significant is the Court’s refusal to quash merely because the FIR cited Section 66B: the controlling inquiry is whether the allegations, on their face, disclose commission of an offence under law. This approach emphasises substance over form in threshold quashing and is likely to influence future challenges where charging sections are imperfectly selected at the FIR stage.