Incident record

카카오게임즈

Kakao Games (Partners / RINK) · Gaming

Confirmed

This record separates what has been publicly claimed, investigated, and confirmed. It does not imply that every affected account belongs to a unique person.

Reported impact

140 users

Disclosure recorded

2026-09-16

Sector

Gaming

Practical risk

Low

What this means

A practical reading of this record

The public record supports a low practical risk level based on the currently reported scope and data categories. This can change if the organisation or regulator updates the record.

  • Change the password for this service through its official app or website. Change it anywhere you reused it.

Classification

Data breach

Categories are assigned only where the currently stored public record supports them. A privacy decision is not automatically treated as a hacking incident.

Evidence status

Why it appears in the index

Confirmed by the organisation, a regulator, or a documented official decision.

Kakao Games stated that the exposed items were third-party integration identifiers or IDs for Partners, and internal identifiers plus limited country codes for RINK. It said passwords and high-sensitivity data such as names and addresses were not confirmed as exposed.

Recorded source · Kakao Games disclosure and Korean media reporting ↗

Editorial record

Review and status trail

Last reviewed

2026-09-21

The latest editorial review of the stored public record.

Latest source event

2026-09-16

The most recent dated event currently documented on this page.

  1. Confirmed

    Current status recorded from the first documented public event in this entry.

Documented events

Public timeline

3 milestones4 days documented
  1. 01

    External attack began

    Kakao Games detected abnormal external access to its Partners and RINK services at 22:44 KST.

  2. 02

    Leak confirmed

    During its investigation, the company confirmed that data relating to 140 users had been exposed.

  3. 03

    Company notice

    Kakao Games published a public notice, reported the incident to relevant authorities, and began a further investigation with an external security firm.

Data reported exposed

Account IDCountry codeOther

Protect your account

Change your password if you use this service

Use a new, unique password through the official app or website. Change any other account where you reused it, and enable a passkey or two-factor authentication when available.

Secure your account

Correction

Is something inaccurate or outdated?

Send a public source or official correction. Material updates are logged rather than silently replacing the record.

Report an error