North India · ranked #11 of 25

Punjab

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


Incidents
4
2020–2026
Confirmed
2
50% of the total
Candidates affected
1.2lakh
reported in 3 incidents
Exams voided
2
cancelled or re-held
Arrests recorded
12
across 2 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
202010001
202210001
202500101
202600011

Bodies involved

  • BFUHS State 2
  • PPSC State 1
  • PSSSB State 1

The record

Every Punjab incident

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

Documented Indian examination leak incidents, sortable by column.
Outcome
19 Jul 2026Pharmacist Officer recruitment exam
BFUHS · State
Punjab
Faridkot/Kotkapura/Ferozepur
Denied77k FIR
21 Dec 2025Group-B recruitment exam (408 posts incl Naib Tehsildar, Treasury Officers, Senior Assistant)
PSSSB · State
Punjab
Bathinda highlighted
Suspected1L Probe
22 May 2022Naib Tehsildar recruitment test (78 posts)
PPSC · State
Punjab
Patiala; centres statewide
Confirmed5 FIR Cancelled
11 Oct 2020Medical Officer (Dental) recruitment test
BFUHS · State
Punjab
leak traced to Goindwal Sahib, Tarn Taran
Confirmed11k Cancelled Retest

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.