Data breach and hacking incidents
Public notices of data leaks and unauthorized access, mainly in Japan and South Korea, with sources, disclosure status and reported figures.
Data breach scale
Breach details
2026.11.21
Rokkatei
/ online shop Possible disclosureEstimated cause: System intrusion (hacking)
About 8,000 card records (as of the first report)
Full card numbersCard security codesNames, phone numbers and contact detailsAddresses / delivery locationsEmail addresses
2026.11.20
PLAID
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)
79,249 registered emails, 45,816 sales contacts and more
Email addressesAPI/site connection keysPersonal data (fields unconfirmed)
2026.11.20
overflow
/ Offers (KARTE) Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
16,080 people (14,738 workers and 1,342 company contacts)
Names, phone numbers and contact detailsDate of birth, gender and other profile detailsMember IDs / identifiersEmail addressesEmployee / workplace details
2026.11.20
Bank of Kagoshima and three others
/ Paydon (Infcurion) Disclosure / access confirmedEstimated cause: System intrusion (hacking)Via a contractor or outside service
251,172 records
Names, phone numbers and contact detailsDate of birth, gender and other profile detailsEmail addressesPasswords (including hashes)Bank accountsContracts, purchases and bookings
2026.11.20
Recruit Management Solutions
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
12,421 records
Names, phone numbers and contact detailsEmail addressesAddresses / delivery locationsEmployee / workplace details
2026.11.20
RIKEN
/ Fugaku and Rikyu supercomputers Possible disclosureEstimated cause: Staff error or poor managementSystem intrusion (hacking)
Up to 4,597 people (4,222 Fugaku and 375 Rikyu users)
Names, phone numbers and contact detailsEmail addressesMember IDs / identifiersAPI/site connection keysTrade secrets / business documents
2026.11.20
Kurly
/ curator program Disclosure / access confirmedEstimated cause: Account takeover or phishingSystem intrusion (hacking)
10,701 people (10,699 curators and 2 customers)
Names, phone numbers and contact detailsMember IDs / identifiersEmail addressesBank accountsKorean resident registration numbers
2026.11.20
Sumitomo Mitsui Banking Corporation
/ KARTE Disclosure / access confirmedEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)Account takeover or phishing
Up to about 14,000,000 records
Date of birth, gender and other profile details
2026.11.19
giftee
/ prismatix Possible disclosureEstimated cause: System intrusion (hacking)Via a contractor or outside service
About 305,000 emails in logs, up to about 12,000 member records and more (overlapping)
Email addressesPasswords (including hashes)Member IDs / identifiers
2026.11.19
SBC Medical Group
/ Tribeau Disclosure / access confirmedEstimated cause: System intrusion (hacking)
About 1,624,000 people and more (published by item)
Names, phone numbers and contact detailsEmail addressesAddresses / delivery locationsDate of birth, gender and other profile detailsPasswords (including hashes)Member IDs / identifiersContracts, purchases and bookingsInquiries / free-text entriesCard details (fields unspecified)
2026.11.19
S.RIDE
/ taxi app (KARTE) Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
Count not disclosed
Date of birth, gender and other profile detailsMember IDs / identifiersEmployee / workplace details
2026.11.19
Vitabrid Japan
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
11,590 people
Member IDs / identifiersEmail addressesNames, phone numbers and contact detailsDate of birth, gender and other profile detailsAddresses / delivery locations
2026.11.19
House Foods Group
/ KARTE Disclosure / access confirmedEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)Account takeover or phishing
44,800 records
Email addressesDate of birth, gender and other profile details
2026.11.19
Pocket Change
/ PocketChange and Pokepay Possible disclosureEstimated cause: System intrusion (hacking)
Up to 116,361 Pokepay records, up to 31,462 PocketChange records and more (partly overlapping)
Names, phone numbers and contact detailsEmail addressesMember IDs / identifiersIdentity document numbersFull card numbersBank accountsPrepaid card IDs, PINs and balances (non-PII)Addresses / delivery locationsDate of birth, gender and other profile details
2026.11.19
MOSH
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
928,617 records
Email addressesMember IDs / identifiers
2026.11.19
Kyash
/ internal web tool Disclosure / access confirmedEstimated cause: Staff error or poor management
Up to 11,996 people
Member IDs / identifiersContracts, purchases and bookings
2026.11.19
Timee
/ employer contact data (KARTE) Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
Up to 226,662 people (employer contacts)
Email addressesNames, phone numbers and contact detailsMember IDs / identifiersEmployee / workplace details
2026.11.19
Sharp
/ COCORO STORE (KARTE) Possible disclosureEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
Up to about 3,260,000 records
Date of birth, gender and other profile detailsMember IDs / identifiers
2026.11.18
Mirae Asset Life
Disclosure / access confirmedEstimated cause: System intrusion (hacking)
10,418 people
Names, phone numbers and contact detailsKorean resident registration numbersDate of birth, gender and other profile detailsEmail addressesAddresses / delivery locationsEmployee / workplace detailsContracts, purchases and bookings
2026.11.18
Nojima
/ Nojima Online Disclosure / access confirmedEstimated cause: System intrusion (hacking)
7,179,818 people (4,223 with bank account details)
Names, phone numbers and contact detailsEmail addressesAddresses / delivery locationsDate of birth, gender and other profile detailsMember IDs / identifiersPasswords (including hashes)Bank accounts
2026.11.18
MUFG Bank
/ KARTE Disclosure / access confirmedEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)Account takeover or phishing
About 6,500,000 records
Date of birth, gender and other profile details
2026.11.18
Mitsubishi UFJ Trust and Banking
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
About 230,000 records
Member IDs / identifiersDate of birth, gender and other profile details
2026.11.18
Mitsubishi UFJ eSmart Securities
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
About 60,000 securities account numbers / 105,000 age records
Bank accountsDate of birth, gender and other profile details
2026.11.18
KBIZ
/ Yellow Umbrella Mutual Aid Disclosure / access confirmedEstimated cause: System intrusion (hacking)
About 362,000 people
Names, phone numbers and contact detailsKorean resident registration numbersAddresses / delivery locationsEmail addressesBank accountsContracts, purchases and bookings
2026.11.18
Streami
/ GOPAX Disclosure / access confirmedEstimated cause: System intrusion (hacking)
2,009 people
Member IDs / identifiersImage metadata
2026.11.18
Infcurion
/ Notion AI Disclosure / access confirmedEstimated cause: AI-relatedSystem intrusion (hacking)Via a contractor or outside service
232 personal information records; other business data under review
Names, phone numbers and contact detailsEmail addressesEmployee / workplace detailsTrade secrets / business documents
2026.11.18
Nippon Liquor
/ Your Cellar Disclosure / access confirmedEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)
2,245 records
Email addresses
2026.11.18
Japan health ministry
/ medicine supply and distribution system Partly confirmed; scope under reviewEstimated cause: System intrusion (hacking)
Count not disclosed
Names, phone numbers and contact details
2026.11.18
Autobacs Seven
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
About 1,370,000 records
Member IDs / identifiers
2026.11.18
NTT Solmare
/ Comic Seymour and MangaPlaza (KARTE) Possible disclosureEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
Up to about 1,300,000 records (Comic Seymour about 130,000 and MangaPlaza about 1,170,000, possibly overlapping)
Member IDs / identifiersEmail addressesDate of birth, gender and other profile details
2026.11.18
MeetsMore
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
3,458,469 people (60,000 of them with a name, email, phone number or date of birth)
Names, phone numbers and contact detailsEmail addressesDate of birth, gender and other profile detailsMember IDs / identifiers
2026.11.18
Mitsubishi UFJ Morgan Stanley Securities
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
About 280,000 records
Date of birth, gender and other profile details
2026.11.18
DHC
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
About 19,110,000 records
Names, phone numbers and contact detailsEmail addressesDate of birth, gender and other profile detailsMember IDs / identifiers
2026.11.18
CAMPFIRE
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
5,819,779 records
Email addressesMember IDs / identifiers
2026.11.18
Ame Kaze Taiyo
/ Pocket Marche (KARTE) Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
955,049 people (944,885 consumers and 10,164 producers, including former members)
Member IDs / identifiersEmail addressesNames, phone numbers and contact details
2026.11.18
Osaki Electric
/ ransomware External disclosure unconfirmedEstimated cause: Ransomware or malware
Count not disclosed (exfiltration under investigation)
Information type unconfirmed
2026.11.18
Toyota Financial Services
/ TOYOTA Wallet (KARTE) Possible disclosureEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)Account takeover or phishing
About 120,000 records
Member IDs / identifiers
2026.11.18
SMS Co.
/ Eiche and Nurse Senka job services (KARTE) Possible disclosureEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
484,504 records across three services (possibly overlapping)
Names, phone numbers and contact detailsEmail addressesAddresses / delivery locationsDate of birth, gender and other profile detailsMember IDs / identifiers
2026.11.18
BASE FOOD
/ KARTE Disclosure / access confirmedEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)Account takeover or phishing
About 751,000 records (about 710,000 with email and name, plus others)
Email addressesNames, phone numbers and contact details
2026.11.18
Kashima Antlers
/ online store (OpenLogi) Disclosure / access confirmedEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)
40,844 people
Names, phone numbers and contact detailsAddresses / delivery locationsEmail addressesContracts, purchases and bookingsMember IDs / identifiers
2026.11.18
airCloset
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
50,990 people
Email addressesNames, phone numbers and contact detailsDate of birth, gender and other profile detailsMember IDs / identifiers
2026.11.18
LEGOLAND Japan
/ annual passes (accesso) Possible disclosureEstimated cause: System intrusion (hacking)Via a contractor or outside service
About 150,000 people
Names, phone numbers and contact detailsDate of birth, gender and other profile detailsAddresses / delivery locationsEmail addressesMember IDs / identifiers
2026.11.18
GPIF
/ m-FILTER MailAdviser Possible disclosureEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)Account takeover or phishing
Up to 8,859 email addresses
Email addresses
2026.11.18
Nulab
/ Cacoo Partly confirmed; scope under reviewEstimated cause: Account takeover or phishingSystem intrusion (hacking)
765 records confirmed, 1,200 possible
Names, phone numbers and contact detailsEmail addressesAddresses / delivery locationsPartial card detailsInquiries / free-text entriesContracts, purchases and bookings
2026.11.17
Rakuten Securities
/ test environment Possible disclosureEstimated cause: System intrusion (hacking)
Up to about 11,250,000 accounts / up to about 4,470,000 with detailed data
Member IDs / identifiersNames, phone numbers and contact detailsDate of birth, gender and other profile detailsAddresses / delivery locationsEmail addressesEmployee / workplace detailsBank accountsContracts, purchases and bookings
2026.11.17
JINS
/ membership Partly confirmed; scope under reviewEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)Account takeover or phishing
Up to about 18,290,000 accounts
Member IDs / identifiersEmail addressesNames, phone numbers and contact detailsDate of birth, gender and other profile detailsAddresses / delivery locations
2026.11.17
Francfranc
/ members and online store Possible disclosureEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
Up to about 5,980,000 membership records / 4,000,000 purchase-related records
Names, phone numbers and contact detailsDate of birth, gender and other profile detailsMember IDs / identifiersAddresses / delivery locationsContracts, purchases and bookings
2026.11.17
Club Tourism
/ KARTE Possible disclosureEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
About 4,060,000 records
Member IDs / identifiersDate of birth, gender and other profile details
2026.11.17
Alpen
/ Alpen Online Disclosure / access confirmedEstimated cause: Via a contractor or outside serviceSystem intrusion (hacking)Account takeover or phishing
86,494 records
Names, phone numbers and contact detailsEmail addresses
2026.11.17
MISUMI Group
/ KARTE Disclosure / access confirmedEstimated cause: System intrusion (hacking)Account takeover or phishingVia a contractor or outside service
About 140,000 records
Names, phone numbers and contact detailsEmployee / workplace details
How to prevent each type of data breach
For each of the seven causes AIB estimates, these are the steps organizations should take, compiled from public-agency material: IPA (Japan), the Japanese and Korean data-protection authorities and CISA (US).
System intrusion (hacking)
490 cases
- Keep an inventory of the software, servers and VPN devices you run, and apply security updates promptly. Do not run versions that are out of support.IPA Top 10 Threats #4 · IPA SME guidelines
- Collect vulnerability information, set patch priorities, and assume some flaws have no fix yet: layer defenses and set up detection for unusual activity.IPA Top 10 Threats #4
- Close unneeded ports, run only the services you need, and check protections against unauthorized access on public servers.IPA Top 10 Threats #1
- Consider a software bill of materials (SBOM) to track components.IPA Top 10 Threats #4 · IPA requirements handbook Table 37
- After an incident, investigate the scope and root cause and strengthen controls.IPA Top 10 Threats #4
Via a contractor or outside service
251 cases
- Write the security responsibilities, security requirements, handling of logs and audit trails, subcontracting conditions and liability terms into outsourcing contracts.IPA Top 10 Threats #2 · IPA requirements handbook 15.5, Table 13
- Make sure the contract lets you check the contractor's security and data handling regularly. Korea's response guide also lists contractor checks as a recurrence-prevention step.IPA Top 10 Threats #2 · Korea PIPC guide
- When choosing SaaS or AI services, set requirements for where data is stored, whether it is used for training, how long logs are kept, whether it can be deleted, and how you will be notified of a breach.IPA requirements handbook 10.6
- Know which contractor and partner accounts and network connections reach your systems, and agree on contact routes in advance.IPA Top 10 Threats #2
- In Japan, when a leak occurs at a contractor, both the client and the contractor generally must report to the PPC (a joint report is allowed).Japan PPC Guidelines 3-5-3-2
Account takeover or phishing
87 cases
- Turn on multi-factor authentication (MFA) for email, VPN and admin accounts first, and prefer phishing-resistant methods such as FIDO2 or passkeys. CISA notes that SMS and push MFA can be defeated by phishing and push bombing.IPA Top 10 Threats #1/#10 · CISA MFA fact sheet
- Use a different password for every service. CISA recommends unique passwords of at least 15 characters.CISA ransomware guide
- Delete accounts that are no longer needed after transfers or departures, and grant only the access each job needs.IPA Top 10 Threats #7
- Never act on a payment or bank-account change request by email alone; confirm through a separate, pre-agreed channel, and require more than one approver.IPA Top 10 Threats #10
- Review unusual sign-in records regularly.IPA Top 10 Threats #6
Staff error or poor management
32 cases
- Review sharing and public-access settings regularly (one of IPA's six basic rules).IPA SME guidelines · IPA Top 10 Threats Table 1.2
- Check websites for vulnerabilities at least once a year, restrict admin pages by IP or add a second factor, and make sure attachments in posts contain no personal data.Korea PIPC guide
- Train staff who handle personal data at least once a year, and share lessons right after an incident.Korea PIPC guide
- Control and log the use of USB drives and printers, destroy storage media so it cannot be recovered, and wipe leased equipment before returning it.IPA Top 10 Threats #7
- Add an authentication step and robots-exclusion rules so personal data is not exposed on the web.Korea PIPC guide
Ransomware or malware
24 cases
- Back up on a set schedule, protect the backups from tampering (offline or write-once storage), and regularly practice restoring from them.IPA Top 10 Threats #1 · CISA ransomware guide
- Prepare a clean-rebuild procedure for the case where systems are encrypted.IPA Top 10 Threats #1
- Do not expose services such as remote desktop to the internet, and minimize access rights to shared servers and directories.CISA ransomware guide · IPA Top 10 Threats #1
- Keep an incident response plan, with an offline copy. Leadership should decide its stance on ransom demands in advance.IPA Top 10 Threats #1 · CISA ransomware guide
- IPA advises recovering without paying the ransom: payment does not guarantee recovery or prevent the data from being published, and payers can be targeted again.IPA Top 10 Threats #1
AI-related
11 cases
- Ban unapproved AI services ("shadow AI") and limit business use of personal accounts. Track actual use through network logs or a CASB.IPA Top 10 Threats #3
- Opt out of training on your inputs and review the terms before contracting. Do not put trade secrets into cloud AI.IPA Top 10 Threats #3 · IPA AI security tips
- Japan's PPC asks businesses to confirm that an AI provider will not use personal data in prompts for machine learning before entering it.Japan PPC
- Keep checking during operation whether the system handles prompt injection, data leakage and misuse, and keep AI usage logs.IPA requirements handbook Tables 23, 37
- Decide in advance the conditions under which you will suspend or restrict an AI system after a leak.IPA requirements handbook Table 24
Related articles
Insider misuse
3 cases
- Leadership names an accountable owner and sets an information-handling policy that includes disciplinary rules.IPA Top 10 Threats #7
- Classify important data, assign owners, grant the minimum access each role needs, and ban shared IDs.IPA Top 10 Threats #7
- Log and monitor access to sensitive data, tell staff that monitoring exists, and watch more closely around an employee's departure.IPA Top 10 Threats #7
- Where needed, use DLP or CASB tools and have staff sign confidentiality agreements.IPA Top 10 Threats #7
- Apply the same controls to contractor staff who work inside your systems.IPA Top 10 Threats #7 case
If a breach happens: first steps and reporting deadlines
- First steps (Japan's PPC guidelines): (1) report internally and stop the damage from spreading, (2) investigate the facts and cause, (3) identify the scope, (4) plan and carry out recurrence prevention, (5) report to the regulator and notify affected people.Japan PPC
- Korea: Notify affected people within 72 hours of learning of a leak. From 11 September 2026, notice is also required within 72 hours of learning of a *possible* leak. Report to the PIPC within 72 hours if 1,000 or more people, sensitive or unique-identifier data, or outside unauthorized access are involved.Korea PIPC guide · Korea PIPC reporting
- Japan: Report to the PPC if the leak involves sensitive personal data, possible financial harm, a wrongful purpose, or more than 1,000 people. The preliminary report is due roughly 3–5 days after learning of it; the final report within 30 days (60 days if a wrongful purpose is suspected).Japan PPC
- Preserve logs and other evidence, and confirm backups are clean before restoring.IPA Top 10 Threats #1 · CISA ransomware guide
If you received a breach notice
Open the official app or site directly instead of links in the email, and act according to what leaked (contact details, passwords, cards or authentication data).
Your Card Number Wasn't Stolen. Are You Really Safe? How to Read a Data Breach NoticeHow to read and calculate these totals
These are cumulative reported figures for the incidents listed here. They are neither the total impact across Japan and South Korea nor a count of unique affected people.
Each case summarizes what organizations, authorities and news reports have published. It is not a final determination or a company rating, and cases are not ranked. If anything differs from the sources, please send a correction request.
Correction requestTwo reporting scopes
“Confirmed exposure” uses the adopted figures for information confirmed to have been exposed or accessed without authorization. “Reported scale (including potential exposure)” also includes potential exposure, maximum numbers under investigation, and estimates. It is not a confirmed exposure total. The two scopes must not be added together.
Cause classification (AIB estimate)
More than half of the published access routes are under investigation or not disclosed. So we sort each case into seven causes: system intrusion (hacking), account takeover or phishing, ransomware or malware, via a contractor or outside service, AI-related, staff error or poor management, and insider misuse.
A case can have more than one cause. For example, if a contractor was hacked and data leaked from there, it gets both system intrusion and via a contractor or outside service.
We first apply the causes that the published type, access route and outside-service fields state as fact. A decision model (Jev) then reads the case description, adds causes and picks the main one. Unauthorized access with an undisclosed route counts as system intrusion. This is our estimate, not what was published. The published access route is still shown separately.
Three units
Data records: the number of data items described in the source as records or entries. This can include counts of email addresses; it is not a count of information categories.
People: figures that sources report as people. The same person may be counted in more than one incident; duplicates across incidents have not been removed.
Accounts / IDs: the number of accounts or IDs. One person may hold multiple accounts, and inactive IDs may be included.
One record does not equal one person or one account. An incident may appear in multiple series, so we do not add the three series together or convert them into a number of people. We do not multiply figures by the number of information fields.
Handling duplicates
We count the latest adopted figure for an incident once, rather than adding its initial and subsequent announcements. Subsets already included in an overall figure are not added again. However, duplicate people or information across separate incidents have not been removed.
An example of a subset
The approximately 6,600,000 Times CAR accounts include approximately 1,600,000 accounts with identity-verification images. The adopted figure is about 6,600,000, not 8,200,000. Where overlap between categories is unclear, we may use only the larger category as the representative figure. It may therefore differ from the total across all categories.
What months and date ranges mean
The currently adopted figure is assigned to the incident’s announcement or update month. It does not show what was known at each point in time or the damage that occurred during that month. Selecting a date range accumulates only the incidents in that range, starting from zero.
Exclusions
Unknown figures, incidents determined to involve no exposure, and other units such as contracts, facilities, or percentages are excluded from the totals. Figures involving only possible exposure are excluded from “Confirmed exposure.” Exclusion does not mean zero impact. Approximate figures and maximum figures retain the qualifications in the original announcement.
The chart and its evidence
The left axis shows the number of breach cases; the right axis shows cumulative exposure counts by unit (in millions). Colored lines show the reported breach scale, including potential exposure and estimates. Buttons display the colored-line totals. Country, date, and other filters change which cases are included. Case details provide sources and adopted figures; the CSV provides unit-specific values for both reporting scopes.
Comparing with other statistics
Media reports may use different incidents, periods, units, and rules for including potential exposure. Matching the time period alone does not make the populations comparable. Country-level incident counts should not be used to compare security.