NHN Dooray! Breach: Account Takeover and Leaked API Keys Expose Some Customers' Work Data

NHN Dooray! security advisory: account takeover, keys leaked. High, no CVE. Not in CISA KEV.

Status: According to NHN Dooray, attacking IP addresses have been blocked, the password-reset check has been hardened, and all previously issued Service API and Admin API keys have expired. NHN Dooray says Service and Admin API use, suspended after the 13 November incident, resumed after 23:10 KST (16:10 Israel time / 14:10 UTC) on Monday 16 November 2026; customers who still need the APIs must issue new keys. The incident has been reported to KISA and the Personal Information Protection Commission (PIPC). No CVE or attribution has been published.

Executive Summary

Dooray! is a cloud collaboration suite (projects, drive, messenger, calendar, mail) run by NHN Dooray Corp., part of South Korea's NHN group. It offers private-sector and public-sector services. On 14 November 2026, Dooray! published a security incident notice on its help centre. According to the notice:

  • The incident happened from about 22:00 KST on 12 November until the early hours of 13 November 2026.
  • An outsider repeatedly entered verification codes in the "find password" flow and passed the verification, then changed the passwords of some accounts and logged in.
  • A security weakness in the Open API service leaked some API keys, and API calls by the outsider using those keys were confirmed.
  • For some customer accounts, work data in projects, drive, messenger and calendar was leaked, along with those customers' employees' account details: ID, name, external email address, phone number, department, rank, title and company.
  • Dooray! says the listed items are those that may have leaked, and that each person's actual items are in the individual notification email.

Facts that limit the alarm: NHN Dooray says only some customer accounts were affected. NHN Dooray says it revoked all existing Service API and Admin API keys and suspended both APIs, then resumed both APIs after 23:10 KST on 16 November 2026; all previously issued keys have expired, and customers who still need the APIs must issue new ones. It reported to KISA on 13 November and PIPC on 14 November, and is notifying affected individuals directly.

NHN Dooray has not disclosed how many customers or accounts were affected, which ones, whether any public-sector tenant was involved, or what the Open API weakness was.

For third-party risk teams, the questions are: which suppliers run their work on Dooray!, were they notified, and what of yours sits in their Dooray! projects, drives and chats? If they used the Service API or Admin API, have they issued new keys and reviewed the integrations that used the old ones?

What Happened

Dooray! has published three notices about this incident on its help centre.

13 November 2026: API suspension. In "보안 조치에 따른 민간, 공공 서비스 및 Admin API 이용 중단 안내" (our translation: "Suspension of private and public service and Admin API due to security measures"), Dooray! said it had found an outsider attempting to access accounts in the early hours of that day. As an emergency step, it revoked all existing Service API and Admin API keys and stopped both APIs, so API-based integrations and automations stopped working. It said API access would resume once security checks and stabilization work were done, and that administrators would be told by email. That notice still describes the suspension and does not record the resumption; the 17 November notice below is the later update.

14 November 2026: breach and personal-data notice. In "두레이 민간 및 공공 보안 침해사고 및 개인정보 유출 관련 안내" (our translation: "Notice on the Dooray private and public security breach and personal data leak"), Dooray! confirmed an outsider's breach of some customer accounts. It describes the two routes summarized above but not how they connect. It adds:

What was leaked. For Dooray! customers: work data in some customer accounts' projects, drive, messenger, calendar and similar, plus employee account details (ID, name, external email address, phone number, department, rank, title, company). For people whose data appeared in NHN Dooray's own corporate work files: name, email, mobile and phone numbers, position or title, department and company name. The notice says these are the items that may have leaked and that actual items are listed in individual notification emails.

What NHN Dooray did. Beyond the measures listed above, it says it has taken the necessary action on "abnormal settings" (our translation) found during the intrusion and is notifying affected individuals separately.

What it asks customers to do. Change the password of any account confirmed as compromised immediately, and have other users change theirs. Turn on two-factor authentication. Watch for phishing emails and smishing texts sent to leaked addresses and numbers, and never give out a password or verification code.

Boannews and Edaily reported the notice. Edaily says Dooray! is used by government ministries and public institutions as well as private companies. Neither the notice nor the press reports say whether any public-sector tenant was affected.

17 November 2026: API resumption. In "민간,공공 서비스 및 관리 API 이용 재개 안내" (our translation: "Notice of resumption of private and public service and admin API use"), Dooray! said Service and Admin API use, which had been temporarily suspended after the 13 November security incident, resumed after 23:10 KST (16:10 Israel time / 14:10 UTC) on Monday 16 November 2026. It said the resumption followed completed security checks and stabilization work. All previously issued Service and Admin API keys have expired and cannot be used; customers who still need the APIs must issue new keys. Dooray! says Admin API keys can be issued from the Admin page, where an allowed-IP list can be registered so calls work only from those IPs. The notice also links to Dooray!'s Service API guide and Admin API guide.

