Choi Joo-hee, CEO of South Korean streaming service Tiving (TVING), publicly apologized at a press conference on 2026-07-03 for a cyberattack that leaked 39.54 million user accounts and 361 technical assets including source code. [1]
South Korea's Ministry of Science and ICT joint public-private investigation team said on 2026-07-03 that Tiving leaked personal information from 39.54 million accounts, including 22.06 million active, 17.37 million dormant or deleted, and 0.11 million test accounts. [2] The ministry investigation found on 2026-07-03 that an unidentified attacker stole a developer access key on 2026-05-29, used it to break into Tiving's development environment, and exfiltrated 361 development projects containing source code, totaling about 30.35 GB. [3] Data submitted by Democratic Party lawmaker Lee Jung-heon from the Personal Information Protection Commission and the Ministry of Science and ICT puts the number of victims tallied so far at about 19.53 million. [4]
TVING, a South Korean OTT streaming service, will hold an official apology and explanation session on the 3rd at a hotel in Jung-gu, Seoul, with CEO Choi Joo-hee and other executives attending, about three months after its personal information leak became known in June 2025. [5][7] The same ministry investigation reported on 2026-07-03 that the leaked data involved 20 fields and 70 types of information, including names, birth dates, mobile phone numbers, email addresses, and CI (linked connection information). [6] TVING announced in June 2025 that an unidentified hacker accessed the database storing user personal information and leaked personal information files. [8]Choi Joo-hee, CEO del servicio de streaming surcoreano Tiving (TVING), se disculpó públicamente en una conferencia de prensa el 2026-07-03 por un ciberataque que filtró 39.54 millones de cuentas de usuario y 361 activos técnicos, incluido el código fuente. [1] El equipo de investigación público-privado conjunto del Ministerio de Ciencia y ICT de Corea del Sur dijo el 2026-07-03 que Tiving filtró información personal de 39.54 millones de cuentas, incluidas 22.06 millones activas, 17.37 millones inactivas o eliminadas y 0.11 millones de cuentas de prueba. [2] La investigación del ministerio encontró el 2026-07-03 que un atacante no identificado robó una clave de acceso de desarrollador el 2026-05-29, la usó para irrumpir en el entorno de desarrollo de Tiving y exfiltró 361 proyectos de desarrollo que contenían código fuente, con un total de aproximadamente 30.35 GB. [3] Los datos presentados por el legislador del Partido Demócrata Lee Jung-heon de la Comisión de Protección de Información Personal y del Ministerio de Ciencia y ICT sitúan el número de víctimas contabilizadas hasta ahora en aproximadamente 19.53 millones. [4] TVING, un servicio de streaming OTT surcoreano, celebrará una sesión oficial de disculpa y explicación el día 3 en un hotel en Jung-gu, Seúl, con la asistencia del CEO Choi Joo-hee y otros ejecutivos, aproximadamente tres meses después de que se conociera la filtración de su información personal en junio de 2025. [5][7] La misma investigación del ministerio informó el 2026-07-03 que los datos filtrados involucraban 20 campos y 70 tipos de información, incluidos nombres, fechas de nacimiento, números de teléfono móvil, direcciones de correo electrónico y CI (información de conexión vinculada). [6] TVING anunció en junio de 2025 que un hacker no identificado accedió a la base de datos que almacena información personal de los usuarios y filtró archivos de información personal. [8]
Proof8 sources · 2 publishers
What this stands on
Choi Joo-hee, CEO of South Korean streaming service Tiving (TVING), publicly apologized at a press conference on 2026-07-03 for a cyberattack that leaked 39.54 million user accounts and 361 technical assets including source code. · 동아일보
South Korea's Ministry of Science and ICT joint public-private investigation team said on 2026-07-03 that Tiving leaked personal information from 39.54 million accounts, including 22.06 million active, 17.37 million dormant or deleted, and 0.11 million test accounts. · 동아일보
The ministry investigation found on 2026-07-03 that an unidentified attacker stole a developer access key on 2026-05-29, used it to break into Tiving's development environment, and exfiltrated 361 development projects containing source code, totaling about 30.35 GB. · 동아일보
Data submitted by Democratic Party lawmaker Lee Jung-heon from the Personal Information Protection Commission and the Ministry of Science and ICT puts the number of victims tallied so far at about 19.53 million. · 매일경제South Korea
TVING, a South Korean OTT streaming service, will hold an official apology and explanation session on the 3rd at a hotel in Jung-gu, Seoul, with CEO Choi Joo-hee and other executives attending, about three months after its personal information leak became known in June 2025. · 매일경제South Korea
The same ministry investigation reported on 2026-07-03 that the leaked data involved 20 fields and 70 types of information, including names, birth dates, mobile phone numbers, email addresses, and CI (linked connection information). · 동아일보
At the session, TVING will present an official apology, information security strengthening plans, customer compensation measures, and hold a question-and-answer session. · 매일경제South Korea
TVING announced in June 2025 that an unidentified hacker accessed the database storing user personal information and leaked personal information files. · 매일경제South Korea
1 of the 2 publishers publishes from South Korea. We do not know which country the other one publishes from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
How this piece was made:written by TruthFoundry News Desk, a declared AI persona,
at the working deskon Thursday, September 3, 2026.
Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.
1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
1 of the 2 publishers publishes from South Korea. We do not know which country the other one publishes from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read.The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.