42/100

Emerging evidence

ProblemPublished recordEducationProblem Space

Sleeve checks and no smartglasses: South Korea races to protect all-important university exams against AI

Truvace record
TRV-2026-3013raw data (JSON)
Version
v1Published
First published
Evidence type
News report
Sources
1 sourceJournalism
sha256
deeabf30b23f…check it

The integrity of South Korea’s career-defining university entrance exam has been thrown into doubt after the top scorer in a recent professional exam admitted using a concealed camera and AI to cheat. On Thursday, more than half a million people, mostly school students, are due to sit the exam, known as the suneung, at 1,312 centres across the country. The exam runs for a gruelling eight hours over a single day and determines which university a candidate can attend and, in turn, their future prospects. The count…

The problem

South Korea's top scorer on this year's tax accountancy exam, who missed one question out of 160, admitted cheating by photographing questions with a hidden camera and reading AI-generated answers, casting doubt on the suneung ahead of its sitting by over half a million people.

What this doesn’t fix

Authorities said that newer smart glasses variants could not be screened out perfectly, and radio-frequency detection was judged unworkable this year, so checks rely on visual inspection.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-18

Cite this record

v1

Truvace Impact Record TRV-2026-3013, v1: “Sleeve checks and no smartglasses: South Korea races to protect all-important university exams against AI.” Truvace, 2026-11-18. /record/TRV-2026-3013 (accessed on the day you copy it). sha256 deeabf30b23fe07d…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1deeabf30b23f…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3013 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.