The year in exam integrity

2012

8 examinations were publicly reported as compromised in 2012, across 4 jurisdictions.


Incidents
8
reported in 2012
Confirmed
8
100% of the year
Candidates affected
286
reported in 1 incidents
Exams voided
0
cancelled or re-held
Arrests recorded
17
across 2 incidents
Central vs state
1 / 7
conducting bodies

Where the 2012 incidents were recorded

  • Confirmed
  • Alleged
  • Suspected
  • Denied

Incidents spanning two states are counted in both.

Show the numbers
PlaceConfirmedAllegedSuspectedDeniedTotal
Madhya Pradesh50005
Delhi10001
Jammu & Kashmir10001
Karnataka10001

The record

Every incident recorded in 2012

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

Documented Indian examination leak incidents, sortable by column.
Outcome
30 Sep 2012Vyapam Police Constable Recruitment Examination 2012
Vyapam · State
Madhya Pradesh Confirmed11 FIR Probe
≈Jun 2012Jammu & Kashmir Common Entrance Test (JKCET) 2012 - medical (MBBS/BDS)
BOPEE · State
Jammu & Kashmir Confirmed11 FIR Probe
≈Jun 2012MP Pre-Medical Test (PMT) 2012
Vyapam · State
Madhya Pradesh Confirmed286 FIR Probe
≈Mar 2012Karnataka Second PU (Class 12) Board Examination 2012
KA PUE · State
Karnataka Confirmed10 FIR Probe
≈Jan 2012AIIMS Post-Graduate (MD/MS) Entrance Examination 2012
AIIMS · Central
Delhi Confirmed7 FIR
≈2012MP Food Inspector Selection Test 2012
Vyapam · State
Madhya Pradesh Confirmed FIR Probe
≈2012MP Pre-PG (Post-Graduate Medical) Test 2012
Vyapam · State
Madhya Pradesh Confirmed FIR Probe
≈2012MP Transport Constable Recruitment Test 2012
Vyapam · State
Madhya Pradesh Confirmed 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.