…was completely destroyed in a fire at the National Information Resources Service …
le centre de donnée a disparu! avec les serveurs dans un incendie, il y a une photo avec les serveurs dans un bac d'eau et les responsable devant qui ne semblent pas très heureux. rien que pour ca la photo ca vaut le coup d'oeuil
sur certain de mes équipements avec un ssd qui subisse un incendie ET que le ssd n'a pas eu trop trop chaud en général je recupere 100% du ssd (industriel sensé tenir jusqu'a 85 degré)
mais comment volts arrive a trouver ce genre d'information !!
Posté par Psychofox (Mastodon) .
Évalué à 10 (+9/-0).
Dernière modification le 06 octobre 2025 à 18:25.
Note by PHRACK STAFF:
A responsible disclosure was attempted to warn South Korea that China/North Korea has hacked them. The full article, dump and release schedule was shared with South Korea before it was published:
16th of June 2025, Informed Defense Counterintelligence Command.
26th of June 2025, Anonymous response from clearbear001 (dcc.mil.kr?).
16th of July 2025, Anonymous response from operation-dl (who is this?).
17th of July 2025, Informed KISA.
17th of July 2025, Informed Ministry of Unification.
17th of July 2025, Informed LG Uplus Corp.
18th of July 2025, Informed KrCERT.
1st of August 2025, Communication then ended abruptly.
14th of August 2025, The author received an ominous message via Signal, advising him that Proton is not secure (using a burner-phone). (Noticeable: The contact knew about “notfox”, a handle only shared with the South Korean government. Why the contact???).
15th of August 2025, Proton disables the whistleblower’s email account.
16th of August 2025, Proton disables the author’s email account.
18th of August 2025, The complaint fails. The appeal fails. Proton’s response: “your account will cause further damage to our service, therefore we will keep the account suspended”.
22nd of August 2025, Phrack vigorously tries to contact Proton-legal, Andy, and others at Proton. No response.
6th of September 2025, Phrack gives Proton 48h notice: Please respond, or we will try to reach you via social media.
9th of September 2025, Phrack reaches out to Proton on social media.
10th of September 2025, Proton re-enables both email accounts. The email account was only used to communicate with South Korea. No ToS was violated. No crime was committed.
We trust that Proton will fix the appeal process and become more transparent. Don’t give up on Proton just yet.
So far Proton has not answered our emails or taken our calls. We wish to communicate and work this out together. This is not our first rodeo.
We thank the community for their support and courage.
…and the story continued…
24th of September 2025, The parliament of South Korea launches an investigation into China/North Korea hacking critical government systems in South Korea & the response (See biz.chosun.com; Questioning of KT’s CEO, KT’s CISO, and officials from SK Telecom and LG Uplus)
25th of September 2025, The Government announces an on-site inspection for 20 hours and 30 minutes, scheduled to start on the 26th of September at 7:30pm and will last until the 27th of September at 4pm.
26th of September 2025, The government data centre suffers a catastrophic failure and burns (video). More than 96 servers are fully destroyed, including the Onnara and GPKI servers mentioned in the Phrack article (and with it, most of the evidence).
27th of September 2025, The fire is believed to have been caused while replacing Lithium-ion batteries. The batteries were manufactured by LG, the parent company of LG Uplus (the one that got hacked by the APT).
27th of September 2025 at 4pm: The “on-site” inspection......was no more.🤡
2nd of October 2025, A new fire erupts at the Lotte IDC (which was also under investigation by the parliament).
At least nobody is falling out of the windows. 8h later: JFC!!!😬. source: https://phrack.org/issues/72/7_md#article
# petit resumé
Posté par ChocolatineFlying . Évalué à 6 (+5/-0).
…was completely destroyed in a fire at the National Information Resources Service …
le centre de donnée a disparu! avec les serveurs dans un incendie, il y a une photo avec les serveurs dans un bac d'eau et les responsable devant qui ne semblent pas très heureux. rien que pour ca la photo ca vaut le coup d'oeuil
sur certain de mes équipements avec un ssd qui subisse un incendie ET que le ssd n'a pas eu trop trop chaud en général je recupere 100% du ssd (industriel sensé tenir jusqu'a 85 degré)
mais comment volts arrive a trouver ce genre d'information !!
[^] # Re: petit resumé
Posté par volts (Mastodon) . Évalué à 4 (+2/-0).
Tu préférerais de ne pas savoir, pas vrai ?
[^] # Re: petit resumé
Posté par raphj (site web personnel) . Évalué à 3 (+1/-0).
C'était bien la Corée du Sud ? Tu as pu prendre quelques belles photos avant de revenir ? :-)
[^] # Re: petit resumé
Posté par ǝpɐןƃu∀ nǝıɥʇʇɐW-ǝɹɹǝıԀ (site web personnel) . Évalué à 7 (+5/-0).
Les plus drôle c'est la raison invoquée pour ne pas avoir de sauvegarde : « trop de données [critiques !] »
« IRAFURORBREVISESTANIMUMREGEQUINISIPARETIMPERAT » — Odes — Horace
[^] # Re: petit resumé
Posté par Antoine J. . Évalué à 8 (+6/-0).
On a enfin la solution aux problèmes de fuites de données.
[^] # Re: petit resumé
Posté par BAud (site web personnel) . Évalué à 7 (+5/-0).
nan mais t'appelle ton pote Dave Null, il a tout stocké !
[^] # Re: petit resumé
Posté par Psychofox (Mastodon) . Évalué à 8 (+6/-1).
La section lien est à quelques exceptions près une sélection de liens déjà publiés sur hacker news.
[^] # Re: petit resumé
Posté par volts (Mastodon) . Évalué à 4 (+2/-0).
C'est exact, je l'avais bien piochée sur Hacker News.
Le lien d'origine vient de cette discussion (et celle du Phrack également)
# Autres articles
Posté par Benoît Sibaud (site web personnel) . Évalué à 5 (+2/-0).
https://www.straitstimes.com/asia/east-asia/up-in-smoke-work-documents-of-191000-civil-servants-lost-in-data-centre-fire-in-south-korea
https://www.koreaherald.com/article/10588068
# l'histoire est bien plus croustillante que cela
Posté par Psychofox (Mastodon) . Évalué à 10 (+9/-0). Dernière modification le 06 octobre 2025 à 18:25.
Note by PHRACK STAFF:
A responsible disclosure was attempted to warn South Korea that China/North Korea has hacked them. The full article, dump and release schedule was shared with South Korea before it was published:
16th of June 2025, Informed Defense Counterintelligence Command.
26th of June 2025, Anonymous response from clearbear001 (dcc.mil.kr?).
16th of July 2025, Anonymous response from operation-dl (who is this?).
17th of July 2025, Informed KISA.
17th of July 2025, Informed Ministry of Unification.
17th of July 2025, Informed LG Uplus Corp.
18th of July 2025, Informed KrCERT.
1st of August 2025, Communication then ended abruptly.
14th of August 2025, The author received an ominous message via Signal, advising him that Proton is not secure (using a burner-phone). (Noticeable: The contact knew about “notfox”, a handle only shared with the South Korean government. Why the contact???).
15th of August 2025, Proton disables the whistleblower’s email account.
16th of August 2025, Proton disables the author’s email account.
18th of August 2025, The complaint fails. The appeal fails. Proton’s response: “your account will cause further damage to our service, therefore we will keep the account suspended”.
22nd of August 2025, Phrack vigorously tries to contact Proton-legal, Andy, and others at Proton. No response.
6th of September 2025, Phrack gives Proton 48h notice: Please respond, or we will try to reach you via social media.
9th of September 2025, Phrack reaches out to Proton on social media.
10th of September 2025, Proton re-enables both email accounts.
We trust that Proton will fix the appeal process and become more transparent. Don’t give up on Proton just yet.
So far Proton has not answered our emails or taken our calls. We wish to communicate and work this out together. This is not our first rodeo.
We thank the community for their support and courage.
…and the story continued…
24th of September 2025, The parliament of South Korea launches an investigation into China/North Korea hacking critical government systems in South Korea & the response (See biz.chosun.com; Questioning of KT’s CEO, KT’s CISO, and officials from SK Telecom and LG Uplus)
25th of September 2025, The Government announces an on-site inspection for 20 hours and 30 minutes, scheduled to start on the 26th of September at 7:30pm and will last until the 27th of September at 4pm.
26th of September 2025, The government data centre suffers a catastrophic failure and burns (video). More than 96 servers are fully destroyed, including the Onnara and GPKI servers mentioned in the Phrack article (and with it, most of the evidence).
27th of September 2025, The fire is believed to have been caused while replacing Lithium-ion batteries. The batteries were manufactured by LG, the parent company of LG Uplus (the one that got hacked by the APT).
27th of September 2025 at 4pm: The “on-site” inspection......was no more.🤡
2nd of October 2025, A new fire erupts at the Lotte IDC (which was also under investigation by the parliament).
At least nobody is falling out of the windows. 8h later: JFC!!!😬.
https://phrack.org/issues/72/7_md#article
ah et une personne mêlée à tout cela se serait suicidée: https://m-fr.yna.co.kr/view/AFR20251003000800884?site=lang_fr
Ça sent quand même le gros nettoyage de preuves cette affaire.
[^] # Re: l'histoire est bien plus croustillante que cela
Posté par ǝpɐןƃu∀ nǝıɥʇʇɐW-ǝɹɹǝıԀ (site web personnel) . Évalué à 5 (+3/-0).
La bonne nouvelle c'est qu'ils sauront à quelles portes frapper pour récupérer les données les plus importantes !
« IRAFURORBREVISESTANIMUMREGEQUINISIPARETIMPERAT » — Odes — Horace
[^] # Re: l'histoire est bien plus croustillante que cela
Posté par Gil Cot ✔ (site web personnel, Mastodon) . Évalué à 2 (+0/-0).
puis
Ça s’appelle donc comme ça maintenant :)
“It is seldom that liberty of any kind is lost all at once.” ― David Hume
Envoyer un commentaire
Suivre le flux des commentaires
Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.