North India · ranked #8 of 25

Haryana

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


Incidents
5
2015–2026
Confirmed
4
80% of the total
Candidates affected
9.4lakh
reported in 2 incidents
Exams voided
4
cancelled or re-held
Arrests recorded
190
across 3 incidents
Bodies involved
3
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
201510001
201710001
202120002
202601001

Bodies involved

  • HBSE State 2
  • HSSC State 2
  • Punjab & Haryana High Court State 1

The record

Every Haryana incident

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

Documented Indian examination leak incidents, sortable by column.
Outcome
4 Jul 2026HTET Level-3 / PGT (Haryana Teacher Eligibility Test)
HBSE · State
Haryana Alleged None
7 Aug 2021HSSC Police Constable (Male) recruitment exam
HSSC · State
Haryana
Kaithal
Confirmed167 Cancelled FIR
9 Jan 2021HSSC Gram Sachiv (Panchayat Secretary) exam
HSSC · State
Haryana
Hisar
Confirmed188L Cancelled FIR
16 Jul 2017HCS (Judicial Branch) Preliminary Examination 2017
P&H HC · State
Haryana Confirmed3 Cancelled FIR Probe
14 Nov 2015HTET Level-3 (Haryana Teacher Eligibility Test)
HBSE · State
Haryana
Jind
Confirmed51.4L Cancelled FIR

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.