West India · ranked #10 of 25

Maharashtra

5 examinations conducted in or for Maharashtra are recorded here as compromised between 2020 and 2026, of which 4 were officially confirmed.


Incidents
5
2020–2026
Confirmed
4
80% of the total
Candidates affected
8.7lakh
reported in 2 incidents
Exams voided
1
cancelled or re-held
Arrests recorded
35
across 4 incidents
Bodies involved
4
examination authorities

Incidents per year

Shown against the full 2004–2026 range so gaps are visible.

  • Confirmed
  • Alleged
  • Suspected
  • Denied

An empty year means nothing is recorded here for that year — not necessarily that nothing happened.

Show the numbers
YearConfirmedAllegedSuspectedDeniedTotal
202010001
202110001
202301001
202510001
202610001

Bodies involved

  • MSCE State 2
  • Maharashtra Revenue Dept / TCS-iON State 1
  • Maharashtra State Board (MSBSHSE) State 1
  • MHADA State 1

The record

Every Maharashtra incident

Showing 5 incidents. Select any row for the full record.

Documented Indian examination leak incidents, sortable by column.
Outcome
26 Feb 2026Class 12 Chemistry board examination
MSBSHSE · State
Maharashtra
Nagpur
Confirmed1 FIR Probe
23 Nov 2025Teacher Eligibility Test (TET)
MSCE · State
Maharashtra Confirmed18 FIR Probe
17 Aug 2023Talathi (village accountant) recruitment exam
MH Revenue · State
Maharashtra Alleged8.7L FIR
12 Dec 2021MHADA staff recruitment exam
MHADA · State
Maharashtra Confirmed3 Cancelled FIR
≈2020Teacher Eligibility Test (TET) 2020
MSCE · State
Maharashtra Confirmed137.8k FIR Probe

Open data · CC BY 4.0

This record is incomplete. Help finish it.

Every row here is one news report away from being verifiable — and there are leaks we have certainly missed, especially state recruitment exams before 2015 and cases reported only in regional-language press. The dataset is one CSV file. Adding to it takes a pull request.

1 Find a source. A named news report, court order, official notice or RTI reply. One incident, one primary link.
2 Add one row to exam_leaks.csv. Leave a field blank rather than guessing it.
3 Open a pull request. A preview build validates the row; a maintainer checks the source against the claim.
4 Not a coder? Open an issue with the link and we will transcribe it for you.