Key Summary
- The Ministry of Science and ICT (MSIT) and KISA jointly released the results of the public-private investigation into the TVING breach on the 3rd.
- The initially reported 39.54 million leaked accounts include many duplicates; the precise scope will be confirmed by the Personal Information Protection Commission (PIPC) investigation.
- During the first attack attempt, a CPU 100% spike alarm was triggered, but MSIT Director-General for Information Protection Network Policy Lim Jeong-gyu acknowledged at the briefing that it was classified at the time as a routine system error rather than a cyberattack, and no follow-up security measures were taken.
Analysis
Table of Contents
The number that first made headlines for the TVING breach was 39.54 million. Not all of these were unique accounts. According to the joint public-private investigation results released on the 3rd by MSIT and KISA, the reported 39.54 million figure includes many duplicates. The precise scope of the breach will be determined through the PIPC’s investigation.
While the joint investigation team officially confirmed this fact, it also drew a different line from the “inflated figures” controversy that erupted immediately after the announcement. At the briefing, MSIT’s Lim Jeong-gyu answered, “The initially reported figure includes duplicates, and the actual scope of damage will be confirmed through the PIPC investigation.” KISA’s spokesperson, Park Yong-gyu, Head of the Digital Threat Response Division, added at the same podium, “The exact number will come out once the investigation is concluded.”
What I found most significant in that room was not simply the fact that the numbers were inflated. The real takeaway is that the presenters and questioners started over from the shared premise that “the exact scope is still unknown” while sitting in the same room. When a data breach occurs, the pattern repeats itself: the first day’s figure draws the loudest headlines, followed by corrections and clarifications the next day. The TVING breach has followed the same pattern.
However, there was a heavier question beyond the numbers. The questions concentrated in the Q&A were: “Why was the initial alarm ignored?” According to the investigation team, a CPU 100% spike alarm was triggered on TVING’s system during the first attack attempt. Yet Director-General Lim directly acknowledged, “At the time, this was judged to be a routine system error rather than a cyberattack, and no follow-up security measures were taken.”
This single sentence captures the essence of the TVING breach incident. The alarm sounded, but no one read it; even if it was read, it was misjudged; and there was no procedure to correct that misjudgment. In incident response, the most expensive mistake is not the response after a breach, but missing the very moment of breach. From a practitioner’s perspective, what stands out is that this is not just TVING’s problem — it reflects a structural weakness across major domestic OTT and platform operators that fail to maintain proper monitoring systems and escalation rules.
In the latter part of the Q&A, the level of sanctions and responsibility emerged as key issues. Under the current Information and Communications Network Act, fines and criminal penalties are possible for violations, but if the initial figure of 39.54 million is adjusted, the scale of sanctions could also change. The joint investigation team only reiterated its position that “the level of sanctions will be decided after reviewing the PIPC’s results.”
These investigation results officially indicate insufficient early detection and response capabilities in the TVING breach. It is not merely a hacking incident — it is a case where “the alarm sounded but was not heard.” In this respect, the TVING breach raises the need for the industry as a whole to re-examine its incident response matrix. It should also be clearly remembered that the 39.54 million figure announced on September 3rd may not be the confirmed number. The initial announcement figure, the measured value after excluding duplicates, and the PIPC’s final confirmed value — whether these three numbers will match to a single digit is still unknown.
What to Do Right Now
- Change your TVING account password immediately to a combination of 12+ characters including letters, numbers, and special symbols.
- Also change passwords separately for any other services (email, banking, shopping) that share the same password as your TVING account.
- Enable ‘Login Notifications’ and ‘Two-Factor Authentication (if available)’ in the TVING app settings.
- Check whether the email you use is included in leaked datasets at haveibeenpwned.com.
- Review your payment card transaction history registered with TVING on a 7-day cycle, and request an immediate card suspension from the issuer if you detect any suspicious transactions.
Key Issues
- Actual scope of the breach: 39.54 million is the initial figure including duplicates and will be finalized through the PIPC investigation.
- Initial alarm misjudgment: Circumstances in which the CPU 100% alarm was classified as a system error have been officially confirmed.
- Responsibility: The level of fines and criminal penalties for detection and response failures will be determined after the figure is confirmed.
- Industry implications: Platforms that do not operate an alarm-escalation-response matrix are exposed to the same pattern.
- Individual control: Users should trust the initial announcement figure but simultaneously carry out password changes and payment monitoring until the confirmed figure is released.
Frequently Asked Questions
How can I directly check whether my TVING account was leaked?
TVING officially operates a leaked account lookup page. You can also instantly check whether your registered email is included in external breach datasets by searching it at haveibeenpwned.com.
How many actual victims are there among the 39.54 million reported accounts?
This has not yet been confirmed. The 39.54 million figure is the initial count including duplicates, and the precise scope of the breach will be disclosed through the PIPC’s additional investigation.
Is it safe to delete my TVING account?
The leaked data is already out in the wild, so deletion is not a direct solution. Instead, changing your password, separating payment methods, and enabling two-factor authentication are more effective.
What sanctions may be imposed on TVING in the future?
Fines, corrective orders, and criminal penalties are possible for violations of the Information and Communications Network Act. However, the level of sanctions depends on the PIPC’s final investigation results and cannot be predicted at this time.
Reference Source
This article was prepared by reviewing the following original source: BoanNews — MSIT and KISA: “39.54 million TVING leaked accounts include many duplicates”… Precise scope to be determined by PIPC investigation

Leave a Reply