NHN Dooray confirmed on 14 November 2026 that attackers breached some client accounts on Dooray!, and that business data and employee personal information leaked. The incident ran from about 22:00 on 12 November to the early morning of 13 November. No victim count was disclosed.
Dooray! combines projects, drives, messengers and calendars in a single cloud service used by companies and public institutions. eDaily reported that the platform was recently used to develop Gukbang I-eum. That platform serves about 300,000 military personnel. The reporting does not say data from that military platform was among the leaked data. eDaily and Global Economic reported the notices; this article relies on their reporting rather than the notice text.
Dooray! customers named in the reporting#
Global Economic named Woori Financial, the Ministry of National Defense, the Korea Aerospace Administration and the National AI Commission among Dooray! customers. None of those organisations has been named as affected, and no report says their data leaked.
Password recovery and open API access#
The attacker used two routes, according to eDaily. The first route ran through password recovery. The attacker repeatedly entered verification codes during the recovery process, changed the passwords of some accounts, and then logged in without authorisation. The report does not say how many codes were tried, how many accounts were taken over this way, or why repeated entry was possible.
The second route ran through an open API vulnerability. Some authentication keys leaked through the vulnerability, and API calls by unauthorised third parties exploiting it were confirmed. No technical detail was published. The report gives no count of leaked keys, and no account of what the unauthorised API calls retrieved.
The attacker changed account passwords and used leaked API keys to take over the accounts.
Client work and employee details obtained#
The leaked data covers two groups. The first group is work content from some client companies, held in projects, drives, messengers and calendars. An NHN Dooray spokesperson confirmed the leak to eDaily:
To date, we have confirmed that business-related data, including emails and messages from some client companies, as well as personal information such as employee IDs, names, and contact information have been leaked.
Project files, drive documents, messenger threads and calendar entries can carry internal discussions and client details.
The second group is employee personal data. eDaily reported that the IDs, names, external email addresses, phone numbers, departments, job titles, positions and company names of client company employees were leaked. An external email address is the address an employee uses outside Dooray! The leak therefore connects a work identity to an address that can be contacted directly and matched against other data sets. NHN Dooray warned that leaked email addresses and phone numbers could be used for phishing and smishing. A breach of email addresses puts the name, employer, department and job title alongside the address.
No passwords appear in the reported leaked data. The attacker changed some account passwords during the attack. A changed password is not a leaked password, and no source lists passwords among the leaked data. No number was given. No source states how many accounts, employees or client companies were affected. The scope is described only as some client accounts and some client companies, and the investigation into the extent of the damage was still under way when eDaily reported the story.
Regulator notifications#
NHN Dooray published a first notice on 13 November. That notice said an external account-access attempt had been confirmed in the early morning of 13 November. It announced emergency measures to protect private and public client accounts. Global Economic reported that the notice did not disclose whether the intrusion had succeeded, whether information had leaked, or how many client companies were affected. The leak was confirmed on 14 November. eDaily reported it on 15 November.
| Date | Event |
|---|---|
| 13 November 2026 | NHN Dooray published a first notice on an external account-access attempt and revoked all service API and administrator API keys. |
| 14 November 2026 | NHN Dooray confirmed that business data and employee personal information had leaked. |
| 15 November 2026 | eDaily reported the confirmed leak. |
NHN Dooray blocked the IP addresses used in the attack. It strengthened the password-reset verification process. It revoked all existing service API and administrator API keys and suspended the related functions. That closed the second attack route. External system integrations and automation that depended on those keys broke with it. Global Economic reported that the API functions would resume once safety was confirmed. No restart schedule had been decided by 13 November.
NHN Dooray reported the incident to two regulators. The security breach went to the Korea Internet and Security Agency (KISA), and the personal information leak to the Personal Information Protection Commission. It notified the affected client companies and individual account holders of the details of the incident. A spokesperson promised cooperation with the relevant authorities. Its work now is to identify the cause, prevent recurrence and restore client data.
Steps stated for Dooray! users#
NHN Dooray changed the passwords of the affected accounts and recommended that other users change their passwords and set up two-factor authentication. Users were told to check whether a notice had arrived from NHN Dooray or from their employer. Affected companies and account holders were notified directly. The guide to whether changing a password stops hackers sets out what a password change can and cannot do after an account takeover.
Password reuse is the main risk here. An attacker who changed an account password through recovery codes has shown that the recovery process can be abused. A user who reuses the same password elsewhere hands the same risk to other accounts. Have I Been Pwned lists breaches by email address. Checking the affected address there shows whether it has appeared in earlier breaches, and the guide to whether Have I Been Pwned is safe explains how to read the results.
The phishing risk lasts longer. The leaked details let an attacker send convincing messages, and names and job titles do the rest. They make the messages look as if they come from inside the organisation. Phishing messages built on leaked email addresses are harder to spot than generic spam because they use real details. Unexpected messages asking for credentials, payments or document access should be checked through a separate channel, since replying to the message itself proves nothing. NHN Dooray also named smishing in its warning, since phone numbers leaked alongside the email addresses. The guide to checking whether an email is phishing covers the checks to run before opening any link.
Your address is probably in this file. Check whether it is, do the password work above, and then fix the part you control: the address you hand out next time. One AliasFleet alias per service means the next leak can only point back to the service that leaked it. Founders Club is $7 a month, locked forever, instead of $12. Early members only.
Open questions in the NHN Dooray investigation#
eDaily described the investigation into the extent of the damage as under way, and the investigation was still open. Global Economic quoted an NHN official saying the specific damage was still being confirmed and would be shared as it was identified. The reports to KISA and the Personal Information Protection Commission put the incident under the Korean regulators for security breaches and personal information leaks.
Several facts remain unknown. The number of affected accounts and people has not been disclosed, and the full list of affected client companies has not been published. The technical detail of the open-API vulnerability has not been described. No attacker has been named, no motive has been stated, and no confirmed misuse of the leaked data has been reported.
The NTT Docomo breach offers a comparison. Disclosed earlier in November 2026 with up to about 300,000 customer records affected, it shows how much more detail an investigation can produce once it has progressed. A collaboration platform holds two kinds of data at once: the work itself and the identity of the people doing it. For the affected employees, the practical consequence is a higher risk of targeted phishing at their external email addresses. The practical response is the one NHN Dooray gave. Change the password and turn on two-factor authentication. Treat unexpected messages with suspicion until the company says more.