What has not been disclosed:

  • How many customers or accounts were affected, or which ones.
  • What the Open API weakness was, and how many keys leaked.
  • What the attacker did with the API access beyond the confirmed calls.
  • Whether the leaked work data has been published or offered for sale.
  • Who was behind the attack.

Technical Information

Two routes in. NHN Dooray describes two routes, not one exploit.

  • Password reset. The attacker got past the find-password verification by entering codes repeatedly. NHN Dooray has not said how many attempts were allowed or how the check worked; it says it has strengthened it.
  • Open API keys. A weakness in the Open API service exposed some API keys. NHN Dooray confirmed API calls by the outsider using the leaked keys. As an emergency measure, it revoked all existing Service API and Admin API keys and suspended both APIs; the 13 November notice said integrations with external systems and automations that use the API could not be used until access was restored. The 17 November notice says access resumed after 23:10 KST on 16 November 2026, and that all previously issued keys have expired.

What this is not. No CVE has been published, so there is no CVSS score or KEV listing. Customers have nothing to patch.

Affected Product Versions

N/A — SaaS incident. There is no customer-installed Dooray! version to upgrade.

  • Breached: some Dooray! customer accounts, according to NHN Dooray. NHN Dooray says it is notifying each individual whose personal data leaked; Edaily reports that affected client companies were also notified.
  • Affected by the API key expiry: every customer using the Service API or Admin API, private and public. NHN Dooray says API use resumed after 23:10 KST on 16 November 2026, but previously issued keys have expired, so integrations and automations will not work until new keys are issued.

Workaround and Mitigation

  1. Check for an NHN Dooray notification. NHN Dooray says it is notifying affected individuals directly and that each notification email lists the actual leaked items; Edaily reports that affected client companies were notified too.
  2. Reset passwords and turn on two-factor authentication. NHN Dooray asks customers to change the passwords of compromised accounts immediately, have all other users change theirs, and set up two-factor authentication. Make two-factor authentication mandatory for all users, and change reused passwords on other services too (Rescana guidance).
  3. Reissue API keys and review integrations. NHN Dooray says Service and Admin API use resumed after 23:10 KST on 16 November 2026, and that all previously issued keys have expired. If you still need the APIs, NHN Dooray asks you to issue new keys. Dooray! says Admin API keys can be issued from the Admin page, where an allowed-IP list can be registered so calls work only from those IPs. Set allowed IPs when you reissue Admin API keys, issue new keys with the least privilege needed, remove old keys from code, CI and config files, and review every integration or automation that used an old key (Rescana guidance).
  4. Rotate secrets stored in Dooray! (Rescana guidance). If teams kept passwords, tokens, API keys or connection details in Dooray! projects, drive files, messenger chats or calendar invites, treat them as exposed and rotate them at the issuing system.
  5. Warn staff about phishing and smishing. Leaked emails, phone numbers and job titles make targeted lures easier (Rescana guidance). NHN Dooray asks users not to open unknown links or attachments and never to share passwords or verification codes.
  6. Follow the Dooray! notice board for any further update.

Indicators of Compromise

NHN Dooray says it blocked the attackers' IP addresses but has not published them, or any other indicators. We will not invent any. Use your own Dooray! admin logs: password resets you didn't request, logins from unfamiliar locations, and API activity before the 13 November key revocation (Rescana guidance).

What to Do With This Vendor Today (TPRM)

Supplier projects, shared drives and chats often hold contracts, customer data, designs and, too often, credentials. If a supplier works with you inside Dooray!, your data may be in the affected work files even if you never used Dooray! yourself.

Ask suppliers, partners and service providers that may use Dooray!:

  1. Do you use NHN Dooray! for work that involves our data, projects or staff? Which tenant: private or public-sector service?
  2. Did NHN Dooray notify you that your organization or any user was affected? If yes, which data does the notification list, and does any of it relate to us?
  3. Have you reset passwords and enforced two-factor authentication for all users?
  4. Did you use the Dooray! Service API or Admin API? Which systems were connected? Have you issued new keys (the previously issued ones have expired), set allowed IPs on Admin API keys where the Admin page allows it, removed old keys from code, CI and integrations, and reviewed each integration that used an old key?
  5. Did anyone store credentials, tokens or our confidential data in Dooray! projects, drives or chats? Have those credentials been rotated?
  6. Will you share NHN Dooray's findings and tell us if the scope changes? Check whether Dooray! is on their subprocessor list and what notification timeline they commit to.

If your own organization uses Dooray!, ask your administrators the same questions and record the answers against the supplier record.

Need help finding which of your suppliers use Dooray! and tracking their answers? Talk to an expert

Sources

Talk to an expert

Talk to Rescana about this advisory — or about how we help TPRM teams keep reviews moving.