Skip to main content

LegalAgent AI Legal Lab

Data Breach & Cyberattack News

Data breaches, unauthorized access and service outages announced by companies and organizations in Japan, listed from their official announcements. Explore incident counts, reported exposure figures and a monthly chart.As of November 7, 2026

Listed incidents in numbers

Data as of 2026.11.07
Listed incidents
278 incidents
Incidents with confirmed leaks
131 incidents
Possible leaks / investigations
127 incidents
Incidents with service / business outages
130 incidents

Gross counts of exposed information

Reference sums excluding image metadata · 176 incidents

Information confirmed exposed
Approx. 271,831,140 reported items
Information potentially exposed
Approx. 259,552,988 reported items

Including image metadata

Information confirmed exposed
Approx. 938,231,140 reported items
Information potentially exposed
Approx. 259,552,988 reported items

Listed incidents by month

Choose a filter to update both the chart and the list. Select a monthly bar to jump to its incidents.

By the latest announcement listed for each incidentAll · 278 listed incidents
  1. April 20262
  2. May 20265
  3. June 20269
  4. July 20267
  5. August 202610
  6. September 202638
  7. October 2026149
  8. November 202658

2026

Listed incidents by month

November 2026

  1. Second notice: website partially reopened

    Club TourismOnline member data / travel website

    Unauthorized access on October 30 potentially exposed about 4.32 million internet-member records. On November 7 the company announced that safeguards and safety checks were complete and the website had reopened except for some pages.

    Official announcement: Club Tourism (Open external link)

    Possible leakUnauthorized accessThe company announced reopening of its website on November 7 except for some pages. The travel-memory photo-submission page remains suspended.

    Approx. 4.32 million recordsOnline members’ names, nationality, gender, birth dates, addresses, phone numbers, emails, member IDs and emergency contacts. Login passwords, passport, card and bank data are stated to be excluded.

    Timeline and sources (2)
    Timeline and sources
    1. First noticeOfficial announcement (Open external link)
    2. Second notice: website partially reopenedOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  2. Update: three card numbers additionally confirmed

    Prestige International (Prestige Core Solution)Business system for road-service intake and dispatch

    Prestige International detected unauthorized access to a group business system on October 29 and shut it down on October 30. On November 2 it announced that customer personal data handled by a group company under outsourcing contracts had been taken out, up to about 5.5 million records including duplicates.

    Official announcement: Prestige International (Prestige Core Solution) (Open external link)

    Leak confirmedUnauthorized accessThe system was shut down on October 30 after continued unauthorized access was found; road-service operations continue through alternative procedures.

    Up to approx. 5.5 million records (including duplicates)Road-service users’ names, addresses, contact, vehicle and service-request information and some bank-account data. Three card numbers were additionally confirmed on November 6 and are a subset of the maximum of about 5.5 million records. Deduplicated person counts and partner-company scope remain under review.

    Timeline and sources (2) · Related announcements (2)
    Timeline and sources
    1. Announcement (exchange filing)Official announcement (Open external link)
    2. Update: three card numbers additionally confirmedOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Nippon Rent-A-Car Service (outsourced road service) (Open external link) · Under investigationWhether its customers' data are included is under investigation (bank-account data reported as not included)
    2. Sompo Japan (auto-insurance inquiry and intake operations) (Open external link) · Possible leakAbout 65,000 records (policy data, inquiry history, roadside-assistance records, etc.)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-07

  3. Third report: online store and app functions suspended

    Ryohin KeikakuMUJI app and MUJI online store

    Ryohin Keikaku detected unauthorized external access to the MUJI app, blocked it and applied fixes. On October 30 it disclosed that up to about 27.26 million records (email, birth date and gender) may have leaked. Its November 4 second report said online-store users were also included, about 520,000 records also contained names, addresses and phone numbers, and card numbers and related data of about 1.09 million MUJI Card members obtained before July 2021, as well as partial card data of about 120 users, may also have been accessed. The November 6 third report announced precautionary suspension of the online store and most app functions.

    Official announcement: Ryohin Keikaku (Open external link)

    Possible leakUnauthorized accessOn November 6 all online-store functions and all MUJI app functions except the membership barcode were suspended. Reopening was planned within one to two days; physical stores operate normally.

    Up to approx. 27.26 million records; approx. 1.09 million MUJI Card records and others(1) Up to about 27.26 million MUJI app and online-store users, including former members: email address, birth date, gender and member ID; about 520,000 of them (so far) also include name, address and phone number. (2) About 1.09 million MUJI Card members who joined by July 2021: full card number, MUJI Card ID and birth date (about 345,000 cards still valid; cardholder name, expiry date and security code not included). (3) About 120 users who registered cards in the app or online store: first six and last two card digits and cardholder name. All may have been accessed externally. Some of the valid cards in (2) and the records in (3) were viewable together with user data in (1).

    Timeline and sources (5) · Related announcements (1)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Announcement (PDF)Official announcement (Open external link)
    3. Second report: wider scope and card data identifiedOfficial announcement (Open external link)
    4. Second report (exchange filing)Official announcement (Open external link)
    5. Third report: online store and app functions suspendedOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Credit Saison (MUJI Card issuer) (Open external link) · Possible leakAbout 1.09 million MUJI Card members (about 345,000 valid cards)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-07

  4. Breakdown corrected; total unchanged

    AraraEmail delivery service “Arara Message”

    Data leaked through unauthorized access on October 28–31, and all services were suspended on October 31. The November 6 third report confirmed exposure of 81,329,467 email addresses after deduplication across all environments.

    Official announcement: Arara (Open external link)

    Leak confirmedUnauthorized accessArara Message and ASP repica remain suspended, with no reopening date as of November 6. TKC has built a separate delivery infrastructure and is progressively restoring sending functions for individual systems.

    81,329,467 email addresses (deduplicated)The November 6 third report gives a confirmed leak count deduplicated across all environments: 34,285,087 email-only records and 47,044,380 with attributes such as names. About 380 customer companies, 61 shared-environment customers and their individual disclosures are not added. A same-day correction changes a breakdown figure, not the total.

    Timeline and sources (7) · Related announcements (22)
    Timeline and sources
    1. Leak and suspension announcedOfficial announcement (Open external link)
    2. Exchange filing (PayCloud Holdings)Official announcement (Open external link)
    3. Update on full suspensionOfficial announcement (Open external link)
    4. Second reportOfficial announcement (Open external link)
    5. Second report (exchange filing, PayCloud Holdings)Official announcement (Open external link)
    6. Third report: deduplicated leak countOfficial announcement (Open external link)
    7. Breakdown corrected; total unchangedOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. asoview (asoview! members) (Open external link) · Leak confirmed15,821,184 records (emails, member data, purchase data, etc.)
    2. TKC (Open external link) · Leak confirmedEmail addresses (scope still being classified). Some sending functions resumed by November 6; certain municipal functions are scheduled for November 10–11.
    3. Himeji City (online procedures portal, via TKC) (Open external link) · Possible leakWhether city-related data leaked is being checked
    4. Osaka City (online administrative system, via TKC) (Open external link) · Possible leakOnly email addresses may have been exposed; whether users' addresses were exposed is still being checked
    5. Osaka Gas (FitDish) (Open external link) · Leak confirmed34,489 email addresses
    6. Odakyu Travel (Open external link) · Leak confirmed63,006 email addresses; the relevant mailing period was corrected to October 10–30.
    7. Niigata City (e-NIIGATA online applications, via TKC) (Open external link) · Under investigationOnly email addresses may have been exposed; whether users' addresses were exposed is under investigation
    8. Bic Camera, Kojima and Sofmap (email newsletters) (Open external link) · Possible leakApprox. 14.9 million records across the group (email addresses, etc.)
    9. Yokohama City (online applications) (Open external link) · Possible leakScope corrected to email addresses only, excluding names. Email authentication and related functions remain suspended.
    10. Workman (online store newsletter) (Open external link) · Possible leakUp to approx. 1.45 million email addresses
    11. Hasegawa (email delivery via Arara repica) (Open external link) · Leak confirmed305 email addresses (emails sent October 10–31; finalized)
    12. JR Kyushu (condominium sales newsletter) (Open external link) · Possible leakUp to about 13,000 records (names and email addresses)
    13. Medica Publishing (emails sent via repica) (Open external link) · Leak confirmedEmail addresses (number of people being confirmed)
    14. Kashiwazaki City (email alert service) (Open external link) · Leak confirmedSubscriber email addresses (count under investigation; 5,364 subscribers as of November 4)
    15. Konaka (Samantha Thavasa group online shops and app, via Arara repica) (Open external link) · Leak confirmed434,414 email addresses
    16. Mitsui Fudosan (&BIZ newsletter, via contractor) (Open external link) · Leak confirmed133,323 email addresses
    17. Kagome (food-service newsletter, via repica) (Open external link) · Leak confirmed11,065 email addresses (October 13 mailing)
    18. Yamada Denki (Family Support FC Club, via contractor Fukuriko) (Open external link) · Possible leakUp to 7,640 email addresses
    19. Toyama Prefecture (energy-saving appliance campaign, via JTB Toyama) (Open external link) · Possible leak247 records (names and email addresses)
    20. Saitama Prefecture (hike and cycle stamp rally) (Open external link) · Possible leakNames and email addresses; affected count under review
    21. Saitama Prefecture (parks / Asoview users) (Open external link) · Possible leakNames, gender, birth dates, phone numbers, email addresses and related data; count undisclosed
    22. Setsunan University (UCARO) (Open external link) · Possible leakOnly email addresses registered for 2023–2026 admissions; 2027 admissions are excluded.

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-07

  5. Restart target and undetermined OEM schedule reiterated

    Rakus Light Cloudblastmail

    The company disclosed exposure of all customer contact and contract/payment information and some delivery lists. Its November 4 update identified exposure for 76 more contracts, bringing contracts with confirmed non-contract exposure to 421, all of which have been notified. It aims to reopen the main service around November 11; operations have not yet resumed.

    Official announcement: Rakus Light Cloud (Open external link)

    Leak confirmedUnauthorized accessThe management console, API and delivery remain suspended. The November 6, 1 p.m. update retains a target around November 11, subject to investigation and testing; OEM reopening remains undetermined.

    All customer-contract information; non-contract information exposed for 421 contracts421 counts contracts, not all exposed records or recipients. For the 76 contracts newly identified on November 4, no exposure of reader data (recipient addresses, customer lists, etc.) or email bodies has been confirmed. Overlap with the information of all customers cannot be separated. Customer disclosures are related information for the same incident.

    Timeline and sources (12) · Related announcements (30)
    Timeline and sources
    1. Announcement / service suspensionOfficial announcement (Open external link)
    2. Joint-reporting guidanceOfficial announcement (Open external link)
    3. Investigation and suspension continueOfficial announcement (Open external link)
    4. Additional exposure confirmed; investigation continuesOfficial announcement (Open external link)
    5. Reopening target announced; suspension continuesOfficial announcement (Open external link)
    6. Second round of joint/proxy PPC reportingOfficial announcement (Open external link)
    7. No new exposure found; restart target maintainedOfficial announcement (Open external link)
    8. No new exposure found; restart target maintainedOfficial announcement (Open external link)
    9. No new exposure found; restart target maintainedOfficial announcement (Open external link)
    10. Exposure found for 76 more contracts (421 in total); restart target maintainedOfficial announcement (Open external link)
    11. No new exposure found; restart target maintainedOfficial announcement (Open external link)
    12. Restart target and undetermined OEM schedule reiteratedOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. NHK Publishing (Shumi no Engei) (Open external link) · Leak confirmed126,525 records (unchanged in third report)
    2. ARTnews JAPAN (Open external link) · Leak confirmedAll subscribers’ email addresses (count not disclosed); names also exposed for those registered by May 2023
    3. Toyama Prefecture (Smart Lab TOYAMA) (Open external link) · Possible leak214 records
    4. Toyama Prefectural Civic Hall cultural association (Open external link) · Possible leakEmail addresses, names and member numbers; count undisclosed
    5. Horai (Open external link) · Possible leakUp to 75,140 people
    6. Nagoya Bank (Sompo Japan DC Securities) (Open external link) · Possible leakNotification recipients’ names and email addresses; count undisclosed
    7. Ministry of the Environment (Open external link) · Possible leakNewsletter and other mailing recipients; count undisclosed
    8. Kagoshima City (industry development) (Open external link) · Possible leakNo list-exposure notice had reached the contractor as of November 5; scope and impact remain under review.
    9. Kagoshima Fureai Sportsland (Open external link) · Possible leakUp to approximately 3,000 people
    10. Hiroshima City Industrial Promotion Center (Open external link) · Possible leak3,372 NEWS recipients and 1,052 network-news recipients; overlap unresolved
    11. Japanese Red Cross Society Tokyo Chapter (Open external link) · Possible leakNT NEWS mailing recipients; count undisclosed
    12. Tokyo Metropolitan Government (Open external link) · Leak confirmedUp to approximately 16,000 people
    13. giftee (Open external link) · Possible leakCount undisclosed; outside the 288 notified contracts as of October 23, with investigation continuing
    14. Shimonoseki City (inclusive-society program) (Open external link) · Possible leakSix people
    15. Shimonoseki City (employment programs) (Open external link) · Possible leakRegistrants’ and participants’ names and related details; count undisclosed
    16. Hobby Japan (Open external link) · Possible leakHobby Japan Web newsletter registration information; count undisclosed
    17. Advanced Education Organization, publishing division (Open external link) · Leak confirmedMailing-list email addresses; count undisclosed
    18. Azone International (Open external link) · Leak confirmedEmail addresses; number of people under investigation
    19. Tamiya (Open external link) · Possible leakCount undisclosed; outside the 288 notified contracts as of October 23, with investigation continuing
    20. Sannichi YBS company guidance (Open external link) · Leak confirmed4,433 people
    21. Sannichi Work (Open external link) · Leak confirmed607 people
    22. DD Town (Open external link) · Leak confirmed10,000 people
    23. Nagano Prefecture (Open external link) · Possible leakApproximately 1,200 Happiness Navi users, 2,900 Shukatsu NAGANO users and 200 farming-course participants
    24. Toho Holdings (eHealthcare) (Open external link) · Possible leakApproximately 8,000 physicians and 1,000 medical institutions; administrative URLs and other fields are subsets
    25. Niigata Nippo (Open external link) · Leak confirmedSome member data confirmed exposed; approximately 7,000 Salmon Project participants remain under investigation
    26. JAPEX (Open external link) · Under investigationNewsletter subscribers and investor-event invitees; counts under investigation
    27. Saitama Prefecture (senior-employment pledge companies) (Open external link) · Possible leakNames, emails and other data for about 2,900 companies
    28. Yamanashi Prefecture (government newsletter) (Open external link) · Possible leakAbout 1,000 subscribers possibly affected; staff names and other data confirmed exposed
    29. Fujicco (via a contractor) (Open external link) · Leak confirmedEmails and profile data of Fujicco Tsushin newsletter subscribers; count not disclosed
    30. Tokyo Metro (event email newsletter) (Open external link) · Leak confirmedApprox. 80,000 email addresses

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-07

  6. External forensic findings

    Daiichikosho

    The November 6 forensic findings confirmed malware on a contractor’s device and unauthorized external communication. The transmitted content and scope could not be identified; personal-data leakage or misuse has not been confirmed.

    Official announcement: Daiichikosho (Open external link)

    Possible leakUnauthorized access

    About 8,724,000 records

    Timeline and sources (3)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Note on SMS notices addedOfficial announcement (Open external link)
    3. External forensic findingsOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  7. Investigation findings and affected counts disclosed

    ROHTO Pharmaceutical

    A November 6 update on the September intrusion disclosed theft of customer-management data for 2,797,545 people and call recordings containing card numbers and expiry dates for 9,715 people. Telephone-system credentials were misused, and customer-management data was obtained through that system.

    Official announcement: ROHTO Pharmaceutical (Open external link)

    Leak confirmedUnauthorized access

    Customer-management data for 2,797,545 people; call recordings containing card data for 9,715 peopleCustomer-management records contain names, addresses and phone numbers, varying by person. Some call recordings include card numbers and expiry dates, but not security codes or authentication information. The 9,715 recording subjects are not added because overlap with customer-management subjects is unresolved.

    Timeline and sources (3)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Dedicated inquiry form addedOfficial announcement (Open external link)
    3. Investigation findings and affected counts disclosedOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  8. National Association of Local Government LotteriesOfficial lottery website and app

    The official lottery website and app were suspended on November 6 after unexpected password changes. Unauthorized third-party logins and possible viewing of member data were reported, but intrusion into servers/databases or export of data has not been confirmed.

    Official announcement: National Association of Local Government Lotteries (Open external link)

    Possible leakUnauthorized accessThe website and app remain suspended with no reopening date; retail sales continue.

    Affected count undisclosed

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  9. Japan Network Security AssociationInformation-security understanding check

    Unauthorized access detected on November 4 may have exposed administrator data, user IDs and hashed passwords from the night of October 30, according to the November 6 notice. Up to 15,128 records are in scope and the service is suspended.

    Official announcement: Japan Network Security Association (Open external link)

    Possible leakUnauthorized accessThe information-security understanding-check service is suspended.

    Up to 15,128 records

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  10. MizkanMizkan 365

    A November 6 announcement confirmed changes to 487 accounts following unauthorized access on October 30 and exposure of member IDs, email addresses and related information for 29 of those people. The issue was detected on November 2; the service was suspended and the vulnerability fixed.

    Official announcement: Mizkan (Open external link)

    Leak confirmedUnauthorized accessMizkan 365 is suspended while restoration proceeds. Mizkan’s shop and Fibee were also suspended as precautions from November 4.

    487 altered accounts; data exposure affecting 29 peopleThe 29 people are a subset of the 487 altered accounts. The 26 with point/campaign data are also a subset and are not added.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  11. Doutor CoffeeOnline shop

    A November 6 announcement disclosed unauthorized access to the shop administration interface on October 24–25 and possible export/viewing of 24,762 member records and nine delivery-address records. No password or card-data leak has been confirmed.

    Official announcement: Doutor Coffee (Open external link)

    Possible leakUnauthorized accessOnline-shop and subscription ordering are suspended; confirmed orders continue to be shipped.

    24,762 member records and 9 delivery-address records

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  12. Third report: exposed fields and continuing suspension

    NTT DocomoDocomo Online Shop and My docomo

    Unauthorized access was detected on November 4; on November 5 Docomo confirmed some customer data had leaked, with up to about 300,000 records in scope. Its November 6 third report specified additional data fields and said no further leak had been detected after access was blocked.

    Official announcement: NTT Docomo (Open external link)

    Leak confirmedUnauthorized accessProcedures on Docomo Online Shop and My docomo remain suspended; no restoration date was set as of 6 p.m. on November 6.

    Up to about 300,000 recordsThe November 6 third report identified names, birth dates, addresses, phone numbers, email addresses, identity-document numbers and contract/plan data. Some records also contain legal-representative, employer, bank-account or childcare-program data. The maximum remains about 300,000 records; subsets are not added.

    Timeline and sources (3)
    Timeline and sources
    1. Emergency maintenance announcedOfficial announcement (Open external link)
    2. Second report: customer data leak confirmedOfficial announcement (Open external link)
    3. Third report: exposed fields and continuing suspensionOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  13. Related update

    SMBC Consumer FinanceSystem used for guaranteeing card loans and other products of partner financial institutions

    SMBC Consumer Finance announced on November 5 that on November 2 it detected unauthorized access to the system used for its guarantee business with regional banks, credit unions, online banks and other partners, and blocked access the same day. During its investigation it confirmed that data sent externally contained customers’ personal information, and it put the number of customers whose data leaked at up to 320,118.

    Official announcement: SMBC Consumer Finance (Open external link)

    Leak confirmedUnauthorized accessThe guarantee system has been suspended for safety checks and maintenance (as of November 5). Partner Hokuyo Bank suspended new applications and limit increases for its Super Arca card loan.

    Up to 320,118 peopleNames, gender, dates of birth, addresses, home and mobile phone numbers, email addresses, driver’s licence numbers, employer information (phone numbers, annual income, etc.) and contract information (financial institution codes, customer numbers, guarantee amounts, guarantee start dates, etc.). Images of identity documents such as driver’s licences are not included. Affected people will be contacted after the scope is identified.

    Timeline and sources · Related announcements (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Hokuyo Bank (Super Arca card loan) (Open external link) · Leak confirmedSome data of borrowers and applicants (count not disclosed)
    2. Resona Bank, Kansai Mirai Bank and Minato Bank (Open external link) · Leak confirmed139, 5,793 and 3 former-loan-customer records (subsets of the main incident)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-07

  14. Second report: scope and scale identified

    Nomura Investor RelationsIR information service for institutional investors and analysts “Kikan Navi”

    Unauthorized access to Kikan Navi was detected on November 2. The November 6 second report disclosed leaked information on about 2,000 institutional investors/analysts, about 250 former employees and other data.

    Official announcement: Nomura Investor Relations (Open external link)

    Leak confirmedUnauthorized accessKikan Navi and MIR@I on the same server remain suspended. MIR@I is suspended as a precaution; no reopening date is set.

    About 2,000 institutional investors/analysts and about 250 former employees, plus unquantified dataNames, email addresses and related information. Listed-company executives’ names and positions are also included, without a published count. Unauthorized access to MIR@I has not been confirmed.

    Timeline and sources (3)
    Timeline and sources
    1. Emergency maintenance (suspension) noticeOfficial announcement (Open external link)
    2. Unauthorized access and leak announcedOfficial announcement (Open external link)
    3. Second report: scope and scale identifiedOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  15. Customer-data exposure and count disclosed

    Aioi Nissay Dowa InsurancePolicyholder page and other customer services

    Suspicious access was detected on the night of November 2 and customer services were suspended from November 3. On November 6 the company announced that its investigation confirmed exposure of about 444,000 customer records.

    Official announcement: Aioi Nissay Dowa Insurance (Open external link)

    Leak confirmedUnauthorized accessAs of 12:00 on November 5, the policyholder page, One Day Supporter, e-travel overseas travel insurance, My Agent, the corporate customer web service, e-G1 and online accident reporting were suspended. The company says other services may also be suspended.

    About 444,000 recordsPolicyholder data and related information. Three records containing the last four card digits and 19 containing partial bank-account information are subsets and are not added.

    Timeline and sources (4)
    Timeline and sources
    1. Service suspension announcedOfficial announcement (Open external link)
    2. Update (suspended services)Official announcement (Open external link)
    3. Update (more services suspended)Official announcement (Open external link)
    4. Customer-data exposure and count disclosedOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  16. Customer-data exposure and count disclosed

    Mitsui Sumitomo InsurancePolicyholder page and other customer services

    Suspicious access was detected on the night of November 2 and customer services were suspended from November 3. On November 6 the company announced that its investigation confirmed exposure of about 37,000 customer records.

    Official announcement: Mitsui Sumitomo Insurance (Open external link)

    Leak confirmedUnauthorized accessAs of 12:00 on November 5, the policyholder page, 1DAY insurance, the “Net de Hoken” travel, golf and cycle products, My Agent, the disaster alert service, the hail emergency alert, the corporate customer web service, e-G1, Jidosha Kantan Net and online accident reporting were suspended. The company says other services may also be suspended.

    About 37,000 recordsPolicyholder data and related information. The company states that credit-card and bank-account information is not included.

    Timeline and sources (4)
    Timeline and sources
    1. Service suspension announcedOfficial announcement (Open external link)
    2. Update (suspended services)Official announcement (Open external link)
    3. Update (more services suspended)Official announcement (Open external link)
    4. Customer-data exposure and count disclosedOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  17. Investigation completed; no leak confirmed

    TV TOKYO DirectOnline shop “Tele-To Mart”

    TV Tokyo Mart was closed after unauthorized access on November 2. On November 6 the company announced completion of its investigation, which found no confirmed personal/card-data leak or unauthorized logins.

    Official announcement: TV TOKYO Direct (Open external link)

    Leak not confirmedUnauthorized accessThe site was urgently suspended at 3:53 a.m. on November 2. Web orders are stopped; call-center orders are still accepted.

    No personal-data leak confirmed so farThe investigation was completed, as announced on November 6. It found no confirmed leak of personal or card data and no confirmed unauthorized logins.

    Timeline and sources (2)
    Timeline and sources
    1. Unauthorized access and site closure announcedOfficial announcement (Open external link)
    2. Investigation completed; no leak confirmedOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  18. Compensation process for unauthorized-trading losses begins

    GMO InternetOnamae.com Desktop Cloud

    On October 27 the company confirmed that a party believed to be the attacker had published what it claimed was customer data, and it is investigating authenticity and scope. Report 14 on October 28 said analysis of submitted devices found no malware or ransomware traces; on October 29 it said information that may identify the perpetrator would be provided to police. On October 30 it began contacting customers about compensation and an alternative service; no restoration of the desktop cloud has been announced. On November 6, individual notices and the compensation process for unauthorized-trading losses were announced.

    Official announcement: GMO Internet (Open external link)

    Possible leakUnauthorized accessAll plans progressively suspended from 04:00 on October 21.

    26,739 potentially affected servers; exposed-data count undisclosedServer counts are not converted into leaked-information counts.

    Timeline and sources (13)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Third report / credential investigationOfficial announcement (Open external link)
    3. Seventh report / examination of customer devices beginsOfficial announcement (Open external link)
    4. Tenth report / attacker publication identifiedOfficial announcement (Open external link)
    5. Thirteenth report / attacker-site domain suspendedOfficial announcement (Open external link)
    6. Report 14: no malware traces on submitted devicesOfficial announcement (Open external link)
    7. Response policy disclosed to investorsOfficial announcement (Open external link)
    8. Report 15: information on the perpetrator provided to policeOfficial announcement (Open external link)
    9. Report 16: tip counts publishedOfficial announcement (Open external link)
    10. Compensation procedure and alternative service notices begunOfficial announcement (Open external link)
    11. Update to report 16: tips received (822 in total)Official announcement (Open external link)
    12. Update to report 16: tips received (839 in total)Official announcement (Open external link)
    13. Compensation process for unauthorized-trading losses beginsOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  19. Update: additional personal-data exposure

    Japan External Trade Organization (JETRO)Affected websites

    JETRO previously disclosed 743 exposed records following the October website intrusion. A November 6 update confirmed additional exposure involving event contacts, staff and contractors, and said identifiable affected contacts had been notified.

    Official announcement: Japan External Trade Organization (JETRO) (Open external link)

    Leak confirmedUnauthorized accessWebsites provisionally reopened; some search and authenticated content remain unavailable.

    Previously reported 743 records; an additional 142, 9,252 and 19 recordsAdditional groups comprise 142 event-calendar contacts, 9,252 current/former staff records and 19 maintenance/production-company contacts, including names and email addresses. The separate e-Venue incident is excluded.

    Timeline and sources (3)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Provisional reopeningOfficial announcement (Open external link)
    3. Update: additional personal-data exposureOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  20. Scheduled FutureShop restart and Shopify authentication change

    WASABI (October 16–17 incident)WASABI SWITCH administration

    WASABI disclosed theft of order and other data through a separate intrusion on October 16–17. Its October 20 sixth report said encryption of store-specific authentication and related information was completed around 05:00 that day. It requested registration of changed passwords; integration with some marketplaces remains suspended until API tokens are reissued.

    Official announcement: WASABI (October 16–17 incident) (Open external link)

    Leak confirmedUnauthorized accessIntegration with eBay, Amazon and Walmart has been suspended since around 19:00 on October 20 until each store reissues its API tokens. SpeedPAK integration resumed on November 2 and BUYMA VINTAGE integration on November 5. WASABI corrected its guidance of around October 20: DHL does not require reauthentication. On November 6, FutureShop integration was scheduled to resume from November 9. Shopify integration is conditional on stores obtaining new tokens after the authentication change that day.

    Number under investigationA separate route from the October 14 incident. Scope and overlap remain unresolved; no numerical amount counted.

    Timeline and sources (9)
    Timeline and sources
    1. Separate access route disclosedOfficial announcement (Open external link)
    2. Third report / theft of order and account dataOfficial announcement (Open external link)
    3. Fourth report / planned temporary removal of transaction dataOfficial announcement (Open external link)
    4. Fifth report / PHP disabled and authentication measuresOfficial announcement (Open external link)
    5. Sixth report / encryption completed and external integration suspendedOfficial announcement (Open external link)
    6. Investigation results and current responseOfficial announcement (Open external link)
    7. SpeedPAK integration resumed; DHL guidance correctedOfficial announcement (Open external link)
    8. BUYMA VINTAGE integration resumedOfficial announcement (Open external link)
    9. Scheduled FutureShop restart and Shopify authentication changeOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  21. Report 26: API integration resumed

    ArcadiaSpeeCAN RAIDEN, NET119 and 119RAIDEN

    Following unauthorized access and possible exposure, services were suspended and progressively restored. Report 26 on November 6 announced resumption of external API integration that had been suspended since October 22.

    Official announcement: Arcadia (Open external link)

    Possible leakUnauthorized accessReport 26 on November 6 announced resumption of external-system API integration. Customer-side configuration is involved, with individual notices to affected users.

    About 3,136,000 RAIDEN email addresses, 9,020 NET119 records and 97,000 119RAIDEN email addressesThe October 16 eleventh report corrected NET119 to 9,020 records. Phone/fax counts and customer subsets are not added.

    Timeline and sources (13) · Related announcements (4)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Expanded scope and correctionsOfficial announcement (Open external link)
    3. All services restored / ninth reportOfficial announcement (Open external link)
    4. Eleventh report / NET119 scope correctionOfficial announcement (Open external link)
    5. Twelfth report / intrusion and response chronologyOfficial announcement (Open external link)
    6. Thirteenth report on proxy reportingOfficial announcement (Open external link)
    7. Reports 14–18 / malicious mail and lifting of restrictionsOfficial announcement (Open external link)
    8. Reports 19–20 / API integration suspended and authentication strengthenedOfficial announcement (Open external link)
    9. Reports 21–22 / investigation report and authenticationOfficial announcement (Open external link)
    10. Report 23: proxy breach report filedOfficial announcement (Open external link)
    11. Report 24: two-factor login addedOfficial announcement (Open external link)
    12. Report 25: cause of the fraudulent emails and responseOfficial announcement (Open external link)
    13. Report 26: API integration resumedOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Yokosuka City (Open external link) · Possible leakDisaster email: 47,065 people; crime-prevention email: 10,848; fax: 996; phone: 11. Four services suspended
    2. Karatsu City (Open external link) · Possible leakInformation-mail registration data; number undisclosed. New registrations suspended.
    3. Kinokawa City (Open external link) · Possible leakCount undisclosed; municipal email delivery resumed
    4. Shimonoseki City (Net119) (Open external link) · Possible leak42 call and practice records, plus 15 staff records

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-07

  22. Reviewed findings: leak affecting 27,139 members confirmed

    Japan Post Group Union (JP Union)Email newsletter system used until around 2019

    A November 6 update confirmed that information on 27,139 union members had leaked following unauthorized access to a former newsletter system operated until around 2019.

    Official announcement: Japan Post Group Union (JP Union) (Open external link)

    Leak confirmedIncident at a vendor

    27,139 peopleRegional-branch names, member names and numbers, gender, birth dates and email addresses. Addresses, phone numbers, passwords and bank-account data are not included. This reviewed person count replaces the initial mailing-list estimate of over 40,000 entries.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Reviewed findings: leak affecting 27,139 members confirmedOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  23. Additional potentially exposed fields

    Doutor CoffeePart of internal systems (employee data)

    Doutor detected unauthorized access to an internal system on October 20 and disclosed on October 26 that personal data of 951 employees and former employees of four stores, including bank account numbers, may have been viewed and leaked.

    Official announcement: Doutor Coffee (Open external link)

    Possible leakUnauthorized access

    951 employees and former employees951 current and former employees at four stores. The November 6 update adds employee numbers, gender, nationality, employment/work/social-insurance details, relatives’ names, relationships and addresses, and bank-account data.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Additional potentially exposed fieldsOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  24. Related update

    FancrewMonitor portal “Fancrew”

    Fancrew announced on November 2 that at about midnight on November 1 it detected unusual access, found unauthorized access to a member-data API and shut down the system at 10:43 that day. Its second report on November 4 said member data had leaked between October 30 and 31 and put the number affected at 1,030,741 records.

    Official announcement: Fancrew (Open external link)

    Leak confirmedUnauthorized accessViewing and all functions of Fancrew have been suspended since 10:43 on November 1. The second report scheduled maintenance until 11:00 on November 5, but no reopening announcement has been confirmed.

    1,030,741 monitor member recordsMember IDs, email addresses, hashed passwords, names, gender, postcodes and the last four digits of phone numbers. Former members are not included. No unauthorized logins or point exchanges using the leaked data have been confirmed. Partner Point Town announced that, for its linked users, Fancrew-issued IDs, gender and first-link dates leaked.

    Timeline and sources (2) · Related announcements (1)
    Timeline and sources
    1. First report: system suspendedOfficial announcement (Open external link)
    2. Second report: number affected disclosedOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. GMO Media (Point Town monitor content) (Open external link) · Leak confirmedFancrew-issued IDs, gender and first-link dates of linked users (count not disclosed)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-06

  25. Second report: possible exposure of data on about 7.7 million people

    Iris Plaza (Iris Ohyama online store)Iris Plaza e-commerce site

    On October 28 Iris Plaza found suspicious files in an external cloud service and shut down the Iris Plaza site and related systems, announcing unauthorized access on October 29. Its November 5 second report said personal data on about 7.7 million people stored in that cloud (about 5.8 million members and 1.9 million non-members) may have been viewed or acquired. The actual number exposed is under investigation; card data were not stored there.

    Official announcement: Iris Plaza (Iris Ohyama online store) (Open external link)

    Possible leakUnauthorized accessIris Plaza and related systems have been shut down since October 28. From the same day the SIMPLE STYLE site and Iris Tech Service’s appliance-subscription and delivery/installation sites were also suspended, with new applications stopped. Stores on other marketplaces remain available. No reopening date had been set as of November 5.

    About 7.7 million people (about 5.8 million members and 1.9 million non-members)Total personal data stored in an external cloud service. The company has confirmed it may have been viewed or acquired; the actual number exposed and people affected remain under investigation. Member data (including former members) covers names, addresses, phone numbers, email addresses, gender, passwords (encrypted; excluding former members) and dates of birth; non-member data (purchasers without accounts, campaign entrants, etc.) covers names, addresses, phone numbers and email addresses. Fields vary by registration. Card data were not stored in that cloud and were unaffected, the company says.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / site suspendedOfficial announcement (Open external link)
    2. Second report: possible exposure of data on about 7.7 million peopleOfficial announcement (Open external link)

    Sources checked: 2026-11-06

  26. Fifth report: web donations to resume in stages from 12:00 on November 6

    TrustbankFurusato Choice-related services

    The October 23 update reports additional fields for five people within the previously disclosed 4,454,097 member records. These include point/donation histories and card last-four digits, cardholder names and expiry dates, with overlap between fields.

    Official announcement: Trustbank (Open external link)

    Leak confirmedUnauthorized accessThe donation management system for municipalities and suppliers resumed on October 26 and the partner-site integration on October 28. The fifth report on November 5 said web donations on Furusato Choice would resume in stages from 12:00 on November 6; the app and Choice Pay are to resume later.

    4,454,097 recordsThe five people with additional exposed fields are a subset of the previously disclosed 4,454,097 records.

    Timeline and sources (7)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. UpdateOfficial announcement (Open external link)
    3. Second report / additional data fieldsOfficial announcement (Open external link)
    4. Third report: management system for municipalities resumedOfficial announcement (Open external link)
    5. FAQ for donors publishedOfficial announcement (Open external link)
    6. Fourth report: partner-site integration resumedOfficial announcement (Open external link)
    7. Fifth report: web donations to resume in stages from 12:00 on November 6Official announcement (Open external link)

    Sources checked: 2026-11-06

  27. Correction/addition to the third report

    Helpfeel

    The October 21 final forensic report attributed entry to a flaw in Helpfeel’s image-conversion processing. Reported user-information and metadata counts remain unchanged, while viewing or acquisition of 432 images belonging to 133 users was additionally confirmed. Service resumed on September 27, but owner-approved resharing of earlier images will remain permanent.

    Official announcement: Helpfeel (Open external link)

    Leak confirmedUnauthorized accessResumed September 27; earlier images remain subject to viewing and sharing restrictions

    About 23.62 million user records, 666.4 million metadata records and 432 imagesThe 432 images belonged to 133 users. Metadata comprises about 490 million, 2.4 million and 174 million records. Counts include overseas usage and are not unique people. The 432 images and 133 users are not added to the reference sums because their correspondence with already counted data is unresolved. A November 5 correction said the 2.4 million records cover images uploaded mainly during about two days from January 1, 2016 and from January 1, 2020 (about 0.07% of all images), and that the about 174 million records relate to about 1.12 million accounts, of which about 57,000 have been closed.

    Timeline and sources (5)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Announcement / updateOfficial announcement (Open external link)
    3. Service resumption notice, updatedOfficial announcement (Open external link)
    4. Third report / investigation findingsOfficial announcement (Open external link)
    5. Correction/addition to the third report (periods and account counts)Official announcement (Open external link)

    Sources checked: 2026-11-06

  28. Kyushu Electric Power Transmission and DistributionSystems holding power-usage data (power usage and charges inquiry service)

    Kyushu Electric Power Transmission and Distribution announced on November 5 that on October 30 it detected unusual errors in a system, found possible unauthorized access and made an emergency shutdown of the system. Server log analysis showed that 4,139 power-usage records may have leaked externally. Power supply is not affected, it says.

    Official announcement: Kyushu Electric Power Transmission and Distribution (Open external link)

    Possible leakUnauthorized accessThe system has been disconnected from the network, and the power usage and charges inquiry web service for registered customers on outlying islands and customers with power-sales contracts on the Kyushu mainland is suspended. Restoration was under consideration as of November 5.

    4,139 power-usage recordsConsumption data (monthly and 30-minute values) with demand-side supply point numbers, and sales-of-power data (monthly and 30-minute values) with generation-side receiving point numbers. Names, addresses, phone numbers, email addresses, bank details and other contract information are not included, the company says.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-06

  29. Third report and service restart

    MoiLive streaming service “TwitCasting”

    Moi announced on October 28 that at about 10:30 that day it detected a system anomaly and traces of unauthorized external access, and made an emergency suspension of TwitCasting, its corporate site and other services. Its second report on October 29 said traces of external access to a total of seven personal-data records before the shutdown had been confirmed. Its third report on November 5 said no further leak of personal data beyond the seven records had been found so far and announced a phased restart of services.

    Official announcement: Moi (Open external link)

    Leak confirmedUnauthorized accessServices were suspended from about 10:40 on October 28. The corporate site reopened on October 29, and the web version reopened on November 4 with recorded viewing, revenue payout requests and Premier ticket sales and purchases. Live streaming and viewing are scheduled to resume partly on November 6 and fully on November 11. The apps will resume in stages after updated versions with security measures are released (as of November 5).

    7 personal-data records (scope and scale of the server log data under investigation)The seven records with confirmed traces of external access are one record of a card expiry date and encrypted cardholder name, and six records of email addresses, activity history and similar data. The company says it does not hold card numbers or security codes. Separately, access to server log data partly containing account IDs and email addresses was confirmed; its scope and scale were still under review as of November 5.

    Timeline and sources (3)
    Timeline and sources
    1. First report (exchange filing)Official announcement (Open external link)
    2. Second report (exchange filing)Official announcement (Open external link)
    3. Third report and service restart (exchange filing)Official announcement (Open external link)

    Sources checked: 2026-11-06

  30. Partial reopening from November 6

    Good Smile CompanyGood Smile Company official shop

    Unauthorized access on October 19-22 led to repeated viewing of member data, and on October 28 the company found malicious code on the card payment page (October 21 13:55 to October 23 7:00). Notices on October 29-30 disclosed possible exposure of full card data for 2,800 people, last four digits and expiry for 402,466 cards and order data for 5,356 people. The online shop remains closed.

    Official announcement: Good Smile Company (Open external link)

    Leak confirmedUnauthorized accessThe official shop is closed. On November 5 the company announced that the shop would reopen from November 6 for product browsing only. My Account, new registrations, new orders, adding to cart and watch lists will resume after the third-party investigation and safeguards are completed; no date has been set.

    Full card data possibly exposed for 2,800 people; last four digits etc. for 402,466 cards; order data for 5,356 people (all possible)The number of people behind the 402,466 cards is still being confirmed. Up to 202 of 7,774 orders from 5,356 customers were viewed but cannot be identified. The 384 ordering customers and 185 card-change customers are subsets of the 2,800. Overlap between groups is not disclosed. Only the largest group, 402,466 cards, is used in the totals.

    Timeline and sources (6)
    Timeline and sources
    1. Unauthorized viewing confirmed / shop closedOfficial announcement (Open external link)
    2. Second report (update to first notice)Official announcement (Open external link)
    3. Third report: malicious code found on payment pageOfficial announcement (Open external link)
    4. Fourth report: partial correction and Q&AOfficial announcement (Open external link)
    5. External support for reopening announcedOfficial announcement (Open external link)
    6. Partial reopening from November 6 (product browsing only) announcedOfficial announcement (Open external link)

    Sources checked: 2026-11-06

  31. Phone notifications begin for people whose names and phone numbers only may be affected

    BUSINESS TECAshikaga funeral-hall reservation system

    Unauthorized database queries and inserted notices were detected on October 15. On October 18, BUSINESS TEC reported possible exposure of about 8,800 people’s data and suspension of the system. Data types and scope remain under investigation; reopening depends on safety checks.

    Official announcement: BUSINESS TEC (Open external link)

    Possible leakUnauthorized accessReservation system suspended; no reopening date announced.

    About 8,800 people

    Timeline and sources (3)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Individual notices to affected people begunOfficial announcement (Open external link)
    3. Phone notifications begin for people whose names and phone numbers only may be affectedOfficial announcement (Open external link)

    Sources checked: 2026-11-06

  32. Exchange filing

    Ashita no Team (subsidiary of Wellness Communications; provider Lafool)Organizational survey system “Ashita no Survey” (OEM-supplied by Lafool)

    Ashita no Team announced on November 4, followed by an exchange filing by its parent Wellness Communications on November 5, that Lafool, the OEM provider of the Ashita no Survey service it sells, detected suspicious access to its system environment on October 27, and reported that data on 209 people at three client companies were confirmed as improperly obtained.

    Official announcement: Ashita no Team (subsidiary of Wellness Communications; provider Lafool) (Open external link)

    Leak confirmedIncident at a vendor

    Data on 209 people at three client companiesItems include names, departments, employee numbers, survey answers, short-survey results and stress-check results. The figures are based on a report from the provider Lafool and may change or grow. No unauthorized access to the systems of Ashita no Team or Wellness Communications has been found.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement (Ashita no Team)Official announcement (Open external link)
    2. Exchange filing (Wellness Communications)Official announcement (Open external link)

    Sources checked: 2026-11-05

  33. Update

    Taito City (vendor Travelzip)Tourism site “TAITO Odekake Navi” and the “Tsutaju Yukari no Chi Taito-ku” site

    Taito City announced on October 23 that the server of Travelzip, the vendor that builds and runs its tourism sites, suffered unauthorized access from the night of October 22 to the morning of October 23 and that personal data of site users and others leaked. Updates on October 28 and 29 gave the numbers affected on the two sites, and a November 5 update said data from the closed Tsutaju site had remained on the server in a non-public state.

    Official announcement: Taito City (vendor Travelzip) (Open external link)

    Leak confirmedIncident at a vendor

    387, 715, 52 and 93 people (four groups)On TAITO Odekake Navi, 387 photo-download applicants (organization, name, email, phone, purpose and IP address), 715 people who requested materials or made inquiries (organization, name, address, email, phone and inquiry content) and 52 site-operation contacts; on the Tsutaju site, 93 people who made inquiries (name, email, address, phone, inquiry content and other data). The scope was finalized on October 26.

    Timeline and sources (5)
    Timeline and sources
    1. Announcement (TAITO Odekake Navi)Official announcement (Open external link)
    2. Announcement (Tsutaju site)Official announcement (Open external link)
    3. Update (TAITO Odekake Navi figures)Official announcement (Open external link)
    4. Update (Tsutaju site)Official announcement (Open external link)
    5. Update (Tsutaju site: cause and next steps)Official announcement (Open external link)

    Sources checked: 2026-11-06

  34. Investigation update: revised counts and dedicated hotline

    and ST HoldingsBusiness servers

    and ST HD detected unauthorized access to several business servers on October 22 and on October 23 disclosed possible exposure of customer, business-partner and employee data. On November 4 it revised possibly exposed customer records to about 2.74 million and said about 24,000 employee records may also have been exposed. It began notifying affected people and opened a dedicated hotline; stores and the web store operate normally.

    Official announcement: and ST Holdings (Open external link)

    Possible leakUnauthorized accessStores and the web store remain available; point use and some internal systems are suspended.

    About 2.74 million customer records; about 10,000 business contacts; about 24,000 employee recordsCustomer data: name, birth date, gender, address, phone number, email and member ID (no payment data or passwords). Employee data cover social-insurance enrollees from June 2013 to November 2022, including some former employees: basic details and social-insurance calculation data, with no My Number data or special-care personal information. The approx. 10,000 business contacts are the October 23 figure.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Investigation update: revised counts and dedicated hotlineOfficial announcement (Open external link)

    Sources checked: 2026-11-05

  35. UchicomiServer of the real-estate site “Uchicomi!”

    Uchicomi announced on November 4 that a failure of its managed server on July 6, after which it investigated and disconnected systems, turned out to be a ransomware attack in which a third party encrypted and stole some files on the server, and that member data of 142,591 accounts may have leaked.

    Official announcement: Uchicomi (Open external link)

    Possible leakRansomware

    Member data of 142,591 accountsMember data that may have been affected. Items are names, email addresses, birth dates, gender, addresses and phone numbers, depending on the member. The company says it holds no card data.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-05

  36. Reopening update

    2nd RetailingInternal systems (2nd STREET, GEO and other apps and web services)

    2nd Retailing confirmed third-party unauthorized access to internal systems on October 15 and suspended 2nd STREET, GEO and other apps and web services from the 17th. Its October 19 second report found no sign of suspicious connections to database servers and no external leak of personal data; some services resumed on October 29.

    Official announcement: 2nd Retailing (Open external link)

    No external leak foundUnauthorized accessApps and web services were suspended from 21:00 on October 17. Most reopened on October 29, GEO Arekore Rental on November 2, and home-delivery rental and the GEO Mobile UQ mobile online store on November 4. No reopening date is set for GEO Online Store, GEO Mobile Online or 2nd STORAGE.

    No external leak of personal or confidential data foundThe source does not disclose an information count.

    Timeline and sources (4)
    Timeline and sources
    1. First report / suspensionOfficial announcement (Open external link)
    2. Second report / findingsOfficial announcement (Open external link)
    3. Restart status (services resumed October 29; GEO Arekore Rental resumed November 2)Official announcement (Open external link)
    4. Reopening update (home-delivery rental and GEO Mobile UQ mobile online store reopened)Official announcement (Open external link)

    Sources checked: 2026-11-05

  37. Final report: investigation complete

    Link StationTicketing service GETTIIS (via Gettii-Lite)

    On October 18 Link Station found that GETTIIS member data had been obtained by exploiting a vulnerability in its Gettii-Lite event-registration service. Its October 20 second report gave leaked counts by item, including 317,971 member IDs, and its November 4 final report said the investigation was complete and the counts were unchanged.

    Official announcement: Link Station (Open external link)

    Leak confirmedUnauthorized access

    317,971 member IDs and other items (counted per item)Counts are per data item, not people: 311,451 hashed passwords, 29,515 encrypted card-related records (first and last four digits and others), 309,759 names, 309,668 phone numbers and 311,426 emails, among others.

    Timeline and sources (3)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)
    3. Final report: investigation complete (counts unchanged)Official announcement (Open external link)

    Sources checked: 2026-11-05

  38. Third report: count refined to 39,505; dedicated hotline

    Yakult HonshaCorporate website (inquiry forms, school-meal site and others)

    Yakult found unauthorized access to its website on October 26 and suspended its functions. Its October 30 second report confirmed leakage of about 40,000 personal records; the November 4 third report refined the count to 39,505 and added that cosmetics-campaign entrants' data were included. The website remains suspended.

    Official announcement: Yakult Honsha (Open external link)

    Leak confirmedUnauthorized accessWebsite functions suspended since October 26; as of November 4 the suspension continues for investigation and safety checks.

    39,505 records31,781 email-inquiry records, 5,698 school-lunch site members (including encrypted passwords), 1,613 press inquiries, 354 web entrants to a cosmetics campaign and the names of 59 employees who handled inquiries.

    Timeline and sources (3)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    2. Second report / exchange filingOfficial announcement (Open external link)
    3. Third report: count refined to 39,505; dedicated hotlineOfficial announcement (Open external link)

    Sources checked: 2026-11-05

  39. Final report: investigation results

    ApplyNow (Kichiri Holdings subsidiary)

    Kichiri disclosed on September 9 unauthorized access to its subsidiary ApplyNow's recruiting services. Its November 4 final report said an intruder exploited a vulnerability in an internal data-analysis tool and bulk-extracted the databases on September 7, leaking personal data of 396,920 applicants, contract signers and corporate users; for 30,067 people who signed employment contracts via the e-contract service, My Number and other data were included.

    Official announcement: ApplyNow (Kichiri Holdings subsidiary) (Open external link)

    Leak confirmedIncident at a vendor

    396,920 peopleNames, phone numbers, email addresses and other data of applicants, contract signers and corporate users. The 30,067 people who signed employment contracts via ApplyNow Sign include, for some, My Number (number only), bank account data, basic pension numbers and residence-card numbers. ID-document images, interview videos and card data are not included.

    Timeline and sources (2) · Related announcements (1)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Final report: investigation results (396,920 people)Official announcement (Open external link)
    Related announcements (customers and principals)
    1. Wondertable (Open external link) · Leak confirmedNumber not disclosed

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-05

  40. Second report

    BasicMarketing platform “ferret One”

    Basic announced on October 27 that on October 26 it found a third party had improperly created an account on an internal admin screen, obtained non-public page content of clients and logged in without authorization. Its November 4 second report said 4,317 login email addresses and related data and 16,970 inquiry and other personal records of three clients were found to have been viewed or taken. The exploited flaws were fixed by October 30.

    Official announcement: Basic (Open external link)

    Leak confirmedUnauthorized access

    4,317 login email addresses and related data; 16,970 inquiry and other personal records of three client companiesThe 4,317 records are ferret One users’ login email addresses and site names. The 16,970 records are 16,968 lead and inquiry records (names, contact details, etc.; de-duplicated) of one client and one inquiry record each of two other clients. Separately, non-public page content of four clients, containing no personal data, was viewed or taken. Login passwords and payment data are not confirmed as viewed or taken.

    Timeline and sources (4)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    2. First report (exchange filing)Official announcement (Open external link)
    3. Second reportOfficial announcement (Open external link)
    4. Second report (exchange filing)Official announcement (Open external link)

    Sources checked: 2026-11-05

  41. Deletion of former members' data announced

    Aidma Holdings (Mamaworks)Remote-work job site “Mamaworks”

    After police reported that data said to be the Mamaworks member list had been uploaded online, an investigation confirmed on October 1 unauthorized access through a system-configuration vulnerability. The operator announced on October 20 that members’ personal data may have leaked.

    Official announcement: Aidma Holdings (Mamaworks) (Open external link)

    Possible leakUnauthorized access

    Count not disclosedNames, birth dates, gender, phone numbers, addresses, emails, career history and password hashes (items vary by member).

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Deletion of former members' data announcedOfficial announcement (Open external link)

    Sources checked: 2026-11-05

  42. Developer's findings: no evidence of malicious activity on this store

    SHIPS CYCLE MARKET (app vendor Swym)External app “Swym Wishlist Plus” (wishlist feature)

    On October 22 the store disclosed that, after unauthorized access to the developer of the Swym Wishlist Plus app used for its wishlist feature, malicious code redirecting to fake checkout pages may have loaded on some shops using the app. On November 4 it reported the developer's findings: no evidence of malicious activity on this store for the October 14-15 event, and no impact from the event after October 19. The wishlist feature remains unavailable.

    Official announcement: SHIPS CYCLE MARKET (app vendor Swym) (Open external link)

    Leak not confirmedIncident at a vendor

    Developer's investigation found no evidence of malicious activity on this storeFrom 19:06 on October 14 to about 1:32 on October 15, malicious code redirecting to a fake checkout may have loaded on some shops using the app; customers may have entered card details on the fake site. No data were taken from the shop’s database. The wishlist feature is suspended as the vendor’s precaution.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Developer's findings: no evidence of malicious activity on this storeOfficial announcement (Open external link)

    Sources checked: 2026-11-05

  43. Joint reporting to the PPC opened for customers

    Studio

    Studio disclosed possible exposure of account data, CMS and form content, and external-service credentials following unauthorized access on September 30–October 1. Actual acquisition remains unconfirmed but is assumed for response purposes; the access route was closed by October 14. Its October 18 notice describes key rotation and ongoing re-encryption. On October 20 it updated guidance on reporting to the Personal Information Protection Commission and notifying affected people, and on November 2 it added that Google Sheets integration credentials and sheet IDs may also have leaked, so third-party viewing or editing of linked sheets up to October 14 cannot be ruled out.

    Official announcement: Studio (Open external link)

    Possible leakUnauthorized access

    Number under investigation

    Timeline and sources (8) · Related announcements (16)
    Timeline and sources
    1. Initial reportOfficial announcement (Open external link)
    2. Incident portal / response statusOfficial announcement (Open external link)
    3. Reporting guidance updatedOfficial announcement (Open external link)
    4. Related Digital Agency disclosureOfficial announcement (Open external link)
    5. Related customer disclosuresOfficial announcement (Open external link)
    6. Joint-report intake timing announcedOfficial announcement (Open external link)
    7. Spreadsheet-integration impact addedOfficial announcement (Open external link)
    8. Joint reporting to the PPC opened for customersOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Digital Agency (Open external link) · Possible leakUp to 8,833 general-feedback entries, 250 recruitment inquiries, 3,661 vaccine-app inquiries, 117 mascot requests, 462 event entries and 35 accounts
    2. Yamanashi Prefecture (workplace-skills course) (Open external link) · Possible leakEight applicants and eight inquirers; overlap unresolved
    3. Fukuoka Convention Center (Open external link) · Possible leak288 facility inquiries, 1,185 lost-property inquiries and 766 accessible-parking submissions
    4. TOMONY (Open external link) · Possible leak19 people
    5. Raksul (Open external link) · Possible leak6,412 form submissions, not unique people
    6. Shima City (Open external link) · Possible leakThree inquiry-form submissions
    7. Monicle (Open external link) · Possible leak14 submissions concerning 11 people
    8. Monicle Research (Open external link) · Possible leak1,487 submissions concerning 807 people
    9. Monicle Financial (Open external link) · Possible leak994 submissions concerning 737 people
    10. Koriyama City (Open external link) · Possible leak23, 55, 55, five and two submissions across the specified forms
    11. Mizkan Asia Pacific (Open external link) · Possible leakUp to 355 submissions; 332 excluding tests and similar entries
    12. Shinseiki Social Welfare Corporation (Open external link) · Possible leakTwo contact-form submissions
    13. Yamanashi Prefecture (home-care training and advisory program) (Open external link) · Possible leak59 inquiries and 54, 102 and 90 training applications by year; overlap unresolved
    14. AISIN (YYSystem) (Open external link) · Possible leak3,396 inquiries (1,937 people)
    15. Koseikai social welfare corporation (Open external link) · Possible leakApprox. 843 inquiries
    16. Sally (Open external link) · Possible leak404 people who submitted the former website’s inquiry form

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-05

  44. Seven-Eleven Japan (vendor CBcloud)Delivery work for the 7NOW service (CBcloud’s PickGo platform)

    Seven-Eleven Japan announced on November 3 that PickGo, run by CBcloud, which handles part of 7NOW’s delivery work, suffered unauthorized access and that 7NOW orderer (recipient) data were found that day to have been taken. CBcloud identified the access on November 1.

    Official announcement: Seven-Eleven Japan (vendor CBcloud) (Open external link)

    Leak confirmedIncident at a vendor

    164,180, 4,762 and 209 records (three groups by data items)Orderer (recipient) names in kana only: 164,180; names and addresses: 4,762; names, addresses, phone numbers and postal codes: 209. Order dates, store names and addresses and item names were also taken in some cases. Card data, IDs and passwords are stated not to have leaked. 7NOW is operating normally.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-04

  45. Denny's JapanDenny's app (migration from the old app to the new app)

    Denny's Japan announced on November 3 that, while investigating suspicious access, it found on October 30 that a third party had improperly created login credentials in the process migrating users from the old app to the new one and could access some accounts, and that some customers' personal data may have leaked. It fixed the system that day and invalidated the improper credentials.

    Official announcement: Denny's Japan (Open external link)

    Possible leakUnauthorized access

    Count under investigationSome customers who used the old Denny's app are affected. Items are member codes, email addresses, birth dates, gender, prefecture, favorite restaurant and children's birthdays. The company says it does not hold names, addresses, phone numbers, passwords or card data. Only access records for October 7 have been reviewed; whether data were taken and how many people are affected are under investigation.

    Timeline and sources
    Timeline and sources
    1. First reportOfficial announcement (Open external link)

    Sources checked: 2026-11-05

  46. istyle (@cosme)@cosme common ID

    istyle announced on November 2 that it had confirmed on October 28 that part of the member data registered to the @cosme common ID leaked through unauthorized third-party access to @cosme. About 3 million people are affected; the cause and scope are under investigation.

    Official announcement: istyle (@cosme) (Open external link)

    Leak confirmedUnauthorized access

    Approx. 3 million peopleUser IDs, nicknames, names, postal codes, addresses, phone numbers, emails, gender, birth dates, skin type and hair type of members at the time of access, including those who later left. Login passwords and card data are stated to be excluded. This is a separate notice from the September file-transfer case.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  47. WILLsPoint-exchange service “Netmile”

    WILLs announced on November 2 that the system environment of its Netmile point-exchange service suffered unauthorized access and that part of the personal data of up to about 5.49 million members, including former members, may have leaked. Netmile and Sugutama are suspended.

    Official announcement: WILLs (Open external link)

    Possible leakUnauthorized accessThe Netmile and Sugutama sites are suspended to prevent secondary damage; no restart date is set.

    Up to approx. 5.49 million people (including former members)Names, emails and other reward-exchange information. The company states it holds no card or My Number card data.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  48. NojimaMember management system for Nojima Online and its used-smartphone buyback site

    Nojima detected unauthorized access to the Nojima Online member management system on November 1 and announced on November 2 that it had confirmed the leak of about 7 million member records of Nojima Online and its used-smartphone buyback site the same day. Both sites are temporarily suspended.

    Official announcement: Nojima (Open external link)

    Leak confirmedUnauthorized accessNojima Online and the used-smartphone buyback site are temporarily suspended; reopening will be announced once safety is confirmed.

    Approx. 7 million recordsNames, birth dates, gender, addresses, phone numbers, login IDs, encrypted passwords and emails of members of the two sites. Former members are excluded. The company states it holds no card data.

    Timeline and sources
    Timeline and sources
    1. First noticeOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  49. Related update

    IDC Frontier

    The October 27 seventh report concludes the investigation and states that virtual-server data was not exfiltrated. It separately confirms unauthorized queries of portal registration data for up to 71 customers, including up to 31 personal-name/email records.

    Official announcement: IDC Frontier (Open external link)

    Lookup confirmedRansomwareThe backup service has resumed and backups can be extracted for 206 customers; this is not full recovery of the four affected zones. Portal reopening remains undated.

    Up to 31 personal-name/email records; 495 organizations affectedRegistration data was queried for up to 71 customers, including up to 31 personal-data records at 31 customers. Four password changes are not added; the 495 affected organizations and 206 recoverable backups are not information counts.

    Timeline and sources (6) · Related announcements (9)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Third reportOfficial announcement (Open external link)
    3. Fourth reportOfficial announcement (Open external link)
    4. Fifth report: investigation and backupsOfficial announcement (Open external link)
    5. Sixth report / backup service resumedOfficial announcement (Open external link)
    6. Seventh report / investigation completed and recovery supportOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Viewcard (Open external link) · Possible leakAbout 4.03 million email addresses
    2. East Japan Railway (Open external link) · Possible leakEkinet: up to about 1.67 million; Otona no Kyujitsu Club: up to about 390,000 records
    3. Kyushu Railway (Open external link) · Possible leakUp to about 1.3 million records
    4. Nissui Logistics (Open external link) · Leak not confirmedSome inbound/outbound operations resumed; no personal or customer data on the affected server
    5. Cyber University (Open external link) · Leak not confirmedCourse registration and payment procedures disrupted
    6. Future Shop (Open external link) · Under investigationEmail services resumed in an alternative environment; leak investigation ongoing
    7. Nihon Shurui Hanbai / Tokyo Shusui (Open external link) · Possible leakNumber not disclosed; newsletter delivery suspended
    8. Japan Telecom Users Association (Open external link) · Leak not confirmedSender email address changed; learning service unaffected
    9. Fibergate (Open external link) · Leak not confirmedAll services except part of the free Wi-Fi authentication service resumed after rebuilding in another environment

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-03

  50. Related update

    SonicmoovLINE integration platform “COMSBI Enterprise”

    Sonicmoov announced on October 26 that on the morning of October 23 a third party logged in to the management system with improperly obtained credentials and obtained server credentials through a flaw in an admin-screen function. It confirmed that information on some clients and personal data of their end users leaked or may have leaked, and began suspending the service that day.

    Official announcement: Sonicmoov (Open external link)

    Leak or possible leak confirmedUnauthorized accessExternal access was blocked at 13:20 on October 23 and the service was suspended in stages. It remained suspended as of October 26.

    Count and number of client companies not disclosedAffected data include information on client companies’ admin-screen users (names, email addresses and encrypted passwords), LINE official account settings, and personal data of the clients’ end users (items vary by client). No card data are held. Client UCC Ueshima Coffee announced that 5,529 of its email addresses were confirmed as leaked.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. UCC Ueshima Coffee (Open external link) · Leak confirmed5,529 email addresses

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-05

  51. Second report

    Fujicco (campaign-entry contractor)Non-member entry forms for two campaigns

    Fujicco announced on October 22 that it had found on October 21 that a contractor server handling non-member entry forms for two campaigns suffered unauthorized access and that entrants’ personal data may have leaked. The November 2 second report revised the count to 14,594.

    Official announcement: Fujicco (campaign-entry contractor) (Open external link)

    Possible leakIncident at a vendorThe affected entry intake was suspended; on October 27 entries for one campaign resumed through the member system only.

    14,594 records (excluding duplicate entries; revised from approx. 15,500 in gross)Names, ages, gender, occupations, marital status, household composition, phone numbers, emails, addresses and survey answers. The second report also gives a combined 14,848 people including 254 who entered both campaigns. Licence, card and bank data are excluded. The contractor is not named. The October 27 blastmail-related notice is a separate incident.

    Timeline and sources (3)
    Timeline and sources
    1. First noticeOfficial announcement (Open external link)
    2. Member entries resumedOfficial announcement (Open external link)
    3. Second report (count revised)Official announcement (Open external link)

    Sources checked: 2026-11-03

  52. Notice by contractor GMO Payment Gateway

    Life Card (contractor GMO Payment Gateway)Prepaid card “Vpreca”

    Life Card partly suspended its Vpreca prepaid service on October 31 after unauthorized access was found at a contractor. A November 2 update said misuse on October 30 of a function GMO Payment Gateway provides for Life Card led to the theft of data in 69 accounts, and the service resumed the same day.

    Official announcement: Life Card (contractor GMO Payment Gateway) (Open external link)

    Leak confirmedIncident at a vendorPart of the service was suspended from October 31; resumption was announced on November 2.

    69 accounts in totalBreakdown: 63 with names, emails, phone numbers and partial addresses; three with Vpreca numbers, dedicated security codes, expiry dates and names; three with partial Vpreca numbers. The three accounts with full card data were closed on October 31. The contractor GMO Payment Gateway describes the same data as possibly stolen. This is separate from the Ymirlink-related case announced on October 28.

    Timeline and sources (4)
    Timeline and sources
    1. First notice / partial suspensionOfficial announcement (Open external link)
    2. UpdateOfficial announcement (Open external link)
    3. Service resumedOfficial announcement (Open external link)
    4. Notice by contractor GMO Payment GatewayOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  53. Ryohin Keikaku (order-curtain contractors)Order-curtain server managed by subcontractor Nanotec

    Ryohin Keikaku announced on November 2 that traces of unauthorized access on October 19 were found on October 28 on a server managed by Nanotec, a subcontractor of its order-curtain contractor MN Inter-Fashion, and that 19,933 customer records may have leaked.

    Official announcement: Ryohin Keikaku (order-curtain contractors) (Open external link)

    Possible leakIncident at a vendor

    19,933 records (including duplicates for the same customers)Names, addresses, phone numbers, order details and delivery addresses of customers who ordered made-to-order curtains at MUJI from April 10, 2018 to January 25, 2022. Card data and emails are excluded. The server is managed by Nanotec, a subcontractor of MN Inter-Fashion. This is separate from the MUJI app case.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  54. Value GolfGolf booking service “Hitori Yoyaku Land”

    Value Golf found traces of unauthorized access to its Hitori Yoyaku Land golf booking service on November 1 and blocked the route. Its November 2 first report said users’ login email addresses may have been viewed or obtained.

    Official announcement: Value Golf (Open external link)

    Possible leakUnauthorized access

    Count not disclosed (login email addresses)Users’ login email addresses may have been viewed or obtained; other registration data such as names are stated to be excluded.

    Timeline and sources
    Timeline and sources
    1. First report (exchange filing)Official announcement (Open external link)

    Sources checked: 2026-11-03

  55. Marui Group (contractor Securitize Japan)Digital bond administration (Securitize Japan servers)

    Marui Group announced on November 2 that servers of Securitize Japan, which administers its digital bonds, suffered unauthorized third-party access on October 29 and that part of the personal data of up to 9,086 applicants was confirmed leaked. Starts Securities announced on October 31 that part of its customers’ data was obtained through unauthorized access to the Securitize system.

    Official announcement: Marui Group (contractor Securitize Japan) (Open external link)

    Partial leak confirmedIncident at a vendor

    Up to 9,086 people (54 of whom may have had bank-account numbers exposed)Names, addresses, phone numbers, emails, birth dates, gender, bank-account numbers and holdings of customers who opened accounts to apply for the digital bonds. The 54 are a subset. No card data were entrusted. None of the notices state a link to the NTT DATA STdirectServices case.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Starts Securities (Open external link) · Leak confirmedNames and holdings of Starts Asset Token (Ryogoku-Chidoricho) holders; count not disclosed

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-03

  56. Suntory HoldingsExternal cloud service used by the group

    Suntory detected anomalies in an external cloud service used by the group on October 28 and announced on November 2 that some files downloaded by a third party contained personal data. By November 1 it had confirmed leaks in seven groups, including about 90,000 employees.

    Official announcement: Suntory Holdings (Open external link)

    Leak confirmedUnauthorized access

    Approx. 90,000 people and six other groups(1) About 90,000 group and partner-company employees (names and emails); (2) 7,323 Mal de Shine registrants; (3) 7,173 applicants for 2026 new-graduate business roles; (4) 1,097 contacts stored on two company phones; (5) 324 Monte Bussan and partner employees; (6) 96 Izutsu Maisen delivery customers and delivery staff; (7) 25 supplier employees. Payment data are not included.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  57. Trade Works third report

    IwaiCosmo Securities / Trade Works

    On October 20, IwaiCosmo added 364 people to the Trade Works incident, bringing confirmed exposure to 4,975. It separately reported unauthorized orders in seven accounts from the same attack, with executions in five. Those accounts were restored to their pre-trade positions without customer charges. On October 21 it clarified that passkeys had not been bypassed.

    Official announcement: IwaiCosmo Securities / Trade Works (Open external link)

    Leak confirmedIncident at a vendor

    4,975 people

    Timeline and sources (4)
    Timeline and sources
    1. Exposure and response noticeOfficial announcement (Open external link)
    2. UpdateOfficial announcement (Open external link)
    3. UpdateOfficial announcement (Open external link)
    4. Trade Works third reportOfficial announcement (Open external link)

    Sources checked: 2026-11-03

October 2026

  1. NTT DATA (STdirectServices contractor)STdirectServices (benefit support for bonds with digital perks)

    NTT DATA announced on October 31 that a contractor SaaS used for STdirectServices suffered unauthorized access and that personal data may have leaked, and suspended the service. Distributors and issuers report that bond-purchaser data may have been taken from the “digital securities platform.”

    Official announcement: NTT DATA (STdirectServices contractor) (Open external link)

    Possible leakIncident at a vendorNTT DATA suspended the service; it states there is no current impact on benefit delivery because no bonds are currently eligible.

    Count under investigation; distributors and issuers disclose separatelyNTT DATA gives no count. Rakuten Securities’ gross 362 records span three bond issues and include the Kagome (109) and JR West (2) figures. Kintetsu Group Holdings’ 2,678 records (names and purchase amounts) may overlap with distributors’ figures. All are shown as related disclosures and not added.

    Timeline and sources · Related announcements (5)
    Timeline and sources
    1. Service suspension announcedOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Rakuten Securities (Open external link) · Possible leak362 records in gross (three bond issues)
    2. Kagome (Open external link) · Possible leak109 people (within Rakuten Securities’ figure)
    3. West Japan Railway (Open external link) · Possible leakTwo records (within Rakuten Securities’ figure)
    4. Nomura Securities (Open external link) · Possible leakPossibly exposed data still being identified
    5. Kintetsu Group Holdings (Open external link) · Possible leak2,678 records (all investors buying JPY 1 million or more of its 135th bond)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-02

  2. Credit Saison (contractor)Member platform for “Saison Smart Real Estate Investment”

    On October 29 a contractor providing the member platform for a real-estate security token was accessed without authorization through a flawed authentication mechanism. Credit Saison announced on October 31 that personal data of 1,889 customers leaked; the platform is urgently suspended.

    Official announcement: Credit Saison (contractor) (Open external link)

    Leak confirmedIncident at a vendorThe member platform has been urgently suspended since 22:00 on October 29; no reopening date is set.

    1,889 customers39 customers: names, emails, addresses, birth dates, phones, nationality, dividend accounts and suitability data; 1,850 customers: names and units purchased. No card data is held. No alteration of holdings or on-chain transfers has been found.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  3. Wording corrected

    Hana CupidInternet Hana Cupid / Business Hana Cupid

    Hana Cupid’s management system was accessed without authorization on October 14–15, and partial leakage of member data was confirmed on the 19th. On October 28 it disclosed that up to 4,238,242 member records may be affected.

    Official announcement: Hana Cupid (Open external link)

    Partial leak confirmedUnauthorized access

    Up to 4,238,242 recordsLogin IDs, hashed passwords (wording corrected on October 30) and email addresses. The figure is customers possibly affected; confirmed leaks are not separated. Names, addresses and card numbers are stated not to have leaked.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Wording corrected (password storage format)Official announcement (Open external link)

    Sources checked: 2026-11-03

  4. Matsuya Foods HoldingsMatsuya app management system (Matsuben Net, mobile ordering, delivery)

    On October 28 Matsuya found that third-party unauthorized access to its app management system had leaked member data. On October 30 it confirmed leakage of 2,000 app-member and 2,377,127 Matsuben Net and related user records, with related services suspended.

    Official announcement: Matsuya Foods Holdings (Open external link)

    Leak confirmedUnauthorized accessThe Matsuya app and related services including the website are suspended.

    2,000 app members (up to 3,000) and 2,377,127 Matsuben Net and other usersApp-member data includes encrypted passwords; the 3,000 maximum includes the 2,000. Overlap between categories is not stated. The company says it holds no card data.

    Timeline and sources
    Timeline and sources
    1. Announcement (exchange filing)Official announcement (Open external link)

    Sources checked: 2026-11-02

  5. World (subsidiary Tin Pan Alley)Business server

    World disclosed on October 30 that an outsider intruded into subsidiary Tin Pan Alley’s business server on October 17 and performed data extraction, detected on October 28, and that about 1.2 million member records in gross may have leaked.

    Official announcement: World (subsidiary Tin Pan Alley) (Open external link)

    Possible leakUnauthorized accessThe server was isolated from external networks and some related internal business systems were stopped.

    Approx. 1.2 million member records in grossNames, addresses, phones, birth dates, gender and emails. The figure is gross and details are being confirmed; card or other payment data and facial data are not found to have leaked.

    Timeline and sources
    Timeline and sources
    1. Announcement (exchange filing)Official announcement (Open external link)

    Sources checked: 2026-11-03

  6. Related update

    Future Shopfutureshop

    Access to its server on October 17–18 resulted in acquisition of 3,147,469 member records from one store. Mitigation was applied and no equivalent access traces were found at other stores. Affected retailer Lindt suspended its online shop. On October 25, the company clarified that this was distinct from the October 21 access incident and the PHP-related maintenance outage.

    Official announcement: Future Shop (Open external link)

    Leak confirmedUnauthorized accessLindt suspended its online shop from 16:00 on October 21; this is not a platform-wide shutdown.

    3,147,469 member records at one storeLindt discloses the same member records and is not added again. Credit card data is excluded. On October 30 Lindt revised its figure to 3,147,377 after removing double-counted members; the totals use the platform’s figure.

    Timeline and sources (2) · Related announcements (1)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Distinction from other outage and access incidentOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Lindt & Sprüngli Japan (Open external link) · Leak confirmed3,147,377 records (revised on October 30 after de-duplication)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-02

  7. Second report: reservation-site leak identified

    Hankyu Hanshin Department Stores / H2O RetailingReservation site, HANKYU HANSHIN E-STORES and Remo Order

    Unauthorized access was detected on October 16–17 and the three affected services were suspended. Investigation on October 19 identified exposure of some personal information in approximately 1.26 million H2O ID records. The October 30 second report newly found that 6,243 reservation-form entries were leaked, while customer information at E-STORES and Remo Order was not found to have leaked externally. Some services remain suspended.

    Official announcement: Hankyu Hanshin Department Stores / H2O Retailing (Open external link)

    Leak confirmedUnauthorized accessReservation site suspended October 16; E-STORES and Remo Order suspended October 17. As of the October 30 second report some services remain suspended for a full system review; no reopening date announced.

    Approximately 1.26 million records / 6,243 reservation-form entriesIn addition to some fields in approximately 1.26 million H2O ID records, the second report found that 6,243 reservation-form entries (including participant application details; about 3% of 188,590 bookings) were leaked. The customer information at E-STORES and Remo Order mentioned in the first report was not found to have leaked.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Second report: reservation-site leak identifiedOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  8. Third report: refund bank account data confirmed leaked

    Adventureskyticket: servers

    The October 16 second report corrected the card-data statement. The October 30 third report said part of an undeleted database backup was read and that 32,341 refund bank account records were sent externally; about 936,000 masked card records (about 414,000 people, 12 with full numbers) and about 118,000 travel insurance records may also have leaked. It also corrected the second report regarding Benefit Station data.

    Official announcement: Adventure (Open external link)

    Leak confirmedUnauthorized access

    About 14.64 million customer records and card data of up to 6,140 people; 32,341 refund bank accounts (leaked); about 936,000 partial card records and about 118,000 travel insurance records (possible)About 4.13 million hashed-password records are a subset. Including the third report’s 32,341 refund bank accounts (confirmed), about 936,000 masked card records (about 414,000 people, 12 with full numbers) and about 118,000 travel-insurance records (possible), overlap between groups and with the other two events is unresolved, so they are not added.

    Timeline and sources (3)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Second report / card-data correctionOfficial announcement (Open external link)
    3. Third report: refund bank account data confirmed leakedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  9. Joint announcement

    LifeNet Insurance / KDDILifeNet’s KDDI-linked system

    On October 23 LifeNet detected unauthorized access to its KDDI-linked system and found that part of the customer data held in KDDI’s system may have leaked through it. The two companies announced this jointly on October 30.

    Official announcement: LifeNet Insurance / KDDI (Open external link)

    Possible leakUnauthorized accessLifeNet has placed some functions of “au no Seimei Hoken,” including applications, under maintenance.

    22,541 records across six categoriesSix categories by data combination (4,524; 226; 8,434; 3,662; 4,888; 807). No total is printed. Passwords, card, bank, identity-document and insurance-contract data are excluded.

    Timeline and sources (2)
    Timeline and sources
    1. Joint announcement (KDDI)Official announcement (Open external link)
    2. Joint announcement (LifeNet)Official announcement (Open external link)

    Sources checked: 2026-11-02

  10. Possible data leak disclosed

    Saga UniversityAdministrative NAS

    Saga University found apparent ransomware damage on an administrative NAS on September 24 and temporarily suspended administrative terminals. On October 30 it disclosed that personal data, including patient information and data on about 80,000 students, staff and others, may have leaked.

    Official announcement: Saga University (Open external link)

    Possible leakRansomwareAdministrative terminals were suspended on September 24, restarted on the 27th and normal operations resumed on the 28th; no impact on education, research or clinical systems was found.

    Approx. 80,000 people; patient-data count under investigationStudents, staff, former students and staff and other parties; includes names, birth dates, addresses, contacts, passwords and sensitive data such as clinical department and diagnoses. Patient-data counts remain under investigation and are not included.

    Timeline and sources (2)
    Timeline and sources
    1. Incident announcedOfficial announcement (Open external link)
    2. Possible data leak disclosedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  11. Announcement

    Tokyu LandGREEN CROSS PARK and GREENUP Cooldown Project websites

    Tokyu Land found unauthorized access to a shared AWS server environment for some of its websites, exploiting CMS vulnerabilities and permission misconfiguration. On October 30 it disclosed possible leakage of 4,079 member registrations and three inquiries.

    Official announcement: Tokyu Land (Open external link)

    Possible leakUnauthorized accessThe sites were cut off and placed in emergency maintenance on October 19 and have been progressively restored since October 20 after fixes.

    4,079 member registrations and three inquiriesCounts are per site; overlap is not stated.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Announcement (PDF)Official announcement (Open external link)

    Sources checked: 2026-11-02

  12. Sixth report: investigation results and scope

    Nihon Kotsu

    Unauthorized access on July 11 led to suspension of dispatch and other systems. The October 30 sixth report, based on an external investigation, disclosed that personal data of about 290,000 people in six groups leaked or may have leaked, with notices being sent.

    Official announcement: Nihon Kotsu (Open external link)

    Leak confirmedMalware infectionPlanned restart of telephone dispatch and selected services

    About 292,900 people across six groups (leaked or possibly leaked)About 13,100 hire-car customers, 60,100 drivers and staff, 107,900 job applicants, 37,700 family members, 2,100 business contacts and 72,000 accident counterparties. Some records include ID documents, My Number or health data; taxi passenger data is not included.

    Timeline and sources (4)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Fourth reportOfficial announcement (Open external link)
    3. Planned restart of selected servicesOfficial announcement (Open external link)
    4. Sixth report: investigation results and scopeOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  13. Exposure figures updated

    Japan Atomic Energy AgencyJRR-3 research support site

    On September 25, JAEA confirmed unauthorized downloads of 2,419 files and suspended external access. An October 30 update revised the files containing identity documents, health examination results or other personal data to 369 and the people with Individual Numbers to seven. It reported no account-data exposure or impact on other systems.

    Official announcement: Japan Atomic Energy Agency (Open external link)

    Leak confirmedUnauthorized accessExternal access to the research support site suspended

    369 files containing personal data (175 people as initially reported)Updated from 367 to 369 files on October 30. Includes 200 identity documents, 146 health examination results and 23 radiation-worker certificates (up from 21); seven people had Individual Numbers included (up from six). No update to the 175-person figure was given. The total of 2,419 downloaded files is not added.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Exposure figures updatedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  14. Fourth report: investigation results

    Ryomo SystemsInternal systems

    Unauthorized access to internal systems was confirmed on August 14. The October 30 fourth report said it was a ransomware attack that began with misuse of a VPN account on August 12, and that data on inquirers, business partners, job applicants and employees (including My Number) may have leaked; clients’ customer data is being reported to each client.

    Official announcement: Ryomo Systems (Open external link)

    Possible leakRansomwareInternal systems were stopped in August; the third report did not specify their recovery status.

    Personal-data count and fields under reviewPotentially includes sales and transaction information and personal data of customers, inquirers and employees. No count disclosed.

    Timeline and sources (4)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)
    3. Third report / investigation statusOfficial announcement (Open external link)
    4. Fourth report: investigation resultsOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  15. Third report

    GMO GlobalSignID management service “GMO Trust Login”

    GMO GlobalSign disclosed on September 16 that files containing customer data had been externally accessible from around November 2017 to September 15, 2026. Its October 30 third report said access-log analysis confirmed the files were obtained by third parties and updated the scope to 2,492 companies and 45,030 people.

    Official announcement: GMO GlobalSign (Open external link)

    Leak confirmedMisconfiguration

    2,492 companies and 45,030 peopleNames, emails, linked-service names and custom attributes such as employee numbers in bulk-operation files (44,836 people), plus names, addresses, phone numbers and emails of billing contacts (194 people), de-duplicated by email. The third report updated the provisional 2,007 companies and 37,747 people. Passwords, MFA data and payment data are not included. Before June 7, 2021 no access logs exist, and that period is treated as one of possible acquisition.

    Timeline and sources (3)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    2. UpdateOfficial announcement (Open external link)
    3. Third report (updated counts and corrections)Official announcement (Open external link)

    Sources checked: 2026-11-03

  16. Ministry of Foreign AffairsNetwork used for external communication

    The ministry detected and blocked unauthorized access to its external-communication network on July 27. On October 30 it disclosed that part of the email and other data on that network may have leaked, covering about 3,600 records such as email addresses and names.

    Official announcement: Ministry of Foreign Affairs (Open external link)

    Possible leakUnauthorized access

    Approx. 3,600 records, including about 900 relating to non-ministry peopleEmail addresses, names and other data. The closed network for classified information and consular systems such as passports were not affected, according to the ministry.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  17. JAL/JTA announcement

    ANA / Japan Airlines (Amadeus passenger service system)Amadeus IT Group passenger service system

    ANA and Japan Airlines were informed by their passenger-service-system provider Amadeus IT Group that unauthorized access to its system left traces of external viewing of part of their reservation data. JAL and JTA, notified on October 23, reported about 92,000 customers with bookings from August 2023 to September 2026; ANA reported about 37,800.

    Official announcement: ANA / Japan Airlines (Amadeus passenger service system) (Open external link)

    Viewing traces confirmedIncident at a vendor

    Approx. 37,800 ANA and 92,000 JAL/JTA customersANA: about 36,100 (names, booking references, flight details) and about 1,700 (also email, phone, passport number and nationality); JAL/JTA: about 90,000 and about 2,000 with similar items. Breakdowns are not added. Each airline’s figure covers its own reservation records. JAL states that card numbers and passwords were not exposed.

    Timeline and sources (2)
    Timeline and sources
    1. ANA announcementOfficial announcement (Open external link)
    2. JAL/JTA announcement (date at end of notice)Official announcement (Open external link)

    Sources checked: 2026-11-02

  18. CoadeHanikuji Land

    An investigation triggered by a September inquiry-form fault found traces of unauthorized command execution and credential misuse. On October 30 Coade disclosed that personal data of up to 7,622 users of its online lottery site may have leaked.

    Official announcement: Coade (Open external link)

    Possible leakUnauthorized access

    Up to 7,622 peopleNames, addresses, phone numbers, emails and purchase history, still under review; card data is stated not to have leaked.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  19. Second report

    East Japan Mitsubishi Motor SalesEmployee business email account

    A fraudulent login to an employee’s email account on October 9 led to spoofed emails, reported on October 13. The October 30 second report discloses that 24,480 customer records in a list stored in the account may have leaked.

    Official announcement: East Japan Mitsubishi Motor Sales (Open external link)

    Possible leakUnauthorized access

    24,480 customer recordsNames, vehicle registration numbers, store and staff names and cost or repair amounts for customers from November 2024 to September 2026; no addresses, phone, bank or card data. The 825 spoofed emails in the first report are messages sent and are not added.

    Timeline and sources (2)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  20. DHCDHC online shop

    On October 28 DHC identified unauthorized access to its online shop, alteration of member data and fraudulent registrations and orders. It disclosed on October 30 that data in 5,096 altered accounts may have been viewed, with no sign of exfiltration found.

    Official announcement: DHC (Open external link)

    Possible leakUnauthorized access

    5,096 accounts alteredMember numbers, delivery details, purchase history and last four card digits of altered accounts may have been viewed. Up to 5,520 delivery addresses belong to the same accounts and are not added; 27 suspicious orders and 71 fraudulent registrations are counts of actions.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  21. Notice to client businesses added

    Fines

    The company disclosed 1,536,322 records affected by unauthorized access to its booking system on September 21-22. An October 29 update said exposure of names, phone numbers, emails and booking details was confirmed, while addresses, dates of birth and other fields remain under investigation as possible exposure.

    Official announcement: Fines (Open external link)

    Partly confirmedUnauthorized access

    1,536,322 records

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Notice to client businesses addedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  22. Fifth report: some functions resumed

    NTT SolmareComic Cmoa

    The October 21 fourth report confirmed exposure of 319 member-registration records and up to about 4.2 million system-log records; logs may repeat users and do not contain passwords. The October 29 fifth report announced partial reopening, including browser reading and the subscription service.

    Official announcement: NTT Solmare (Open external link)

    Leak confirmedUnauthorized accessOn October 29 browser reading, the subscription reading service, member-detail changes and cancellation requests resumed; purchases, the bookshelf app and new registrations have not.

    319 registration records and up to about 4.2 million log recordsLogs may include repeated information about the same users. Their overlap and scope relative to registration records remain unresolved, so neither figure is added to the reference sums.

    Timeline and sources (4)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Third update and further investigationOfficial announcement (Open external link)
    3. Fourth report / affected scopeOfficial announcement (Open external link)
    4. Fifth report: some functions resumedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  23. ELESTYLEManagement system for the OneQR and elepay payment services

    ELESTYLE announced on October 29 that on October 25 it found unauthorized access exploiting an access-control flaw in part of its management system, and that 7,162 merchant registration records may have been obtained externally. The flaw was fixed on October 27.

    Official announcement: ELESTYLE (Open external link)

    Possible leakUnauthorized access

    7,162 merchant registration recordsUser names (company or personal names), email addresses, internal system identifiers and similar data. Login passwords, end-user data, card data, bank-account data, transaction data and ID documents are stated to be excluded. Order intake and payment processing were not affected.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-04

  24. Related update

    AZOOHotel system “WASIMIL”

    After a client facility reported on October 17 that guests were receiving suspicious messages, AZOO confirmed on October 19 that reservation data of guests at some contracted facilities leaked through unauthorized access to its WASIMIL hotel system. It says the exploited vulnerability was fixed on October 19.

    Official announcement: AZOO (Open external link)

    Leak confirmedUnauthorized access

    Count under investigation (reservation data of guests at some contracted facilities)Reservation data including names and contact details; the exact items and count are under investigation. Card data are not stored. No site-controller integration data leaked.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. PIECE (30 PIECES and others) (Open external link) · Possible leakData of guests who booked on or before October 19, 2026; count not disclosed

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-03

  25. Second report

    Shinryo CorporationEnergy management service “SEMS”

    Shinryo announced on October 21 that unauthorized third-party access on October 17 caused a system failure affecting its SEMS energy management service. Its October 28 second report attributed the incident to ransomware and said no external leak of personal or customer data has been confirmed.

    Official announcement: Shinryo Corporation (Open external link)

    Leak not confirmedRansomwarePart of the services for SEMS customers and partners has been affected since October 17; as of October 28 no recovery date is set.

    No external leak of personal or customer data confirmed; investigation continuesThe source does not disclose an information count.

    Timeline and sources (2)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  26. Unauthorized access and leak announced

    Sony LifePolicyholder “Customer Web Service” and related systems

    Sony Life found unauthorized access to its policyholder website and related systems on October 27 and suspended related services. On October 28 it confirmed leakage of about 385,000 records on Medicare Life policies it handled as an agent.

    Official announcement: Sony Life (Open external link)

    Leak confirmedUnauthorized accessThe Customer Web Service, app and related services have been suspended since 08:00 on October 28; restoration timing is undecided.

    Approx. 385,000 recordsNames, birth dates, addresses, phones, policy numbers and contract details of Medicare Life policyholders and insureds handled by Sony Life as agent. Medicare Life’s identical figure is not added; the scope is still being identified.

    Timeline and sources (2) · Related announcements (1)
    Timeline and sources
    1. Service suspension noticeOfficial announcement (Open external link)
    2. Unauthorized access and leak announcedOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Medicare Life (Open external link) · Leak confirmedApprox. 385,000 records (same figure)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-02

  27. METI press release

    Electricity and Gas Market Surveillance Commission (METI)Reporting system “Dentori-net”

    The commission confirmed on October 28 that its Dentori-net site, used by electricity and gas retailers to submit reports, was accessed without authorization early on October 27, and stopped operating it. Whether data leaked is being checked.

    Official announcement: Electricity and Gas Market Surveillance Commission (METI) (Open external link)

    Under investigationUnauthorized accessThe site is out of operation; reports are accepted by email until it is restored.

    Whether data leaked is being checkedThe source does not disclose an information count.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / suspensionOfficial announcement (Open external link)
    2. METI press releaseOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  28. Benefit One (contractor Forestec)“Toku-Kai” perks service for Credit Saison members

    A system run by Forestec, a contractor of Benefit One, was intermittently accessed without authorization from October 14 to 20, and personal data of 29,465 “Toku-Kai” registrants was downloaded. Benefit One and Credit Saison announced this on October 28.

    Official announcement: Benefit One (contractor Forestec) (Open external link)

    Leak confirmedIncident at a vendorThe service has been suspended since 17:00 on October 21; no restart date is set.

    29,465 peopleNames, kana, birth dates, gender, postcodes, emails, customer numbers and payment-management numbers; no card numbers. Credit Saison reports the same figure, which is not added.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Credit Saison (Open external link) · Leak confirmed29,465 people (same figure)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-02

  29. Unauthorized access and leak announced

    ENEOS PowerCustomer pages for ENEOS Denki and related services

    ENEOS Power suspended part of its website content on October 27 and announced on October 28 that its low-voltage electricity service system had been accessed without authorization and personal data of 57 customers leaked.

    Official announcement: ENEOS Power (Open external link)

    Leak confirmedUnauthorized accessExternal access to customer pages and parts of the website is blocked and some content is unavailable.

    57 customersNames, addresses, customer-page login IDs and passwords and contract, usage and billing details; bank and card data are excluded.

    Timeline and sources (2)
    Timeline and sources
    1. Partial content suspensionOfficial announcement (Open external link)
    2. Unauthorized access and leak announcedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  30. Second report: up to about 230,000 records

    JFE ChemicalCorporate IT environment

    Possible unauthorized access was identified on October 14 and data theft was confirmed on October 19. The October 28 second report confirms that the stolen data includes personal data on business partners, external parties and employees, with up to about 230,000 records obtained or possibly obtained, including duplicates still under review.

    Official announcement: JFE Chemical (Open external link)

    Data theft confirmedUnauthorized access

    Up to about 230,000 personal-data records (obtained or possibly obtained)Names, affiliations, phone numbers and emails, among others. Includes duplicates and data that cannot identify individuals on its own; under review. No card or bank data of business partners or external parties leaked, according to the company.

    Timeline and sources (2)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    2. Second report: up to about 230,000 recordsOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  31. Don Quijote and three group companies (watch-repair contractor Cox)Watch-repair contractor’s server

    Cox, a watch-repair contractor, detected an attack on September 15 and its server was encrypted by ransomware. Don Quijote, Nagasakiya, Tachibana Department Store and UD Retail jointly announced on October 28 that leakage is not confirmed but cannot be ruled out; the server has not been restored.

    Official announcement: Don Quijote and three group companies (watch-repair contractor Cox) (Open external link)

    Leak cannot be ruled outRansomware

    Count not disclosedNames and partial addresses and phone numbers of customers who requested watch repairs at group stores since September 2025.

    Timeline and sources
    Timeline and sources
    1. Joint announcement by four companiesOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  32. Sony Network CommunicationsSo-net member database

    The So-net member database was accessed without authorization on October 19; the company confirmed it on the 23rd and stopped the server. On October 27 it confirmed leakage of 2,141,986 So-net and 443,495 docomo Hikari “plala (S course)” member records, among other data, and reset the affected mail passwords.

    Official announcement: Sony Network Communications (Open external link)

    Leak confirmedUnauthorized access

    2,141,986 So-net member records and 443,495 plala (S course) member recordsNames, phones, emails, user IDs, birth dates, gender and connection IDs (no passwords). Separately, email addresses with mail passwords (54,401 addresses across four services), 16 bank-account records and seven notice records leaked; they likely overlap with So-net members and are not added. No card data.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. NTT DOCOMO (docomo Hikari plala S course) (Open external link) · Leak confirmed443,495 records (same figure)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-02

  33. Final report / service resumed

    Kufu CompanyKufu Machi Talk (beta)

    Kufu Company found suspicious access on October 2 and suspended the service on the 5th. On the 13th it reported that birth dates and gender of 308 users were externally viewable and one user’s email was obtained; its October 27 final report announced the service’s resumption.

    Official announcement: Kufu Company (Open external link)

    One user’s data confirmed obtainedUnauthorized accessThe service was suspended on October 5 and resumed on October 27.

    308 users, including one whose email was confirmed obtainedBirth dates and gender of 308 users were externally viewable; for one of them, the email address was obtained and could be linked.

    Timeline and sources (3)
    Timeline and sources
    1. Announcement / suspensionOfficial announcement (Open external link)
    2. Investigation resultsOfficial announcement (Open external link)
    3. Final report / service resumedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  34. Notice to users

    gifteePart of the e-gift issuance system

    On October 25 giftee found that e-gifts had been fraudulently issued through unauthorized access exploiting a system vulnerability, and stopped the system that day. It announced on October 26 an expected loss of about JPY 550 million, with no personal-data leak confirmed.

    Official announcement: giftee (Open external link)

    No personal-data leak confirmedUnauthorized accessThe system was stopped on October 25 and will not be reused; disruptions to some e-gift exchanges are being resolved progressively.

    No personal-data leak confirmedExpected loss of about JPY 550 million (a monetary amount, not an information count). This is separate from the RAKUS Lite Cloud blastmail incident.

    Timeline and sources (2)
    Timeline and sources
    1. Exchange filing (giftee Group)Official announcement (Open external link)
    2. Notice to usersOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  35. Japan External Trade Organization (JETRO)e-Venue

    JETRO identified unauthorized access on September 24–25 and October 14 to its outsourced e-Venue system, with up to 133 registration records potentially exposed. The service was suspended for security checks.

    Official announcement: Japan External Trade Organization (JETRO) (Open external link)

    Possible leakUnauthorized accessSystem suspended to prevent further damage; reopening undated.

    Up to 133 recordsNames, emails, telephone, mobile and fax numbers. This concerns a different system from the separately reported 743-record JETRO website incident.

    Timeline and sources
    Timeline and sources
    1. Announcement / suspensionOfficial announcement (Open external link)

    Sources checked: 2026-10-28

  36. Investigation results: about 124,000 people

    Dai-ichi Life Group / Dai-ichi Life Insurance

    On October 27 the companies published external investigation results on unauthorized access to an employee HR system, revising the affected people to about 124,000 (about 54,000 employees and 70,000 former employees) and stating that customer data such as policyholder information was not accessed.

    Official announcement: Dai-ichi Life Group / Dai-ichi Life Insurance (Open external link)

    Possible leakUnauthorized access

    About 124,000 peopleAbout 54,000 employees and 70,000 former employees; about 96,000 involve only addresses and phone numbers. Updated from about 120,000.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Investigation results: about 124,000 peopleOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  37. Second report: individual notices

    Daito Gas

    The company disclosed possible leakage of customer information from historical files left on a vendor network.

    Official announcement: Daito Gas (Open external link)

    Possible leakIncident at a vendor

    About 124,000 records

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Second report: individual noticesOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  38. MICINOnline medical consultation service “curon”

    MICIN announced on October 27 that on October 23 it confirmed unauthorized logins by a third party, apparently through a credential-stuffing attack, to some medical-institution and patient accounts of the curon service. It says no traces of intrusion into its servers or databases have been found. It reset passwords of the affected accounts and others and logged out all medical-institution accounts. It does not plan to suspend the service.

    Official announcement: MICIN (Open external link)

    Leak confirmedUnauthorized access

    Data on 73 patients viewed; unauthorized logins to 14 patient accounts and 6 accounts of 5 medical institutionsAt three of the institutions whose accounts were accessed, data on 73 patients (names, email addresses, phone numbers, dates of birth, addresses, gender, medical record numbers, patient card numbers, consultation status and doctors’ notes) were viewed. Through patient accounts, names, email addresses, phone numbers, dates of birth, addresses, gender and patient codes may have been viewed. For some patients, prescription images, consultation records and service usage history are also affected. Names and email addresses of medical staff are also affected; their number is not stated. Identity documents and passwords are not included.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-06

  39. Smart ShareSocial media campaign tool “OWNLY”

    Smart Share announced on October 27 that in the early hours of October 16 its monitoring system detected unauthorized access through a flaw in a file upload function, and that the entry route was blocked the same day. It found traces that some campaign participant data stored on the server were viewed and downloaded, and says a total of 14,034 participant records from three campaigns were found to have leaked.

    Official announcement: Smart Share (Open external link)

    Leak confirmedUnauthorized access

    14,034 campaign participant recordsParticipant data from three MOS Burger social media campaigns (receipt challenge 2,995, Halloween giveaway 11,001 and VALX collaboration receipt campaign 38): X or LINE user names and IDs, entry times, draw and coupon status and similar data. Names, addresses, phone numbers, email addresses and card data were not collected and are not included.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-06

  40. BushiroadSystems of the development contractor for the game app “BanG Dream! Our Notes”

    Bushiroad announced on October 27 that its development contractor’s systems suffered unauthorized third-party access and that personal data of applicants and others in the June closed beta test, and of users who contacted customer support between September 24 and October 14, were found to have leaked. It says the data appear to have been taken from the data storage environment owing to a management deficiency at the contractor.

    Official announcement: Bushiroad (Open external link)

    Leak confirmedIncident at a vendor

    10,194 closed beta applicants, 71 staff and related persons, 5 survey respondents and 3,034 customer support inquirersApplicant data are email addresses, IP addresses, application times and device type. The 71 persons are employees of Bushiroad and affiliates (including names) and contractor employees (phone numbers). The 3,034 support inquirers contacted support between September 24 and October 14; besides inquiry text, the data include, depending on the inquiry, device information (2,832), player IDs (2,820), email addresses (311), names (257), phone numbers (11) and addresses/postcodes (6), all subsets of the 3,034. Passwords, card data and similar items are not confirmed as leaked.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-06

  41. Rakuten Group (Rakuten Travel Xchange)Part of Rakuten Travel’s overseas hotel booking pages

    Rakuten detected anomalies on September 10 on part of the overseas hotel booking pages run by a subsidiary and confirmed unauthorized access. On October 26 it disclosed that up to about 40,000 booker records and up to about 2.6 million logged-in user records were targeted.

    Official announcement: Rakuten Group (Rakuten Travel Xchange) (Open external link)

    Data confirmed as targetedUnauthorized access

    Up to approx. 40,000 bookers and up to approx. 2.6 million logged-in usersPayment data (issuer number, last four digits, name, expiry) for up to about 36,000 bookers is a subset. Overlap between bookers and logged-in users is not stated. Full card numbers, passwords, ID documents and addresses are excluded.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  42. Second report: counts of possible exposure

    Joshin DenkiInternal systems and some services

    Joshin detected unauthorized access on October 16, restricted external connections and suspended some services. Its October 26 second report discloses possible exposure of up to about 6 million member-database records, 230,000 subscription records and 800 renovation-photo records.

    Official announcement: Joshin Denki (Open external link)

    Possible leakUnauthorized accessSome services suspended following external connection restrictions.

    Up to about 6 million member records, 230,000 subscription records and 800 renovation photo records (possible)All are maximum counts of possible exposure; the renovation photos include two driver-licence images, one My Number card and five bank account numbers. The company says these are not confirmed leak counts and it holds no card data.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Second report: counts of possible exposureOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  43. Taito City (vendor Mirabo)Taito City disability support app “Sasaeru”

    Taito City announced on October 26 that its contractor Mirabo reported on October 23 that an administrator account had been improperly created and member registration data improperly downloaded. The cause is attributed to a design-stage flaw in account registration and permission management.

    Official announcement: Taito City (vendor Mirabo) (Open external link)

    Leak confirmedIncident at a vendorNew member registration is suspended (as of October 26).

    197 email addresses, relationship to the person with a disability, and disability categoryNo counts are given for the relationship and disability-category items. Names, addresses and phone numbers are stated to be excluded.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-05

  44. Update

    Maruki Medical SystemsCore system (ordering, purchasing, warehouse management)

    Maruki Medical Systems’ servers were attacked on October 15, taking its core system fully down and halting order intake and shipping. An October 26 update confirmed unauthorized external access; impact on customer and supplier data and any leakage are still being checked.

    Official announcement: Maruki Medical Systems (Open external link)

    Under investigationCyberattackThe core system went fully down and order intake and shipping were temporarily suspended; orders are accepted by fax to branches until recovery.

    Whether data leaked is under investigationThe source does not disclose an information count.

    Timeline and sources (2)
    Timeline and sources
    1. Order and shipping suspension announcedOfficial announcement (Open external link)
    2. UpdateOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  45. Rakuten GroupRakuten Travel multilingual booking site

    Rakuten detected possible unauthorized access to its multilingual booking site on October 20 and fixed it on the 21st. On October 26 it disclosed that up to about 860,000 logged-in user records and up to about 40,000 property-staff account records were targeted.

    Official announcement: Rakuten Group (Open external link)

    Data confirmed as targetedUnauthorized access

    Up to approx. 860,000 logged-in users and up to approx. 40,000 property-staff accountsUsers’ names, emails, phones and countries of residence, and property staff’s account names and emails on the admin screen.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  46. Furukawa Electric Power SystemsShipping-management web system

    After detecting anomalies on October 14, the company identified possible unauthorized access and stopped its shipping-management web system. It is investigating potential exposure of customer and recipient company names, personal names, addresses and phone numbers; card and bank-account information is excluded.

    Official announcement: Furukawa Electric Power Systems (Open external link)

    Possible leakUnauthorized accessThe web system and server were stopped on October 14; order-taking and shipping operations continue normally.

    Count under investigationThe source does not disclose an information count.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-28

  47. Bandai LogipalShipping-management system

    Unauthorized access was detected on October 21, and possible exposure of delivery-recipient names, addresses and phone numbers was identified on October 22. Logistics systems were suspended and external specialists are investigating.

    Official announcement: Bandai Logipal (Open external link)

    Possible leakUnauthorized accessLogistics system temporarily suspended while investigation and recovery proceed.

    Count under investigationThe source does not disclose an information count.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-28

  48. Third report / some exposure confirmed

    VALTECMOT/Cloud, attendance, booking and POS services

    VALTEC confirmed external transmission of some data after unauthorized access exploiting a vulnerability in its own service. User information from multiple services was exposed, and the personal-information count remains under investigation. Phased resumption of suspended services was planned from October 26.

    Official announcement: VALTEC (Open external link)

    Some exposure confirmed; scope under investigationUnauthorized accessMultiple services suspended; phased resumption was planned from October 26.

    1,213 customer company records and sales data for 875 companies; personal-information count under investigationOverlap between the company and sales-data figures and the number of personal-information records are unconfirmed; neither figure is included in the gross information total.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Third report / some exposure confirmedOfficial announcement (Open external link)

    Sources checked: 2026-10-27

  49. Investigation results and current response

    WASABI (October 14 incident)WASABI SWITCH

    WASABI confirmed leakage of order and other data from unauthorized access on October 14 and announced blocking the route and removing malware. Future Shop integration stopped on October 16. The scope remains under investigation; this is separate from the October 16–17 intrusion through another route.

    Official announcement: WASABI (October 14 incident) (Open external link)

    Leak confirmedUnauthorized accessIntegration with futureshop stopped at 17:40 on October 16. As of October 26 penetration testing was under way with no restart date; on October 30 the company issued preparation guidance for resuming Yahoo! Shopping and related integrations.

    Number under investigation

    Timeline and sources (3)
    Timeline and sources
    1. Initial reportOfficial announcement (Open external link)
    2. External integration suspendedOfficial announcement (Open external link)
    3. Investigation results and current responseOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  50. Third-party investigation report published

    PingCAPInternal systems

    PingCAP reported internal-system access and copying during September 9–October 7 (US time), exposing up to about 50,000 personal-data records in Japan. Account and transaction information are affected; support-ticket information was added on October 21. No unauthorized access to TiDB Cloud itself or card-data exposure was found.

    Official announcement: PingCAP (Open external link)

    Leak confirmedUnauthorized access

    Up to about 50,000 records in Japan

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Third-party investigation report publishedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  51. Exposed data fields corrected

    LAWSONLAWSON ID

    Unauthorized access to Lawson ID exposed 2,155,345 records. An October 24 update corrected that email addresses and newsletter data were not exposed, while dates of birth may have been.

    Official announcement: LAWSON (Open external link)

    Leak confirmedUnauthorized access

    2,155,345 records

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Exposed data fields correctedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  52. Chari-Loto“Chariloto” app

    Unauthorized access exploiting a vulnerability occurred on October 21; the app service was stopped on the 22nd and resumed on the 23rd. On October 24 Chari-Loto disclosed that data of 373 Charika members, including bank-account details, leaked.

    Official announcement: Chari-Loto (Open external link)

    Leak confirmedUnauthorized accessThe app service was stopped on October 22 and resumed on the 23rd after the vulnerability was fixed.

    373 membersMember data, bank-account data, card data (last four digits, expiry and others), Charika account data and betting history.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  53. Shizuoka CityLost-ticket forms at Ekipa underground parking

    After a caller demanded payment on October 23 for allegedly found lost-ticket forms, the city announced missing documents and possible personal-information exposure on October 24. The forms may contain names, addresses, phone and driver’s-license numbers; investigation and police consultation continue.

    Official announcement: Shizuoka City (Open external link)

    Possible leakLoss of media

    Affected people and document count unknownApproximately 300 forms is the caller’s claim, not a verified count, and is not included in totals.

    Timeline and sources
    Timeline and sources
    1. Possible exposure announcedOfficial announcement (Open external link)

    Sources checked: 2026-10-26

  54. PayCloud Holdings (Value Design)House e-money issuing service “Value Card”

    PayCloud Holdings announced on October 23 that the server of Value Card, a house e-money issuing service its subsidiary Value Design provides to issuers, suffered unauthorized access, and that on October 19 it confirmed the leak of 1,424,748 records of ID numbers, PINs and balances. It attributes the access to an exploited web-server vulnerability.

    Official announcement: PayCloud Holdings (Value Design) (Open external link)

    Leak confirmedUnauthorized access

    1,424,748 records (ID numbers, PINs and balances)Of these, 569,224 were issued IDs and 855,524 unissued IDs. The company states no personal data were involved. Issued IDs were at risk of misuse but have been dealt with, and no actual loss is reported.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. Announcement (exchange filing)Official announcement (Open external link)
    Related announcements (customers and principals)
    1. MOS Food Services (MOS Card) (Open external link) · Leak confirmed1,133,070 MOS Card numbers, PINs and balances

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-04

  55. Second report / retail-site impact

    CapcomCAPCOM ID and e-Capcom

    Capcom disclosed exposure of 11,774,247 CAPCOM ID email and identifier records on October 22. The October 23 update confirmed e-Capcom address and purchase-history exposure for 19 Japanese accounts among the 196 whose passwords were changed without authorization.

    Official announcement: Capcom (Open external link)

    Leak confirmedUnauthorized access

    11,774,247 records worldwideAdditional attributes for 43 accounts, 196 unauthorized password changes and 19 Japanese retail accounts are subsets; the headline is not a Japan-only count.

    Timeline and sources (2)
    Timeline and sources
    1. First reportOfficial announcement (Open external link)
    2. Second report / retail-site impactOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  56. Green MonsterFX Navi

    Investigation of October 17 access identified possible continuing acquisition of user information from a different IP address on April 27–30. The disclosed scope is about 6.19 million records; the API and authentication credentials were corrected.

    Official announcement: Green Monster (Open external link)

    Possible leakUnauthorized access

    About 6.19 million user-information recordsIncludes information that is not personal data. Approximately 66,003 email addresses and other fields are subsets.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  57. Fifth report / final counts and image-retention policy

    Park24 Group (Times Car / Times Club)

    The October 23 fifth report confirms exfiltration of 6,628,007 Times Car records and details the encrypted-ID-image investigation. Times Club also had exposure of some identity data, membership-card numbers, linked IDs and payment-card last-four digits. The group changed its policy to stop retaining ID images after registration.

    Official announcement: Park24 Group (Times Car / Times Club) (Open external link)

    Leak confirmedUnauthorized access

    6,628,007 Times Car recordsWithin the same account group, 1,464,800 ID images show exfiltration traces and 891,602 show access only. Overlap with Times Club’s five identity records, 135,436 linked IDs and other fields is unresolved.

    Timeline and sources (5)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)
    3. Third reportOfficial announcement (Open external link)
    4. FAQ updateOfficial announcement (Open external link)
    5. Fifth report / final counts and image-retention policyOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  58. Tracking resumed / maximum count disclosed

    Sagawa Express

    The October 23 update reports up to approximately 53.23 million potentially exposed personal-information records, including waybill, shipping-contract and Smart Club data, with duplication remaining. Web parcel tracking reopened, while some services remain suspended.

    Official announcement: Sagawa Express (Open external link)

    Possible leakUnauthorized accessWeb parcel tracking resumed October 23; the tracking API and specified booking and delivery-change services remain suspended.

    Up to approximately 53.23 million records, including duplicatesSubstantial duplication remains after partial deduplication. This is neither a unique-person count nor a count of confirmed exfiltration.

    Timeline and sources (5)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)
    3. Third reportOfficial announcement (Open external link)
    4. Fourth reportOfficial announcement (Open external link)
    5. Tracking resumed / maximum count disclosedOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  59. Yamada DenkiYamada Video / Smartphone Gold membership

    Unauthorized access to service-procedure screens prompted suspension of the affected Yamada Video and Smartphone Gold membership services. The impact on personal information is under investigation.

    Official announcement: Yamada Denki (Open external link)

    Under investigationUnauthorized accessAffected services suspended from about 16:13 on October 22; recovery outlook to be announced.

    Personal-data impact under investigationThe source does not disclose an information count.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-28

  60. Related customer disclosures

    Sankei Living ShimbunWeb membership and survey services

    The company detected unauthorized server access on October 16 and disclosed possible exposure of names, contact details and other data of web members, including former members, and survey users. Some web services are suspended. Tome City and Hiroshima Prefecture disclosed related program impacts on October 23.

    Official announcement: Sankei Living Shimbun (Open external link)

    Possible leakUnauthorized accessSome web services suspended, including browsing, registration, login, applications and surveys.

    Under investigation; overall count undisclosedCustomer disclosures are related information within the same incident and are not added to an unknown overall count.

    Timeline and sources (2) · Related announcements (2)
    Timeline and sources
    1. First report / partial service suspensionOfficial announcement (Open external link)
    2. Related customer disclosuresOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Tome City (marriage-support program) (Open external link) · Possible leak39 people
    2. Hiroshima Prefecture (prefectural newsletter) (Open external link) · Possible leak1,470 applications: 723 and 747 from the two issues

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-25

  61. Okinawa Tourist ServiceOTS Rent-a-Car and related services

    The October 23 update confirms leakage of some customer data, with a maximum scope of about 730,000 customers. Whether license images in a separate database leaked remains under investigation. New reservations for five services, including OTS Rent-a-Car, remain suspended.

    Official announcement: Okinawa Tourist Service (Open external link)

    Some leakage confirmedUnauthorized accessNew reservations suspended for five services; bookings completed by 16:30 on October 20 remain usable.

    Up to about 730,000 customers; up to 6,000 license images in a separate database remain under investigationThe confirmed portion is not separately quantified. The 6,000 images in a separate database are not added to the customer maximum.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  62. Possible viewing of registration data

    East Nippon ExpresswayDora-Tora and My Route

    The October 23 notice reports possible viewing of some Dora-Tora users’ emails, passwords, gender, prefecture and birth year following unauthorized access. Dora-Tora, My Route and route-email services have been suspended since October 21.

    Official announcement: East Nippon Expressway (Open external link)

    Possible leakUnauthorized accessDora-Tora, My Route and route-email services suspended; reopening undated.

    Affected count undisclosed

    Timeline and sources (2)
    Timeline and sources
    1. Services suspendedOfficial announcement (Open external link)
    2. Possible viewing of registration dataOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  63. Treasure FactoryHome-purchase and moving case-management system

    Unauthorized access and data acquisition were confirmed on October 20. External access and application forms were suspended, with reopening targeted for October 28. Store and app customer data is outside the affected system.

    Official announcement: Treasure Factory (Open external link)

    Leak confirmedUnauthorized accessExternal access and application forms suspended; October 28 is a planned reopening.

    746,277 customer records; 750 business-contact/employee records; 1,000 device recordsEleven customer records also include names and addresses; overlap with other categories is unresolved.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  64. Investigation and reopening preparations

    PapylessRenta!

    The October 23 notice reports possible leakage of some members’ email addresses and other information. Payment data is not held, and leakage or loss of purchase history and bookshelves has not been confirmed. Service remains suspended, with password resets planned at reopening.

    Official announcement: Papyless (Open external link)

    Possible leakUnauthorized accessService suspended for emergency maintenance; reopening undetermined.

    Affected count undisclosed

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Investigation and reopening preparationsOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  65. Bureau of Waterworks, Tokyo Metropolitan GovernmentExternal hard drives holding land-management records

    The Bureau of Waterworks announced on October 23 that on October 2 it found four external hard drives missing from a locked cabinet, with only their cases left. They held land-management records and personal data of 1,932 people.

    Official announcement: Bureau of Waterworks, Tokyo Metropolitan Government (Open external link)

    Lost; no leak confirmedLoss of media

    Personal data of 1,932 people (four hard drives)1,037 people from companies, the national government and municipalities, and 895 local residents and others. Most entries contain only names; some include addresses or phone numbers. No leak or other secondary harm has been confirmed so far.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-04

  66. Pizza Hut JapanPayment API for online orders

    Unauthorized access to the domestic ordering payment API on October 19 exposed customer IDs, emails, phone numbers, session-login tokens and transaction records. Credit card data is excluded; the scope remains under investigation.

    Official announcement: Pizza Hut Japan (Open external link)

    Leak confirmedUnauthorized access

    Count undisclosed

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  67. Third report: information possibly exposed

    The Japan Times / News2u Holdings

    Following the September 18 ransomware attack and an October 15 claim of data publication, the October 23 third report said possible exposure could not be ruled out for business-partner data (including bank details), employee and former-employee data and some My Number, passport and residence-card information on an administrative file server used until August 2022. Digital, subscriber and payment systems run separately.

    Official announcement: The Japan Times / News2u Holdings (Open external link)

    Possible leakRansomware

    Affected count undisclosed

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Third report: information possibly exposedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  68. Investor Q&A

    Digital ArtsCloud-service operations and internal environments

    An October 9 inspection found access traces dating back to around July 2025. On October 21, Digital Arts disclosed possible viewing of some customer data across six cloud services, including i-FILTER@Cloud, through stolen operational credentials. As of noon that day, exfiltration and secondary harm were unconfirmed. Credentials were invalidated or replaced.

    Official announcement: Digital Arts (Open external link)

    Possible leakUnauthorized access

    Affected count undisclosed

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Investor Q&AOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  69. Second report / affected counts

    M3MR-kun

    The October 23 second report confirms exposure of 25,775 members and others and 2,260 pharmaceutical-company contacts. Data includes names, workplaces and some email addresses; login passwords and m3 points are excluded.

    Official announcement: M3 (Open external link)

    Leak confirmedUnauthorized access

    25,775 m3.com members and others; 2,260 pharmaceutical-company contactsThe six and 264 people with email-address exposure are subsets of their respective groups.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Second report / affected countsOfficial announcement (Open external link)

    Sources checked: 2026-10-25

  70. Net ProtectionsInvoice-reissue system for “NP Atobarai”

    Net Protections found on October 14 that automated, continuous requests to its invoice-reissue system had accessed part of customers’ personal data. On October 22 it disclosed 28,884 affected transactions.

    Official announcement: Net Protections (Open external link)

    Access confirmedUnauthorized accessThe affected system is to restart after safety checks; NP Atobarai itself operates normally.

    28,884 transactionsNames and addresses (company and department for business users) and whether invoices were returned.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  71. Technohill (MHLW contractor)1FEdu radiation-exposure reduction training website

    On October 22, MHLW confirmed exposure of six trainees’ email addresses and passwords and unauthorized logins using them following an attack on its contractor’s training website. The database holds information for up to 595 trainees including those six, potentially exposed. The service remains suspended.

    Official announcement: Technohill (MHLW contractor) (Open external link)

    Partial leak confirmedUnauthorized accessService suspended and external access blocked.

    Six confirmed / up to 595 people including the sixCredentials for six people were confirmed exposed. The maximum 595 database subjects include these six; they are not added again.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-23

  72. Third report: all functions resumed

    Japan Football AssociationJFA Passport

    Following attacks on the official app on October 17, JFA suspended some system integrations. Its October 21 investigation found no personal-data leakage or impact on related systems from this incident. The October 22 third report said safety checks and necessary measures were complete and all app functions had resumed.

    Official announcement: Japan Football Association (Open external link)

    Leak not confirmedUnauthorized accessSome system integrations had been suspended; on October 22 service resumed for all app functions. The latest version of the app is required.

    No personal-data exposure found in the investigation

    Timeline and sources (3)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. UpdateOfficial announcement (Open external link)
    3. Third report: all functions resumedOfficial announcement (Open external link)

    Sources checked: 2026-11-03

  73. Internal systems restored

    Kaneko Agricultural Machinery

    After ransomware disrupted systems early on July 9 and partial recovery was announced on August 20, Kaneko announced full internal-system recovery and normal operations on October 22. Its website remains a simplified version while a replacement is prepared.

    Official announcement: Kaneko Agricultural Machinery (Open external link)

    Under investigationRansomwareInternal systems restored and normal operations announced on October 22; the website remains a simplified version.

    Scale not disclosed

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Internal systems restoredOfficial announcement (Open external link)

    Sources checked: 2026-10-23

  74. Potential personal-data exposure disclosed

    PIECEProperties’ Booking.com management accounts

    Unauthorized access to properties’ Booking.com management accounts on October 13 caused unfulfillable bookings and fraudulent messages. An October 22 notice reports possible access to guests’ names, addresses, phone numbers and emails; whether data leaked and the scope remain under investigation.

    Official announcement: PIECE (Open external link)

    Possible leakUnauthorized access

    Affected number and period under investigationThe source does not disclose an information count.

    Timeline and sources (2)
    Timeline and sources
    1. Fraudulent bookings disclosed (date in notice body)Official announcement (Open external link)
    2. Potential personal-data exposure disclosedOfficial announcement (Open external link)

    Sources checked: 2026-10-28

  75. Update

    RecruitCarsensor net, app and C-match

    After detecting suspicious access on October 17, Recruit suspended all related services around 17:00. On October 21 it reported possible exposure of up to 3,709,551 records: 3,210,421 inquiries, 5,289 reviews, 483,168 dealer records and 10,673 staff/contractor records. No reopening date was announced.

    Official announcement: Recruit (Open external link)

    Possible leakUnauthorized accessAll related services suspended from around 17:00 on October 17.

    Up to 3,709,551 recordsTotal across inquiries, reviews, dealers and staff. The 447,670 records with detailed addresses are a subset.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. UpdateOfficial announcement (Open external link)

    Sources checked: 2026-10-22

  76. Restoration status updated

    UP Inc.Rakushin, Shingakukan and related websites

    Unauthorized access exploiting a website plugin was detected on August 24. On September 4, UP reported possible viewing of data on 10 applicants and three internal administrators, without confirmed exfiltration. As of October 21, 17 sites had been restored and three accepted inquiries through interim pages.

    Official announcement: UP Inc. (Open external link)

    Possible leakUnauthorized accessAs of October 21, 17 sites were restored and three accept inquiries through interim pages; member pages operate normally.

    10 applicants and three administrators

    Timeline and sources (3)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Restoration updateOfficial announcement (Open external link)
    3. Restoration status updatedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  77. AEON

    AEON detected unauthorized access to some group websites and reported safety checks and investigation of the cause and whether personal information was exposed. It said recovery work was under way.

    Official announcement: AEON (Open external link)

    Under investigationUnauthorized access

    Affected scope and count under investigationThe affected sites and information count have not been disclosed.

    Timeline and sources
    Timeline and sources
    1. Announcement / investigation ongoingOfficial announcement (Open external link)

    Sources checked: 2026-10-27

  78. Second report: scope narrowed to up to 18,000 records

    NIFTYLine application and reception management system

    The company confirmed unauthorized access to an internal management system on October 19 and initially disclosed up to 542,513 records. Its October 21 second report narrowed the scope to @nifty Hikari applications since 2019 (excluding its own website) and revised the possibly affected data to up to 18,000 records, covering member IDs, names, addresses and phone numbers; email addresses were removed from scope.

    Official announcement: NIFTY (Open external link)

    Possible leakUnauthorized access

    Up to 18,000 recordsRevised from the first report’s up to 542,513 records across three services after narrowing the scope to @nifty Hikari.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Second report: scope narrowed to up to 18,000 recordsOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  79. Security measures announced

    The Monogatari Corporation

    The company disclosed leakage of Yakiniku King app member data. The leak count differs from the total number of registrations.

    Official announcement: The Monogatari Corporation (Open external link)

    Leak confirmedUnauthorized access

    10,788,963 records

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Security measures announcedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  80. Second report

    Eyelash GarageWholesale e-commerce site for professionals

    Eyelash Garage’s e-commerce server was breached between October 10 and 12, detected and blocked on the 13th. On October 15 it confirmed that 49,191 stored customer records leaked.

    Official announcement: Eyelash Garage (Open external link)

    Leak confirmedUnauthorized accessThe second report states that the e-commerce site operates normally.

    49,191 recordsCompany and salon names, names, phones, emails and password hashes; addresses, purchase history and card data are not found to have leaked.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  81. Password resets reopened

    Z-kaiZ-ID system

    Z-kai disclosed on October 19 that 13 abnormal password changes occurred early on October 15, potentially exposing names, emails and Z-IDs. It suspended affected accounts and password resets; on October 20 it reported reopening reset functionality after security measures.

    Official announcement: Z-kai (Open external link)

    Possible leakUnauthorized accessThirteen affected accounts temporarily suspended; password reset functionality was reported reopened on October 20.

    13 accounts

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Password resets reopenedOfficial announcement (Open external link)

    Sources checked: 2026-10-23

  82. Fuji TelevisionProgram publicity system

    On October 20, Fuji disclosed unauthorized access the previous night to its program publicity system. Names, companies and email addresses of media contacts may be affected, up to 730 records; the scope including stored materials is under investigation. Viewer personal information was not registered in that system.

    Official announcement: Fuji Television (Open external link)

    Possible leakUnauthorized accessThe affected system was suspended after unauthorized access was detected.

    Up to 730 records

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-23

  83. Housing Energy Efficiency 2024 Campaign secretariat (Hakuhodo)

    On October 20, MLIT reported possible exposure of data for 23,918 representatives, sole proprietors and subsidy contacts following unauthorized manipulation of the secretariat’s system. Consumer-data exposure was unconfirmed; registered-business data for equivalent programs in other years was reported unaffected.

    Official announcement: Housing Energy Efficiency 2024 Campaign secretariat (Hakuhodo) (Open external link)

    Possible leakUnauthorized accessAll system functions suspended. Only functions needed for completion reports and related work are planned to reopen after checks.

    23,918 people at 16,950 businesses, preliminaryPeople and business counts describe the same scope and are not added together.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-23

  84. NECCustomer systems and shared cloud storage accessed through a vendor

    NEC announced on October 20 that a late-September attack on a vendor led to unauthorized access using stolen credentials. It confirmed system outages caused by file encryption and exposure of shared-cloud files containing personal and system information. Customer names and counts were not disclosed.

    Official announcement: NEC (Open external link)

    Leak confirmedUnauthorized accessFile encryption made customer systems unavailable; restoration scope is not disclosed.

    Number undisclosed

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-21

  85. Announcement

    Kushiro City (contractor Portas)Contractor server for managing school learning devices

    Portas, the contractor managing school learning devices, suffered a ransomware attack on its internal server on August 29, and traces of unauthorized access were found on a server holding the city’s device settings. Kushiro announced on October 15 that student and staff account data may have leaked.

    Official announcement: Kushiro City (contractor Portas) (Open external link)

    Possible leakRansomware

    Account data by year (up to 11,106 student records and others)School names, names, kana, account names and passwords of elementary and junior-high students and staff by year (2020, 2025, 2026; likely overlapping) and admin passwords for all 39 schools. Hokuyo High School files hold 179–200 records each. No total is published.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement (elementary and junior high schools)Official announcement (Open external link)
    2. Announcement (Hokuyo High School)Official announcement (Open external link)

    Sources checked: 2026-11-02

  86. EC app reopened

    AenaOfficial online store and app

    The EC app reopened at noon on October 19 after safety checks, with a password reset on first launch. The October 14 initial report confirmed unauthorized viewing of member pages and possible exposure of names, contacts, delivery details and other information for up to 817,215 members.

    Official announcement: Aena (Open external link)

    Leak confirmedUnauthorized accessEC app resumed at noon on October 19; the notice does not establish reopening of the entire online store.

    Up to 817,215 peopleUnauthorized viewing is confirmed; the maximum scope is counted only as possible exposure.

    Timeline and sources (3)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Planned reopeningOfficial announcement (Open external link)
    3. EC app reopenedOfficial announcement (Open external link)

    Sources checked: 2026-10-20

  87. Reservation function resumed

    LAWSONApp reservations

    The October 19 update announced that the suspended app reservation function had resumed. The reported exposure count remains 26 records, including names, phone numbers and partial card numbers.

    Official announcement: LAWSON (Open external link)

    Leak confirmedUnauthorized accessReservation function resumed October 19; app update required.

    26 recordsNot added to the LAWSON ID event.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Reservation function resumedOfficial announcement (Open external link)

    Sources checked: 2026-10-20

  88. Entouch / Toho HoldingsSystems holding healthcare-professional and related data

    Entouch confirmed external data exfiltration at 16:00 on October 13. The data includes healthcare professionals’ names, institutions and prefectures, administrator and eMR names and email addresses, and appointment information. It reported no impact on normal operations and none identified at other group companies.

    Official announcement: Entouch / Toho Holdings (Open external link)

    Leak confirmedUnauthorized access

    Number undisclosed

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-20

  89. Nikkei (development cloud)Cloud used for system development

    Nikkei disclosed unauthorized access to its development cloud on October 7 using stolen credentials. About 150,000 records contain names, contact details or other personal fields, while about 1.68 million contain only identifiers that cannot identify individuals alone. Credentials were disabled. Card data was not included, and no system outage had been identified as of October 16.

    Official announcement: Nikkei (development cloud) (Open external link)

    Leak confirmedUnauthorized access

    Approximately 1.83 million recordsAbout 120,000 email records are within the 150,000 subset. The 1.83 million total is counted once; separate from the Google Workspace and Microsoft 365 incidents.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-18

  90. Password update

    SourcenextMember information

    Sourcenext detected unauthorized access to its member-information API on October 13 and blocked it that day. It confirmed external exfiltration and disclosed the potentially affected scope, including names, addresses, contact details and passwords. Card information is not stored on its servers. An October 16 update said previous passwords had been changed.

    Official announcement: Sourcenext (Open external link)

    Leak confirmedUnauthorized access

    22,519,960 possibly exposed recordsExfiltration is confirmed, but not for all 22,519,960 records; the full scope is counted only as possible exposure.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Password updateOfficial announcement (Open external link)

    Sources checked: 2026-10-17

  91. Announcement

    Yamato TransportKuroneko deferred-payment service

    Yamato suspended the service after detecting unauthorized access on September 28 and reopened it at 13:00 on October 9. Its fourth report on October 16 confirmed exfiltration of customer, delivery-recipient and merchant data. Card data and passwords were not included, and exfiltration of previously suspected billing amounts, receivable balances and employee names was not found.

    Official announcement: Yamato Transport (Open external link)

    Leak confirmedUnauthorized accessService reopened at 13:00 on October 9.

    About 5.26 million customer records, 50,000 delivery-recipient records and 4,100 merchant recordsAbout 490,000 email records are a customer-data subset. Overlap across customer, recipient and merchant categories is unresolved; excluded from the gross reference sum.

    Timeline and sources (2)
    Timeline and sources
    1. Third report / reopeningOfficial announcement (Open external link)
    2. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-17

  92. Final report / confirmed scope

    Estore

    The October 16 final report confirmed exfiltration through an application vulnerability from May 21 to August 1. The estimate matches customer, member, store-operator and affiliate records. Full card numbers and security codes were not included. Email/FTP credentials and payment-account details previously listed in the second report were excluded.

    Official announcement: Estore (Open external link)

    Leak confirmedUnauthorized access

    Approximately 23,356,000 people across 7,858 storesFinal-report estimate after matching records; some duplication may remain. Partial card information for about 2,096,900 people is a subset. Store counts are not added, and this replaces the earlier maximum cumulative count.

    Timeline and sources (2) · Related announcements (1)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Final report / confirmed scopeOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Designphil (Open external link) · Leak confirmedNumber not disclosed

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-18

  93. Announcement

    Golf Digest OnlineInternal systems and member information

    An unauthorized-access incident caused disruption on October 13. Findings announced on October 16 confirmed exfiltration of 1,789 employee, former-employee and vendor records and possible queries of 55 customer records. Of the latter, 51 contain identifiers only and four include personal information. Payment-data exposure has not been confirmed.

    Official announcement: Golf Digest Online (Open external link)

    Leak confirmedUnauthorized accessCoupon use and prepaid-ticket purchases affected, with delivery delays; full restoration not announced.

    1,789 employee/vendor records; 55 customer records potentially affected

    Timeline and sources (2)
    Timeline and sources
    1. Service-impact noticeOfficial announcement (Open external link)
    2. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-21

  94. Sumitomo Mitsui DS Asset ManagementDirect investment-trust service

    Unauthorized access at a transaction service provider triggered a precautionary shutdown and temporary loss of My Page access. Normal access was restored; no impact on account data or transactions had been identified at the announcement.

    Official announcement: Sumitomo Mitsui DS Asset Management (Open external link)

    Leak not confirmedIncident at a vendorMy Page login unavailable from about 19:50 on October 15 to 06:00 on October 16; restoration announced.

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Outage and restoration noticeOfficial announcement (Open external link)

    Sources checked: 2026-10-19

  95. Second report / alleged publication under investigation

    Keio Group

    Keio identified ransomware-related system failures on September 26. Its October 16 second report says a group claiming responsibility alleged it had published some group data. Personal-data leakage remains under investigation; the attacker’s claim is not treated as confirmed exposure.

    Official announcement: Keio Group (Open external link)

    Under investigationRansomwareBusiness systems at some group companies affected; recovery work continues in the second report. The initial notice reported no effect on train operations.

    Number under investigation

    Timeline and sources (2)
    Timeline and sources
    1. Initial reportOfficial announcement (Open external link)
    2. Second report / alleged publication under investigationOfficial announcement (Open external link)

    Sources checked: 2026-10-19

  96. Related update

    Kobo (Hassha Orai Net)Partner API server for bus booking site Hassha Orai Net

    Kobo, operator of Hassha Orai Net, found suspicious access to its partner API server from September 16 to 19, detected on October 13, with traces that some booking data leaked. On October 15 it disclosed up to 8,341 bookings as possibly affected.

    Official announcement: Kobo (Hassha Orai Net) (Open external link)

    Possible leakIncident at a vendor

    Up to 8,341 bookings (5,614 people)Katakana booking names, phone numbers and booked-bus details. The 8,341 bookings and 5,614 people describe the same scope and are still being finalized. Card, bank, address, email and password data were not stored.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Hokkaido Chuo Bus (Open external link) · Possible leakApprox. 5,600 people (citing Kobo’s figure)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-02

  97. BK Japan HoldingsBurger King official app

    BK Japan confirmed on October 13 that unauthorized access between October 2 and 7 had exfiltrated member data, including email addresses, names, phone numbers and dates of birth. Card data is not stored on its servers, and password leakage has not been confirmed. It blocked the access route and is investigating with external specialists.

    Official announcement: BK Japan Holdings (Open external link)

    Leak confirmedUnauthorized access

    Approximately 11.18 million recordsPublished approximate record count; individual data fields are not added.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-17

  98. Usage history service resumed

    nimoca

    The company disclosed a data leak caused by unauthorized access and suspended its usage-history service, then announced on October 15 that the service had resumed.

    Official announcement: nimoca (Open external link)

    Leak confirmedUnauthorized accessOn October 15 the company announced the usage history service had resumed after investigation and countermeasures, stating no passwords were leaked.

    521 records

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Usage history service resumedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  99. Third report / scope

    MoonStar

    In its October 15 third report, MoonStar concluded information had been stolen after finding impersonation emails containing private past-order details. Leakage was considered likely between May 14 and 19, with up to 593,000 people potentially affected. Card data and store passwords were not held on the affected server.

    Official announcement: MoonStar (Open external link)

    Theft confirmed; full scope remains possibleUnauthorized access

    Up to 593,000 peopleTheft was inferred from impersonation emails containing private order data; the maximum scope is counted only as possible exposure.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Third report / scopeOfficial announcement (Open external link)

    Sources checked: 2026-10-17

  100. RecruitStudy Sapuri for schools / teacher notifications

    A permissions defect allowed a few users to view attachments they were not entitled to access. Recruit said it fixed the defect by September 30 and confirmed the users had not saved, shared or otherwise used the files. It described no external attack and will work with schools and authorities where files contain personal information.

    Official announcement: Recruit (Open external link)

    Unauthorized viewing confirmedMisconfiguration

    483 files sent by 139 schoolsCounts viewed attachments. The number containing personal information and the number of affected people were not disclosed; excluded from gross information totals.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-16

  101. Update

    Tokyo Metro

    Tokyo Metro announced on September 27 that about 59,000 email addresses may have been viewed or taken through unauthorized access to its Metpo member service. An October 15 update said the scope was unchanged and confirmed that only addresses whose delivery had been stopped as undeliverable were taken.

    Official announcement: Tokyo Metro (Open external link)

    Leak confirmedUnauthorized access

    About 59,000 email-address recordsEmail addresses of Metpo members whose delivery had been stopped because messages could not be delivered. The affected server held no member information other than email addresses.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Update (acquisition confirmed; scope unchanged)Official announcement (Open external link)

    Sources checked: 2026-11-04

  102. Suzuki Nirin (Suzuki World)Suzuki World website

    Suzuki Nirin detected unauthorized access to the Suzuki World website on July 29, closed it and found some pages defaced. On October 14 it disclosed that about 4,400 inquiry-form log entries may have been viewed or obtained.

    Official announcement: Suzuki Nirin (Suzuki World) (Open external link)

    Possible leakUnauthorized accessThe site was closed on detection on July 29 and has reopened after fixes and checks; the reopening date is not stated.

    Approx. 4,400 recordsNames, emails, phones, addresses and inquiry text in the inquiry-form log; no sign of outflow found. The site operator Chubu Insatsu published the same notice.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Chubu Insatsu (site operator) (Open external link) · Possible leakApprox. 4,400 records (same figure)

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-02

  103. News posting

    ToypoStore app platform “Toypo App”

    On October 4 Toypo confirmed unauthorized access exploiting an access-control flaw that let authenticated users retrieve other users’ data. On October 14 it disclosed that registration data of 697,209 users may have leaked.

    Official announcement: Toypo (Open external link)

    Possible leakUnauthorized access

    697,209 usersPhone numbers and user IDs, plus names, emails, birth dates, gender and addresses where registered; not every item for every user. Passwords, payment data and usage history are excluded. Disclosures by adopting stores are not added.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. News postingOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  104. Sapporo International UniversityEmail / Microsoft 365

    Phishing since July 9 led to misuse of multiple email accounts and large volumes of malicious messages sent inside and outside the university. The October 14 findings identify mailbox access and other unauthorized traces, but do not confirm external leakage of personal data.

    Official announcement: Sapporo International University (Open external link)

    External leakage not confirmedUnauthorized accessForensic investigation and removal of unauthorized access mechanisms were completed, with normal operations resumed.

    Multiple accounts; information count undisclosedThe source does not disclose an information count.

    Timeline and sources
    Timeline and sources
    1. Investigation results / remediation completedOfficial announcement (Open external link)

    Sources checked: 2026-10-28

  105. Second report / confirmed exposure count

    GMO Research & AI

    The October 14 second report confirmed 894,082 personal-data records extracted, replacing the initial maximum of 948,498. All member passwords were invalidated on October 7; the service remains suspended while the investigation continues.

    Official announcement: GMO Research & AI (Open external link)

    Leak confirmedUnauthorized accessService suspended from October 3; no reopening date in the second report.

    894,082 recordsThe second report confirms the personal-data total. The previous maximum of 948,498, 9,068 records with personal data already deleted, 45,348 not extracted and 611 unauthorized point exchanges are not added.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Second report / confirmed exposure countOfficial announcement (Open external link)

    Sources checked: 2026-10-19

  106. Third report

    Ride On Express HoldingsGin no Sara, Kamatora and Sushi Joto official websites and apps

    After detecting unauthorized access from October 5, the company stopped its systems on October 7 following a server operator report that a ransomware attack made data extraction and recovery difficult. Its third report on October 13 disclosed that up to about 6.5 million personal data records on official websites and apps may have leaked; credit card data was not held.

    Official announcement: Ride On Express Holdings (Open external link)

    Possible leakRansomwareOrders via official websites and apps suspended; phone, in-store, Demae-can and Uber Eats orders continue

    Up to about 6.5 million recordsNot the number of confirmed leaked records.

    Timeline and sources (3)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)
    3. Third reportOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  107. Renewed suspension and reopening plans

    Commune

    After confirming leakage affecting about 307,000 members and starting limited reopening on October 8, Commune suspended services again on October 10. Its October 13 notice planned restricted reopening for requesting customers from October 16 and said no new unauthorized access or leakage had been confirmed since the October 9 announcement.

    Official announcement: Commune (Open external link)

    Leak confirmedUnauthorized accessSuspended again from October 10; limited reopening planned from October 16

    About 307,000 members (estimated)Includes about 126,000 with email addresses and about 42,000 employee and demo accounts.

    Timeline and sources (2) · Related announcements (7)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Renewed suspension and reopening plansOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. WingArc1st (Open external link) · Possible leakAbout 1,200 people (estimated)
    2. Suzuki (Open external link) · Possible leakAbout 3,000 people
    3. LIXIL (Open external link) · Possible leakNumber not disclosed
    4. CHITOSE (Open external link) · Possible leakUp to 843 people; service suspended, reopening date unconfirmed
    5. VALX (Open external link) · Possible leak2,950 people potentially affected (estimated)
    6. Yamaha Motor / PAS Life (Open external link) · Possible leakAbout 1,600 people
    7. LY Corporation / DS.LAB (Open external link) · Possible leak1,750 people

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-16

  108. Third report / investigation results

    Kindal

    The completed investigation confirmed leakage affecting 136,464 people. Staff credentials were stolen through phishing; the company introduced passkey-based two-step authentication and restricted export permissions.

    Official announcement: Kindal (Open external link)

    Leak confirmedUnauthorized access

    136,464 peopleIncludes 109,311 people whose address information was involved; this subset is not added.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Third report / investigation resultsOfficial announcement (Open external link)

    Sources checked: 2026-10-13

  109. Updated disclosure

    HOTELIER

    The company disclosed leakage of accommodation reservation information, including names, contact details and stay dates.

    Official announcement: HOTELIER (Open external link)

    Leak confirmedUnauthorized access

    7,919 people across 8 propertiesThe October 13 notice retains 7,919 people across 8 properties; property counts and related disclosures are not added.

    Timeline and sources (2) · Related announcements (1)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Updated disclosureOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Daiei Sangyo / Grand Inn Canalside (Open external link) · Possible leakNumber not disclosed

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-14

  110. Applabo

    The company identified unauthorized access to its mail-server database on October 11. It reported possible viewing of email addresses and encrypted passwords, and blocked access and changed credentials.

    Official announcement: Applabo (Open external link)

    Possible leakUnauthorized access

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-13

  111. Related update

    Temairazu

    The company disclosed that unauthorized access to its hotel reservation management system may have allowed reservation holders’ contact and booking data to be viewed or taken; an October 9 disclosure put the scope at up to about 4.45 million people. Functions suspended on September 24 were restored the same day.

    Official announcement: Temairazu (Open external link)

    Possible leakUnauthorized accessNormal operation announced

    Up to about 4.45 million peopleReservation holders’ contact details such as names, phones and emails, and booking data; no card data is held. Individual hotel notices are not added.

    Timeline and sources (3) · Related announcements (10)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)
    3. Exchange disclosure: up to about 4.45 million peopleOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Chojuso / Hotel Crystal Palace (Open external link) · Possible leakNumber not disclosed or under investigation
    2. Yumotokan (Open external link) · Possible leakNumber not disclosed or under investigation
    3. FJ Resort Management / Gyokuhokan (Open external link) · Possible leakNumber not disclosed or under investigation
    4. Holonic (Open external link) · Possible leakNumber not disclosed or under investigation
    5. Kur and Hotel (Open external link) · Possible leakNumber not disclosed or under investigation
    6. Resort Hanayunomori / Hana Hotel (Open external link) · Possible leakNumber not disclosed or under investigation
    7. Nikken Hotel Management / Feliz Villa Suite (Open external link) · Possible leakNumber not disclosed or under investigation
    8. Capital-Zenrin / Feriendorf (Open external link) · Possible leakNumber not disclosed; fraudulent-email warning updated
    9. Espacio / two hotels (Open external link) · Possible leakNumber not disclosed
    10. Hotel Grand Hill Ichigaya (Open external link) · Possible leakPossible viewing or acquisition of reservation data; number undisclosed.

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-11-02

  112. BOOKOFF Group Holdings

    Unauthorized access to a membership system caused a data leak. The maximum affected figure is not a count of unique people.

    Official announcement: BOOKOFF Group Holdings (Open external link)

    Leak confirmedUnauthorized access

    Up to about 6.43 million membership-number recordsCount of membership numbers, not unique people.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  113. dip

    Some email addresses for Baitoru and Baitoru NEXT leaked. The maximum figure is the potentially affected scope.

    Official announcement: dip (Open external link)

    Leak confirmedUnauthorized access

    Up to 3,885,771 recordsLeakage of every record in the maximum figure has not been confirmed.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  114. REXT / REXT Holdings

    Ransomware stopped POS, accounting and other systems. The disclosure separates publicly exposed data from potentially leaked data. All stores reopened.

    Official announcement: REXT / REXT Holdings (Open external link)

    Part confirmed / part possibleRansomwareAll stores reopened

    310 files publicly exposed; 1,044,906 records potentially affected27 applicants and employees were notified. These figures use different units and scopes and are not added.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  115. Precautionary portal suspension

    Anabuki Housing Service

    External file leakage was confirmed and the May investigation refined the possibly affected scope. During ongoing safety checks following the February attack, the company suspended its owners portal as a precaution from noon on October 9.

    Official announcement: Anabuki Housing Service (Open external link)

    Leak confirmedRansomwareOwners portal suspended as a precaution

    207,773 possibly affected recordsThe figure does not confirm leakage of all 207,773 records.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Precautionary portal suspensionOfficial announcement (Open external link)

    Sources checked: 2026-10-13

  116. Second report

    Uzabase / NewsPicks

    Customer data may have leaked from a business-management tool. Full card numbers and security codes were not held, and service continued.

    Official announcement: Uzabase / NewsPicks (Open external link)

    Possible leakUnauthorized access

    Up to 323,000 email records; 362,000 partial card-data recordsMaximum figures for separate data fields, not a combined count of people.

    Timeline and sources (2)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  117. Enecom

    Unauthorized access to the internal network was identified on October 6. The company found traces of file exfiltration, while customer-data impact remains under investigation; it reported no effect on its services.

    Official announcement: Enecom (Open external link)

    Possible leakUnauthorized access

    Number under investigationTraces of file exfiltration were found; customer-data exposure remains under investigation.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-13

  118. coconala

    Unauthorized access exposed recruitment documents. Credit card information and passwords were outside the affected scope.

    Official announcement: coconala (Open external link)

    Leak confirmedUnauthorized access

    449 resumes; 1,845 employment-history documents

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  119. Resorttrust

    The company disclosed leakage of member and reservation information. Figures for the two categories are kept separate.

    Official announcement: Resorttrust (Open external link)

    Leak confirmedUnauthorized access

    About 26,000 member records; about 36,000 reservation records

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  120. Lashinbang

    The company disclosed possible leakage of purchase-related data. An update excluded identity-document images, card data and passwords.

    Official announcement: Lashinbang (Open external link)

    Possible leakUnauthorized access

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  121. Adventureskyticket: business systems

    The company disclosed leakage or possible leakage from skyticket business-management systems, including refund bank-account data.

    Official announcement: Adventure (Open external link)

    Leak / possible leakUnauthorized access

    17,780 records, including duplicatesOther affected information is still being counted. Not added to the other two events.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  122. Adventureskyticket: bus reservations

    A third party systematically viewed bus-booking confirmation pages that required no login. The issue was fixed on October 1.

    Official announcement: Adventure (Open external link)

    Viewed / possibly viewedMisconfiguration

    About 12,000 reservationsNot a count of people including companions. Not added to the other two events.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  123. Related update

    Scala Communications

    Unauthorized access to an inquiry-management system may have exposed inquiry information of customer companies.

    Official announcement: Scala Communications (Open external link)

    Possible leakUnauthorized access

    Up to 713,126 cumulative inquiry recordsCount of inquiries, not unique people.

    Timeline and sources · Related announcements (5)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Daiwa Securities (Open external link) · Possible leakAbout 110,000 people; about 220,000 cumulative inquiry records
    2. Sompo Japan / SMILING ROAD (Open external link) · Possible leakAbout 60,000 cumulative inquiry records
    3. Citizen Watch (Open external link) · Possible leakAbout 100,000 people
    4. The Shikoku Bank (Open external link) · Possible leakNotice referring customers to Daiwa Securities
    5. ORIX Life Insurance (Open external link) · Possible leakAbout 26,500 cumulative inquiry records

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-14

  124. Hi-Ho

    The company disclosed unauthorized acquisition of information through account logins. The figure counts contracts.

    Official announcement: Hi-Ho (Open external link)

    Leak confirmedUnauthorized access

    38,509 contractsA customer with multiple contracts may be counted more than once.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  125. H.I.S. (Thai Subsidiary H.I.S. TOURS)

    Unauthorized access to a Thai subsidiary file server may have exposed passport information (including passport numbers, expiry dates, names and birth dates) and allergy information for up to 627 customers who traveled from Japan to Thailand.

    Official announcement: H.I.S. (Thai Subsidiary H.I.S. TOURS) (Open external link)

    Possible leakUnauthorized access

    Up to 627 peoplePhone numbers, addresses, email addresses and card data were not included.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  126. TODA

    The company disclosed leakage of business-partner and employee information. Employee data covered 4,778 people.

    Official announcement: TODA (Open external link)

    Leak confirmedUnauthorized access

    Up to 7,200 email addresses; up to 6,000 transaction recordsSeparately, data for 4,778 employees. Categories are not added together.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  127. Saitama Prefecture

    The prefecture disclosed unauthorized viewing of a list and detailed information for some listed people.

    Official announcement: Saitama Prefecture (Open external link)

    Leak confirmedUnauthorized access

    A list of about 2,200 people; details for 3 of them

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  128. MrMax

    The company disclosed leakage of member information. It said addresses, birth dates, card data, passwords and purchase histories did not leak.

    Official announcement: MrMax (Open external link)

    Leak confirmedUnauthorized access

    Up to 1,735,154 people

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  129. Daiki Suisan

    The company disclosed possible leakage of official-app registration data, including former members.

    Official announcement: Daiki Suisan (Open external link)

    Possible leakUnauthorized access

    174,933 people

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  130. Asahi Kasei Therapeutics

    Asahi Kasei disclosed possible unauthorized viewing or acquisition of the Pharma DIGITAL member database, also affecting employee information. A temporary site provides product-information links while login and other member services remain unavailable.

    Official announcement: Asahi Kasei Therapeutics (Open external link)

    Possible leakUnauthorized accessServices restricted from October 2; a temporary site was available on October 17, while login and other member functions remained unavailable.

    About 514,000 healthcare professionals, plus other categoriesAbout 44,000 with email addresses and other data are a subset. Separately, about 700 employees.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-17

  131. Saitama Citizens Medical CenterElectronic media containing surgical images

    On October 6 the center disclosed loss of electronic media containing surgical/specimen images and patient IDs. It had no password protection and had not been found as of October 1; external exposure was unconfirmed but could not be ruled out.

    Official announcement: Saitama Citizens Medical Center (Open external link)

    Possible leakLoss of media

    About 200 images

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  132. Additional disclosure of possibly exposed data

    Evergreen MarketingEmployee email account

    Evergreen Marketing announced on July 31 that an employee’s email account was accessed on June 26 and used to send phishing emails. An October 6 update, based on forensic investigation, disclosed that information on 237 partner contacts and 763 corporate customers, including account details, may have been viewed.

    Official announcement: Evergreen Marketing (Open external link)

    Possible leakUnauthorized access

    237 agency and partner contacts and 763 corporate customersPartner contacts: organization names and email addresses. Corporate electricity customers: organization names, addresses, account details containing personal names and billing amounts.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Additional disclosure of possibly exposed dataOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  133. Rakuten Symphony / Rakuten Drive

    Compromised administrator credentials enabled acquisition or viewing of account names, display names and profile-image URLs.

    Official announcement: Rakuten Symphony / Rakuten Drive (Open external link)

    Leak confirmedUnauthorized access

    687 accountsThe three events are not added because overlap is unknown. The date is the information cutoff stated in the notice.

    Timeline and sources
    Timeline and sources
    1. Information as of October 6Official announcement (Open external link)

    Sources checked: 2026-10-14

  134. Rakuten Symphony / Rakuten Drive

    The company disclosed acquisition or viewing of account data, passwords transformed to resist recovery, and added strings.

    Official announcement: Rakuten Symphony / Rakuten Drive (Open external link)

    Leak confirmedUnauthorized access

    313 accountsThe three events are not added because overlap is unknown. The date is the information cutoff stated in the notice.

    Timeline and sources
    Timeline and sources
    1. Information as of October 6Official announcement (Open external link)

    Sources checked: 2026-10-14

  135. Rakuten Symphony / Rakuten Drive

    The company disclosed acquisition or viewing of stored photos, documents and other data between January 29 and September 17.

    Official announcement: Rakuten Symphony / Rakuten Drive (Open external link)

    Leak confirmedUnauthorized access

    15,382 accountsThe three events are not added because overlap is unknown. The date is the information cutoff stated in the notice.

    Timeline and sources
    Timeline and sources
    1. Information as of October 6Official announcement (Open external link)

    Sources checked: 2026-10-14

  136. Active

    The company found traces of customer and order data being exported from its online store and disclosed possible leakage. It said core business operations continued normally.

    Official announcement: Active (Open external link)

    Possible leakUnauthorized access

    Up to 54,916 records

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  137. White Essence

    The company disclosed data leakage after attackers reached core systems through a reservation-site vulnerability. Leakage of customer images was not confirmed.

    Official announcement: White Essence (Open external link)

    Leak confirmedUnauthorized access

    About 1.05 million accounts

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  138. Fourth report / affected scope

    Seicomart

    The fourth report identified 574,647 past or present app registrants whose data was subject to unauthorized viewing. It began notifying members and announced the end of app/web account-information viewing and editing functions.

    Official announcement: Seicomart (Open external link)

    Leak confirmedUnauthorized accessSome login and account-management functions restricted or ended

    574,647 peopleExcludes people who had left the club by September 24; replaces the previous estimate of about 570,000 accounts.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Fourth report / affected scopeOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  139. Second report

    SOFTSU

    The company disclosed possible leakage of call timestamps, transcripts and related information. Actual leakage was not confirmed.

    Official announcement: SOFTSU (Open external link)

    Possible leakUnauthorized access

    159,850 telephone numbersCount of telephone numbers, not unique people.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  140. i-plug / OfferBox

    A configuration flaw included names and email addresses in network responses accessible to customer companies through developer tools.

    Official announcement: i-plug / OfferBox (Open external link)

    Possible leakMisconfiguration

    Theoretical maximum: 314,009 studentsNot the number actually viewed.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  141. Nikkei

    Unauthorized logins to a Google Workspace account may have exposed employee and business-contact data.

    Official announcement: Nikkei (Open external link)

    Possible leakUnauthorized access

    1,646 peopleReaders and news sources are excluded. Separate from the Microsoft 365 incident.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  142. Nikkei

    The company disclosed an attack on a Microsoft 365 account and apparent leakage of contact information and some email contents.

    Official announcement: Nikkei (Open external link)

    Possible leakUnauthorized access

    Leak count under investigationAbout 9,000 counts impersonation emails sent, not leaked records.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  143. Second report / information leakage confirmed

    SK LogiInternal systems and order processing

    A September 20 ransomware attack affected ordering, shipping and inventory management. The October 3 second report confirmed leakage of some internal information and stated that EDR deployment and virus scanning had been completed by September 30.

    Official announcement: SK Logi (Open external link)

    Leak confirmedRansomwareNetwork-based order processing suspended. The October 3 second report describes an expected restart, not completed recovery.

    Count undisclosedLeakage of internal information is confirmed; whether it includes personal information and its scale are undisclosed.

    Timeline and sources (2)
    Timeline and sources
    1. System disruption announcedOfficial announcement (Open external link)
    2. Second report / information leakage confirmedOfficial announcement (Open external link)

    Sources checked: 2026-10-26

  144. Recruit

    The company disclosed that a third party may have identified 3,687 email addresses as registered with Study Sapuri.

    Official announcement: Recruit (Open external link)

    Possible leakUnauthorized access

    3,687 email addresses

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  145. Japan Organization for Metals and Energy Security

    Unauthorized access may have exposed email addresses of staff and external contacts.

    Official announcement: Japan Organization for Metals and Energy Security (Open external link)

    Possible leakUnauthorized access

    About 1,100 staff and 7,400 external email addressesCounts of email addresses, not unique people.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  146. FAQ update and partial reopening

    Aflac Life Insurance Japan

    The investigation disclosed leakage of policyholder and agency data. Policyholders whose account information was involved form a subset. The FAQ updated on October 1 reports that Yorisou Net reopened on September 28 after safety checks, except for some services.

    Official announcement: Aflac Life Insurance Japan (Open external link)

    Leak confirmedUnauthorized accessYorisou Net reopened on September 28 except for some services; remaining reopening dates are not announced.

    About 4.4 million policyholders and 40,000 agenciesAbout 220,000 people with account information are a subset. Policyholders and agencies are not added together.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. FAQ update and partial reopeningOfficial announcement (Open external link)

    Sources checked: 2026-10-21

  147. Nippon Rent-A-Car Service (September 19–21 event)Nippon Rent-A-Car app

    The app system was attacked from September 19 to 21 using a different method from the first event, confirmed on September 29. On October 1 the company disclosed unauthorized access to 55 members’ pages, with possible viewing of driver-licence and other data.

    Official announcement: Nippon Rent-A-Car Service (September 19–21 event) (Open external link)

    Possible leakUnauthorized access

    55 membersNames, phones, emails, login IDs, usage history and reservations; for members who registered them, driver-licence details (number, address, birth date) and card last four digits and holder names may also have been viewed. This is a separate intrusion from the previously listed first event.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

September 2026

  1. VOISING

    The final report confirmed leakage of personal information following unauthorized access.

    Official announcement: VOISING (Open external link)

    Leak confirmedUnauthorized access

    About 170,000 records

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  2. Second report / investigation results

    Hachioji Gakuen Hachioji Junior and Senior High School

    The September 30 report said the external investigation concluded in late August. Server and other files were encrypted with no prospect of restoration. No traces of exfiltration were found, but missing logs mean leakage cannot be completely ruled out.

    Official announcement: Hachioji Gakuen Hachioji Junior and Senior High School (Open external link)

    No evidence of leakage; cannot be ruled outRansomwareNo prospect of restoring encrypted files; full system recovery remains in progress

    Number under investigation

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Second report / investigation resultsOfficial announcement (Open external link)

    Sources checked: 2026-10-16

  3. Osaka City and its after-school program contractorDevices in three after-school activity rooms

    Osaka City announced on September 30 that support scams installed remote-control software at three activity rooms, exposing data for possible viewing on 1,261 children, 953 guardians and 58 staff. Evidence showed approximately 15–50 minutes of remote activity, but no external transmission was found within the examinable scope.

    Official announcement: Osaka City and its after-school program contractor (Open external link)

    Possible leakUnauthorized access

    Up to 2,272 people

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-21

  4. Nabari Kintetsu Gas

    The company disclosed possible leakage of customer data after unauthorized access at a vendor. Bank-account and card data were excluded.

    Official announcement: Nabari Kintetsu Gas (Open external link)

    Possible leakIncident at a vendor

    About 6,800 records

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  5. G-PLAN

    The company disclosed possible leakage of member identifiers and related data. Identifier counts are not counts of unique people.

    Official announcement: G-PLAN (Open external link)

    Possible leakUnauthorized access

    Up to about 70,000 member identifiers

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  6. Benefit One

    The company disclosed that another customer downloaded mixed personal data and confirmed its deletion.

    Official announcement: Benefit One (Open external link)

    Leak confirmedMisconfiguration

    13,460 people across 2,322 organizations

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  7. Okayama PrefectureSeminar registration form

    A contractor distributed an editing URL for a seminar form, making 26 applicants’ names, gender, age, municipality, occupation, phone numbers and emails accessible. Permissions were corrected on September 26 and the incident was disclosed on September 29.

    Official announcement: Okayama Prefecture (Open external link)

    Leak confirmedMisconfigurationForm-access permissions were corrected on September 26; the seminar was cancelled.

    26 applicants26 applicants’ records were accessible; third-party viewing or downloading has not been established.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-28

  8. TOPPAN / Sompo Japan Insurance

    Insurance-related personal data were mistakenly sent to another insurer. Complete deletion at the recipient was confirmed.

    Official announcement: TOPPAN / Sompo Japan Insurance (Open external link)

    Leak confirmedMisdelivery

    177,426 people, potentially including duplicatesThe figure may include the same person more than once.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  9. eplus

    Unauthorized access exposed refund-processing information. Card numbers were outside the affected scope.

    Official announcement: eplus (Open external link)

    Leak confirmedUnauthorized access

    1,463 records

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  10. Saitama Citizens Medical CenterFiles attached to staff-only pages

    The September 28 notice disclosed that unauthorized third parties could directly access attachments to staff-only pages. A manual uploaded in July 2018 contained two patient photographs and names/phone numbers of two staff members; resulting harm has not been confirmed.

    Official announcement: Saitama Citizens Medical Center (Open external link)

    Possible leakMisconfiguration

    Two patient photographs and data for two staff members

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-07

  11. Resona BankAccount-closure index records (microfiche)

    Resona Bank announced on September 28 the loss of microfiche recording account-closure data on about 9,000 customers of predecessor banks. It says the records were most likely discarded by mistake, with no sign of unauthorized removal.

    Official announcement: Resona Bank (Open external link)

    Leak described as highly unlikelyLoss of media

    Approx. 9,000 customersNames, account numbers, closure amounts, reasons and last transaction dates for accounts closed from July 1992 to March 2001 at predecessor banks; the records were most likely discarded by mistake.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  12. Ainokaze Toyama Railway

    Unauthorized access to a reservation system may have exposed customer information.

    Official announcement: Ainokaze Toyama Railway (Open external link)

    Possible leakUnauthorized access

    1,409 people

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  13. Shueisha

    Shueisha disclosed leakage of Hapicomu registration and related data. Figures for different categories are not added together.

    Official announcement: Shueisha (Open external link)

    Leak confirmedUnauthorized access

    2,835 blogger records; other categories listed separatelySeparately: 630 project records, 11,237 emails and 10,780 business-contact records.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  14. Second report

    Mitsui Fudosan

    The company disclosed possible leakage of employee-related and external-contact data. Viewing or acquisition of every record was not confirmed.

    Official announcement: Mitsui Fudosan (Open external link)

    Possible leakUnauthorized access

    Up to 19,000 employee-related and 36,000 external-contact records

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  15. Nippon Rent-A-Car Service

    Unauthorized access to the NR app may have exposed member information. For members who registered it, driver-license data and other information were also affected.

    Official announcement: Nippon Rent-A-Car Service (Open external link)

    Possible leakUnauthorized access

    41 peopleCard data is limited to the last four digits and cardholder names. The notice does not state leakage of license images.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  16. Second report / investigation status

    King PrintersOnline printing site and related functions

    King Printers detected unauthorized access to its systems on September 10, suspended the site and reopened it on September 14. Its September 25 report said the apparent aim was misuse of its credentials for a generative-AI service; no leakage of customer information had been confirmed. An external forensic investigation was planned.

    Official announcement: King Printers (Open external link)

    No leakage confirmed; investigation ongoingUnauthorized accessSite suspended from September 10 evening and reopened at 16:00 on September 14

    Number not disclosedAs of September 25, no traces of external transfer or unauthorized access to personal information had been found.

    Timeline and sources (2)
    Timeline and sources
    1. Initial notice and site reopeningOfficial announcement (Open external link)
    2. Second report / investigation statusOfficial announcement (Open external link)

    Sources checked: 2026-10-16

  17. Related update

    Nichirei

    The seventh report confirmed leakage of personal information. Normal warehouse and frozen-food shipping operations resumed at all sites on July 24.

    Official announcement: Nichirei (Open external link)

    Leak confirmedRansomwareNormal operations resumed

    3,308 delivery; 6,849 partner; 43,709 employee-related recordsSeparately, 43,709 employee-related records. Categories are not added together.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Q'sai (Open external link) · Leak confirmed484 people

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-10

  18. LEGOLAND Japan

    The hotel disclosed the scope of reservations potentially affected by unauthorized access to a booking service.

    Official announcement: LEGOLAND Japan (Open external link)

    Possible leakIncident at a vendor

    1,557 reservations

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  19. Second report

    EPARK Relax & Esthe

    External transfer of the PeakManager database was confirmed. Review revised the scope from about 33 million to about 22.18 million records.

    Official announcement: EPARK Relax & Esthe (Open external link)

    Leak confirmedUnauthorized access

    About 22.18 million records after reviewCannot be converted to unique people. Includes health information and five entries resembling card data.

    Timeline and sources (2)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  20. Co-op Yamaguchi

    The cooperative disclosed possible leakage of member-related database records. Actual leakage was not confirmed.

    Official announcement: Co-op Yamaguchi (Open external link)

    Possible leakUnauthorized access

    69,586 / 143,126 / 365 / 4,218 records by categoryCategories are not added together. The 143,126-record category includes Coco Card numbers and PINs.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  21. Kufu Zaim

    The company disclosed unauthorized changes to information including nicknames and email addresses for 14 users. It reported no leakage or viewing of information, restored the affected data and resolved saving errors for new users on September 21.

    Official announcement: Kufu Zaim (Open external link)

    No leak reportedUnauthorized accessSaving errors resolved on September 21

    Data alteration affecting 14 usersThe company reported no leakage. The 14 users concern alteration, not exposed information, and are excluded from exposure totals.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-13

  22. GMO InternetConoHa WING

    Unauthorized access and malicious programs were found in some customers’ web-server storage. GMO detected the incident on September 16, identified its cause and scope, and removed the programs on September 18. It reported no leakage of membership, contract or payment information held in a separate environment.

    Official announcement: GMO Internet (Open external link)

    Leak not confirmedUnauthorized access

    426 affected accountsAccounts affected by unauthorized access to web-server storage; not a disclosed exposure count.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-15

  23. RIZAP / APORITO

    Malicious scripts on the online store may have exposed card and other information. Investigation continued in the third report.

    Official announcement: RIZAP / APORITO (Open external link)

    Possible leakUnauthorized accessOnline store temporarily closed

    Number not disclosedSeparate from the August ransomware incident at REXT.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  24. Final report

    Kyoiku Sangyo

    A compromised employee Microsoft 365 account was used to send suspicious emails. The final investigation found no traces of file exfiltration but could not rule out third-party viewing of business contacts’ email information.

    Official announcement: Kyoiku Sangyo (Open external link)

    Possible leakUnauthorized access

    Number not disclosedOne employee refers to the compromised account holder, not the number of exposed people.

    Timeline and sources (2)
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)
    2. Final reportOfficial announcement (Open external link)

    Sources checked: 2026-10-13

  25. JGC Digital

    A third party acquired account data for Azas and Sloop. The figures include multiple accounts held by the same person.

    Official announcement: JGC Digital (Open external link)

    Leak confirmedUnauthorized access

    About 40,000 Azas and 20,000 Sloop accounts

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  26. Third-party review found no exfiltration

    REQREA

    Tabiq identity-document images and related data were accessible. Unauthorized acquisition and secondary harm were not confirmed.

    Official announcement: REQREA (Open external link)

    Possible leakMisconfiguration

    1,060,338 peopleThe figure is not limited to residents of Japan.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Third-party review found no exfiltrationOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  27. Aichi Prefecture (Mental Health and Welfare Center)Applications for mental-disability certificates and medical-support certificates

    Aichi Prefecture announced on September 17 that its Mental Health and Welfare Center lost 233 application documents (172 applicants) from fiscal 2023–2025, likely through mistaken disposal. No leak has been confirmed.

    Official announcement: Aichi Prefecture (Mental Health and Welfare Center) (Open external link)

    Lost; no leak confirmedLoss of media

    233 application documents (172 applicants)79 certificate and 154 medical-support applications, covering 172 applicants after removing overlap; they include names, addresses, Individual Numbers, diagnosis details such as illness and medical history, and family information.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  28. Chibagin Shoten

    The company disclosed possible leakage of customer data. Evidence of external transmission had not been confirmed.

    Official announcement: Chibagin Shoten (Open external link)

    Possible leakUnauthorized access

    About 192 individual and 722 corporate contacts; about 7,670 email-only contactsSeparately, about 7,670 email-only contacts. About 31 with account information are a subset.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  29. istyle

    Information placed on a file-transfer service was accessible. Actual acquisition by an outside party was not confirmed.

    Official announcement: istyle (Open external link)

    Possible leakMisconfiguration

    10,997 people

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  30. Murauchi.com

    The second report disclosed leakage of personal information through unauthorized access. Card data and passwords were excluded.

    Official announcement: Murauchi.com (Open external link)

    Leak confirmedUnauthorized access

    7,716,811 records

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  31. Komatsu (cross-system review)Portal site and other internal systems

    A cross-system review following the June 16 disclosure found that personal data in several systems was, or may have been, viewable beyond the necessary scope, Komatsu announced on September 15. The portal covers 214,916 people, among others; access has been restricted.

    Official announcement: Komatsu (cross-system review) (Open external link)

    Possible leakMisconfiguration

    214,916 people on the portal and three other systems (overlapping)Portal 214,916; design-change approvals 29,621; sales system 86,015; quality reporting 46,445. The same people appear in several systems, according to the notice. Only authorized system users could view the data; no passwords are included. Separate from the June 16 disclosure.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  32. LEAN BODY

    The company disclosed leakage of account data. Card data were limited to items such as the last four digits; full numbers and security codes were not held.

    Official announcement: LEAN BODY (Open external link)

    Leak confirmedUnauthorized access

    About 440,000 accountsThe company expects the number of unique people to be lower than the account count.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  33. Digital Agency

    Possible leakage concerns officials and contractors. The disclosure does not report leakage of the general public's data or My Number identifiers.

    Official announcement: Digital Agency (Open external link)

    Possible leakUnauthorized access

    About 246,000 records

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  34. SAKURA internet

    Unauthorized access affected sales-management and other systems. Viewing or acquisition was possible, but clear evidence of external removal was not confirmed.

    Official announcement: SAKURA internet (Open external link)

    Possible leakUnauthorized access

    1,360,563 accountsIncludes 951 rental-server accounts. A link between the two system compromises was not established.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  35. FUSO DENTSU

    The company disclosed possible leakage of information about customers and contacts of business partners. Bank-account and card data were excluded.

    Official announcement: FUSO DENTSU (Open external link)

    Possible leakUnauthorized access

    26,489 records

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  36. MOL Cruises

    Some external storage media used to transfer data from Nippon Maru to a new ship were found missing during a July onboard check. They may contain passport, medical and allergy information, and crew banking or payroll data. Their contents remain under investigation; no leakage or misuse has been confirmed.

    Official announcement: MOL Cruises (Open external link)

    Possible leakLoss of media

    Affected scope under investigationApproximately 200,000 head-office backup files are being investigated; this is not a count of lost or exposed files.

    Timeline and sources
    Timeline and sources
    1. AnnouncementOfficial announcement (Open external link)

    Sources checked: 2026-10-15

  37. Second report: personal data possibly leaked

    FIVE FOXes

    After detecting possible ransomware infection, the company stopped servers, internet and email functions while shops and the online store remained open. Its September 8 second report disclosed possible leakage of 59,504 customer, 8,403 inquiry-customer and 5,278 employee records.

    Official announcement: FIVE FOXes (Open external link)

    Possible leakCyberattackServers and email stopped; shops and online store remained open

    Customers 59,504, inquiry customers 8,403, employees 5,278 in total (possible)Employees: 2,450 at Five Foxes and 2,828 at COMME CA; card and My Number data are not included.

    Timeline and sources (2)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    2. Second report: personal data possibly leakedOfficial announcement (Open external link)

    Sources checked: 2026-11-02

  38. Correction to third report

    Charm

    A correction to the third report refined the affected figures. The scope for former customers remained under review.

    Official announcement: Charm (Open external link)

    Leak confirmedUnauthorized access

    About 370,000 confirmed; about 20,000 possibly affected recordsCorrected on September 2. The 239 unauthorized logins are a separate measure.

    Timeline and sources (3)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)
    3. Correction to third reportOfficial announcement (Open external link)

    Sources checked: 2026-10-10

August 2026

  1. Yellow Hat

    The company disclosed possible leakage of personal information and said it did not hold card, password or vehicle information.

    Official announcement: Yellow Hat (Open external link)

    Possible leakUnauthorized access

    Up to 1,801,499 people

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  2. Second report

    Hands Holdings

    Ransomware caused some internal systems to stop. The second report disclosed possible employee-data leakage and possible viewing of My Number data.

    Official announcement: Hands Holdings (Open external link)

    Possible leakRansomwareSome systems stopped in June; recovery status not stated in the second report

    Number not disclosed

    Timeline and sources (2)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Second reportOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  3. Related update

    KDDI

    The PPC disclosure on August 19 identified the leak scope. People whose plaintext passwords were involved form a subset.

    Official announcement: KDDI (Open external link)

    Leak confirmedUnauthorized access

    12,231,954 peopleThe 7,616,173 people with plaintext passwords are a subset. Related company figures are not added.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. KDDI Web Communications (CPI) (Open external link) · Leak confirmed1,250,543 email-account records

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-10

  4. Faith Group

    Ransomware encrypted and erased internal systems. Product shipping was suspended, with dispatch arrangements resuming on June 24.

    Official announcement: Faith Group (Open external link)

    Possible leakRansomwareDispatch arrangements resumed

    Number not disclosedAs of August 21, full system recovery was expected around the end of October.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  5. COTA

    Following unauthorized access, the company rebuilt its environment and announced full internal-system recovery on August 20. It could not rule out leakage.

    Official announcement: COTA (Open external link)

    Possible leakUnauthorized accessAll internal systems restored

    See the announcement for category figures

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  6. Related update

    CyberAgent / dotmoney

    Unauthorized access suspended dotmoney and dotgift. Partner PointTown announced resumption of exchanges to dotmoney on August 20.

    Official announcement: CyberAgent / dotmoney (Open external link)

    Leak not confirmedUnauthorized accessExchanges resumed at a partner

    Number of affected users not disclosedThis does not establish full recovery of all functions or dotgift.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. GMO Media / PointTown (Open external link) · Leak not confirmedExchanges to dotmoney resumed

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-14

  7. KAGA SOLNET

    Leakage of Academico Navi information was confirmed. The scope was refined from an initial maximum of about 170,000 records.

    Official announcement: KAGA SOLNET (Open external link)

    Leak confirmedUnauthorized access

    165,587 people

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  8. OCS

    OCS disclosed leakage of customer and other data for its Family Link Service. New applications and service provision remained suspended in the fourth report.

    Official announcement: OCS (Open external link)

    Leak confirmedUnauthorized accessAffected service still suspended

    Number not disclosedThis does not mean all international transport operations stopped.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  9. Tokushima Prefecture

    Storage media from resident-register network equipment were unaccounted for and may have been disposed of without erasure.

    Official announcement: Tokushima Prefecture (Open external link)

    Possible leakLoss of media

    About 460,000 cumulative recordsAbout 180,000 cumulative records containing My Number identifiers are a subset.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  10. Toshiba Tec

    A specific ShopCraft customer could access another customer's data. Actual viewing was not confirmed.

    Official announcement: Toshiba Tec (Open external link)

    Possible leakMisconfiguration

    382,123 people

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

July 2026

  1. LY Corporation

    Internal LINE GAME identifiers and related data were sent to an external advertising tool. Names, addresses and card information were not included.

    Official announcement: LY Corporation (Open external link)

    Leak confirmedMisconfiguration

    About 5.74 million unique users in JapanDistinct from about 6.66 million Japanese identifiers and about 6.1 million users worldwide.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  2. Solid Advance

    A malware incident led to suspension of the affected system. Other operating services continued after safety checks.

    Official announcement: Solid Advance (Open external link)

    Leak not confirmedMalware infectionAffected system suspended

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  3. ASKUL

    An investigation into an earlier attack added potentially affected records. This was not a new attack.

    Official announcement: ASKUL (Open external link)

    Possible leakRansomware

    About 600,000 additional recordsExternal leakage or misuse of the newly added information was not confirmed.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  4. SEIDENSHA ELECTRONICS

    Server encryption and external transfer of some data were confirmed. Quoting, orders, production and shipping resumed on a temporary core system.

    Official announcement: SEIDENSHA ELECTRONICS (Open external link)

    Leak confirmedRansomwareOperations resumed on temporary systems

    Affected systems; personal-data count not disclosedThe company reported no traces of transfer of information received from customers or partners.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  5. Kankyo Kaihatsu Kogyo

    The company disclosed a system disruption caused by unauthorized access. Waste-oil and industrial-waste collection continued normally, while data leakage remained under investigation.

    Official announcement: Kankyo Kaihatsu Kogyo (Open external link)

    Under investigationUnauthorized accessSome systems disrupted; collection operations continued

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  6. Asahi Group Holdings

    The group revised the potentially affected server-data scope for an earlier attack. External leakage of that scope was not confirmed.

    Official announcement: Asahi Group Holdings (Open external link)

    Possible leakRansomware

    1.525 million customer-inquiry records; 378,000 partner records, and other categoriesSeparately: 117,000 ceremonial contacts, 107,000 employee records and 162,000 family records. The confirmed scope announced on February 18 was not revised.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  7. Related update

    Nostrum

    Ransomware prevented servers from starting and suspended learning-support services. The company reported rebuilding in a new environment.

    Official announcement: Nostrum (Open external link)

    Under investigationRansomwareLearning-support services suspended

    Number not disclosed

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Fukuoka University (Open external link) · Possible leakUp to 33,668 people, including up to 800 with names

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-14

June 2026

  1. Marutake

    A ransomware incident involved data removal and public exposure. Pharmaceutical supply operated using temporary servers.

    Official announcement: Marutake (Open external link)

    Leak confirmedRansomwareOperating on temporary servers

    Number of affected people not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  2. Final report

    ICOMSOFT

    Unauthorized access led to isolation and rebuilding of web and email servers. The final report assessed leakage as unlikely but could not rule it out.

    Official announcement: ICOMSOFT (Open external link)

    Possible leakUnauthorized accessWeb and email environments rebuilt; full recovery not expressly stated

    Number not disclosed

    Timeline and sources (2)
    Timeline and sources
    1. Initial noticeOfficial announcement (Open external link)
    2. Final reportOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  3. 2 Rinkan Yellow Hat

    The final report confirmed personal-data leakage, refining the scope from an initial maximum of 3,455,754 people.

    Official announcement: 2 Rinkan Yellow Hat (Open external link)

    Leak confirmedUnauthorized access

    3,179,454 people

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  4. Osaka Organic Chemical Industry

    Unauthorized access disrupted website availability; the company reported recovery. Core operations, including order processing, were unaffected.

    Official announcement: Osaka Organic Chemical Industry (Open external link)

    Under investigationUnauthorized accessWebsite restored; core operations unaffected

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  5. Komatsu

    Registered users could access information about other registered users.

    Official announcement: Komatsu (Open external link)

    Possible leakMisconfiguration

    139,302 peopleThe disclosure does not describe unrestricted public access.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  6. Nippon Tele-net

    The ransomware investigation disclosed potentially affected information categories. No traces of external transfer were detected.

    Official announcement: Nippon Tele-net (Open external link)

    Possible leakRansomware

    602,000 / 404,000 / 33,000 / 2,044 records by categorySeparately, 33,000 sales-contact records and 2,044 employee/family records. No aggregate total.

    Timeline and sources · Related announcements (1)
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)
    Related announcements (customers and principals)
    1. Mobility Platform (Open external link) · Possible leakNumber not disclosed

    Figures are those announced by each organization. They arise from the same incident and are not added together.

    Sources checked: 2026-10-10

  7. Kyushu Electric Power Transmission and Distribution

    The company disclosed lost storage media and possible exposure of customer data. Actual leakage was not confirmed.

    Official announcement: Kyushu Electric Power Transmission and Distribution (Open external link)

    Possible leakLoss of media

    Up to 10.9 million supply-contract recordsCount of supply contracts, not unique people.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  8. Matsuzawa Shoten

    Ransomware affected ordering and shipping for Gakufu Navi and Chumon-kun. Alternative methods remained in use after major functions resumed.

    Official announcement: Matsuzawa Shoten (Open external link)

    Under investigationRansomwareMajor functions resumed

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  9. Asahi-Seiki Manufacturing

    Unauthorized access disrupted website display. The second report said the site was viewable again, with some functions still restricted.

    Official announcement: Asahi-Seiki Manufacturing (Open external link)

    Leak not confirmedUnauthorized accessWebsite viewing restored; some functions restricted

    Number not disclosedThe company reported no impact on internal core operations.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

May 2026

  1. KDDI Web Communications (CPI)

    DDoS attacks disrupted Web and FTP access. Recovery was announced for 10:30 on May 28.

    Official announcement: KDDI Web Communications (CPI) (Open external link)

    Leak not confirmedDDoS attackRestored May 28 at 10:30

    Some shared-hosting plansSeparate from the email-information breach.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  2. Universal Music Japan

    An investigation into unauthorized access to online stores in the previous year disclosed leakage of customer information.

    Official announcement: Universal Music Japan (Open external link)

    Leak confirmedUnauthorized access

    3,105,585 recordsA figure disclosed by a Japanese business, not necessarily a count of Japanese residents.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  3. Aisan Technology

    Unauthorized access and website tampering prompted temporary closure. The company rebuilt the environment and republished the site on May 14.

    Official announcement: Aisan Technology (Open external link)

    Leak not confirmedWebsite defacementWebsite republished on May 14

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  4. Medica Shuppan

    The investigation revised the scope of possibly exposed personal data. Conclusive evidence of external removal was not detected.

    Official announcement: Medica Shuppan (Open external link)

    Possible leakRansomware

    About 641,000 people, potentially including duplicatesMay include the same person more than once.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

  5. Enessance Holdings

    The company confirmed public exposure of some data from an earlier-year attack and disclosed the affected scope.

    Official announcement: Enessance Holdings (Open external link)

    Leak confirmedRansomware

    About 365,000 potentially affected recordsThe figure does not mean leakage of every record was confirmed.

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-10

April 2026

  1. B&G Foundation

    A malware attack disrupted servers. The foundation isolated affected servers and disconnected the network while working on recovery.

    Official announcement: B&G Foundation (Open external link)

    Leak not confirmedMalware infectionAffected servers isolated and network disconnected

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

  2. Setsunan University

    The university confirmed partial tampering with its economics-faculty website and closed the affected site. Data leakage was not confirmed.

    Official announcement: Setsunan University (Open external link)

    Leak not confirmedWebsite defacementAffected economics-faculty website closed

    Number not disclosed

    Timeline and sources
    Timeline and sources
    1. Announcement / updateOfficial announcement (Open external link)

    Sources checked: 2026-10-14

Methods and coverage

How incidents are counted

  • The overview counts each listed incident once. Its figures cover the full list and do not change with the chart filters.
  • The leak statuses also include 19 incidents with leakage unconfirmed and 1 reporting no leak. Confirmed incidents include partial confirmations; possible or investigating incidents include cases still being investigated.
  • Outage counts include restored services. An incident can have both a leak and an outage, so these categories must not be added together.

How information counts are aggregated

  • Reviewed figures from 176 incidents are included; 102 incidents are excluded. Confirmed and possible exposure are shown separately. Both sums include approximate figures, so neither is an exact nationwide total.
  • Disclosed counts of people, accounts, records, contracts and other information units are each counted as one reported item per source unit. These are sums of reported scopes, not unique people or a standardized database-record count. Names and addresses within one person's record are not counted as separate items. Some domestic organizations' disclosures include overseas users.
  • Certainty is reviewed for each numerical scope. If some leakage is confirmed but its count cannot be separated, the full reported scope is counted only under possible exposure. When separate confirmed and possible figures are disclosed, each is included in its own category. Maxima are not treated as confirmed solely because some leakage occurred.
  • The first row excludes image metadata; the row below includes it when separately disclosed from user information. The rows are alternative scopes and must not be added together. Metadata is information attached to images, such as image IDs and source URLs, not the image files themselves or the number of affected people.
  • Subsets, superseded figures and related customer disclosures already covered by a parent scope are not added again. Unknown counts or unresolved scopes are excluded, not treated as zero. The lists below preserve source units, calculation decisions and exclusions.

How the monthly chart is counted

  • Each incident is counted once, in the month of its latest listed announcement, including related customer disclosures. Follow-ups and related disclosures are not counted as separate incidents. The chart does not show when incidents occurred or how many people were affected.
  • Initial coverage includes announcements and follow-ups from April 10, 2026. Coverage criteria differ by month, and the latest month runs only through the data cutoff date. The chart therefore does not represent national incident totals or trends.

Incidents listed

  • Only incidents announced by the company, organization or public body itself in Japan. Incidents known only from press reports or from an attacker's claims are not listed.
  • Listed are incidents with announced figures of 1,000 or more, cyberattack-related service or business outages, identity documents, card data, My Number or health information, and vendor incidents affecting many customers. Unauthorized-access incidents with follow-up reports while the affected count is under investigation are also included.
  • For incidents up to August 2026, only those with an announced figure of 100,000 or more, or with an outage that affected the business, are included.
  • This is not a complete list of every incident announced in Japan.

Reading each entry

  • Figures retain the units of each announcement, with subsets marked as part of the overall figure.
  • “Confirmed”, “possible” and “under investigation” follow the wording of the announcement. When a later report changes the picture, the entry is updated and the earlier reports stay in the timeline.
  • An incident at a vendor or cloud platform is listed once, with the announcements of its customers shown as related announcements.
  • Each row shows the latest date among the listed sources, including related announcements. The timeline contains the announcements reviewed and the source-check date for that entry.

Corrections

If an entry is wrong, or a new announcement has changed the facts, please let us know through the contact form. We will check and correct it.

Figures included in the sums (176 incidents)

Each entry shows the number used in the sum alongside the original wording, including qualifiers such as “about” and “up to”. Even when some leakage is confirmed, the entire reported scope may not be confirmed leaked. Follow an incident link for its status and timeline.

Information confirmed exposed — 938,231,140 reported items

  1. Up to approx. 5.5 million records (including duplicates) — Road-service users’ names, addresses, contact, vehicle and service-request information and some bank-account data. Three card numbers were additionally confirmed on November 6 and are a subset of the maximum of about 5.5 million records. Deduplicated person counts and partner-company scope remain under review.

    Counts once the up to approximately 5.5 million records confirmed as taken out (a maximum including duplicates); the de-duplicated count is pending and partner-company data are not added.

    Official source
  2. Arara81,329,467 email addresses

    81,329,467 email addresses (deduplicated) — The November 6 third report gives a confirmed leak count deduplicated across all environments: 34,285,087 email-only records and 47,044,380 with attributes such as names. About 380 customer companies, 61 shared-environment customers and their individual disclosures are not added. A same-day correction changes a breakdown figure, not the total.

    The third report confirms 81,329,467 addresses, deduplicated across all environments. This replaces the earlier approximately 77 million and shared/customer-environment figures; none are added again. The correction leaves the total unchanged.

    Official source
  3. ROHTO Pharmaceutical2,797,545 people

    Customer-management data for 2,797,545 people; call recordings containing card data for 9,715 people — Customer-management records contain names, addresses and phone numbers, varying by person. Some call recordings include card numbers and expiry dates, but not security codes or authentication information. The 9,715 recording subjects are not added because overlap with customer-management subjects is unresolved.

    Counts confirmed customer-management data for 2,797,545 people. The 9,715 people with card data in recordings are not added because overlap is unresolved.

    Official source
  4. Mizkan29 people

    487 altered accounts; data exposure affecting 29 people — The 29 people are a subset of the 487 altered accounts. The 26 with point/campaign data are also a subset and are not added.

    Counts only the 29 people with confirmed data exposure; 487 altered accounts and the subset of 26 are not added.

    Official source
  5. About 2,000 institutional investors/analysts and about 250 former employees, plus unquantified data — Names, email addresses and related information. Listed-company executives’ names and positions are also included, without a published count. Unauthorized access to MIR@I has not been confirmed.

    Counts about 2,000 institutional investors/analysts; unquantified executive information is excluded.

    Official source
  6. About 2,000 institutional investors/analysts and about 250 former employees, plus unquantified data — Names, email addresses and related information. Listed-company executives’ names and positions are also included, without a published count. Unauthorized access to MIR@I has not been confirmed.

    Counts the separate group of about 250 former employees.

    Official source
  7. Aioi Nissay Dowa Insurance444,000 reported items

    About 444,000 records — Policyholder data and related information. Three records containing the last four card digits and 19 containing partial bank-account information are subsets and are not added.

    Counts the approximate total disclosed on November 6 once; subsets by data field are not added.

    Official source
  8. Mitsui Sumitomo Insurance37,000 reported items

    About 37,000 records — Policyholder data and related information. The company states that credit-card and bank-account information is not included.

    Counts the approximate total disclosed on November 6 once; subsets by data field are not added.

    Official source
  9. Previously reported 743 records; an additional 142, 9,252 and 19 records — Additional groups comprise 142 event-calendar contacts, 9,252 current/former staff records and 19 maintenance/production-company contacts, including names and email addresses. The separate e-Venue incident is excluded.

    Counts once the 743 personal-data records explicitly confirmed exposed in the October 19 official notice; website and event counts are excluded.

    Official source
  10. Previously reported 743 records; an additional 142, 9,252 and 19 records — Additional groups comprise 142 event-calendar contacts, 9,252 current/former staff records and 19 maintenance/production-company contacts, including names and email addresses. The separate e-Venue incident is excluded.

    Counts 142 newly confirmed event contacts records as an additional group separate from the previously reported 743.

    Official source
  11. Previously reported 743 records; an additional 142, 9,252 and 19 records — Additional groups comprise 142 event-calendar contacts, 9,252 current/former staff records and 19 maintenance/production-company contacts, including names and email addresses. The separate e-Venue incident is excluded.

    Counts 9252 newly confirmed current/former staff records as an additional group separate from the previously reported 743.

    Official source
  12. Previously reported 743 records; an additional 142, 9,252 and 19 records — Additional groups comprise 142 event-calendar contacts, 9,252 current/former staff records and 19 maintenance/production-company contacts, including names and email addresses. The separate e-Venue incident is excluded.

    Counts 19 newly confirmed contractor contacts records as an additional group separate from the previously reported 743.

    Official source
  13. 27,139 people — Regional-branch names, member names and numbers, gender, birth dates and email addresses. Addresses, phone numbers, passwords and bank-account data are not included. This reviewed person count replaces the initial mailing-list estimate of over 40,000 entries.

    Counts the reviewed 27,139 members, replacing the initial estimate of over 40,000 entries.

    Official source
  14. Fancrew1,030,741 reported items

    1,030,741 monitor member records — Member IDs, email addresses, hashed passwords, names, gender, postcodes and the last four digits of phone numbers. Former members are not included. No unauthorized logins or point exchanges using the leaked data have been confirmed. Partner Point Town announced that, for its linked users, Fancrew-issued IDs, gender and first-link dates leaked.

    Counts the 1,030,741 monitor member records the second report says were found to have leaked. The related Point Town disclosure (no count given) is not added.

    Official source
  15. Trustbank4,454,097 reported items

    4,454,097 records — The five people with additional exposed fields are a subset of the previously disclosed 4,454,097 records.

    Retains 4,454,097 records reiterated in the second report; five people with additional fields are a subset.

    Official source
  16. Ymirlink190 reported items

    FC: 51,628,280 records in gross; BASE: 190 customer records — Exposure traces were found in 49 FC systems. The detailed table labels the gross figure as possible exposure; counts for 16 systems remain under investigation. The 190 BASE records are a separate customer-management dataset. Customer disclosures and the superseded approximate nine million are not added.

    Counts the separately identified 190 accessible BASE customer records, supported by the service table and the October 16 viewing-log finding. These are distinct from FC mailing-list records.

    Official source
  17. Helpfeel23,620,000 reported items

    User information

    About 23.62 million user records, 666.4 million metadata records and 432 images — The 432 images belonged to 133 users. Metadata comprises about 490 million, 2.4 million and 174 million records. Counts include overseas usage and are not unique people. The 432 images and 133 users are not added to the reference sums because their correspondence with already counted data is unresolved. A November 5 correction said the 2.4 million records cover images uploaded mainly during about two days from January 1, 2016 and from January 1, 2020 (about 0.07% of all images), and that the about 174 million records relate to about 1.12 million accounts, of which about 57,000 have been closed.

    Disclosed user-information records, including anonymous and overseas usage, separate from image metadata. The third report retains this exposed-data count. The 432 images and 133 users are not added.

    Official source
  18. Helpfeel490,000,000 records

    Image metadata

    About 23.62 million user records, 666.4 million metadata records and 432 images — The 432 images belonged to 133 users. Metadata comprises about 490 million, 2.4 million and 174 million records. Counts include overseas usage and are not unique people. The 432 images and 133 users are not added to the reference sums because their correspondence with already counted data is unresolved. A November 5 correction said the 2.4 million records cover images uploaded mainly during about two days from January 1, 2016 and from January 1, 2020 (about 0.07% of all images), and that the about 174 million records relate to about 1.12 million accounts, of which about 57,000 have been closed.

    Approximately 490 million image-metadata records, such as image IDs and source URLs, not image files. The third report retains this exposed-data count. The 432 images and 133 users are not added.

    Official source
  19. Helpfeel2,400,000 records

    Separately extracted image metadata

    About 23.62 million user records, 666.4 million metadata records and 432 images — The 432 images belonged to 133 users. Metadata comprises about 490 million, 2.4 million and 174 million records. Counts include overseas usage and are not unique people. The 432 images and 133 users are not added to the reference sums because their correspondence with already counted data is unresolved. A November 5 correction said the 2.4 million records cover images uploaded mainly during about two days from January 1, 2016 and from January 1, 2020 (about 0.07% of all images), and that the about 174 million records relate to about 1.12 million accounts, of which about 57,000 have been closed.

    The initial notice describes 2.4 million separately extracted records in addition to the 490 million. The second notice leaves their scope, not the leakage itself, under investigation. The third report retains this exposed-data count. The 432 images and 133 users are not added.

    Official source
  20. Helpfeel174,000,000 records

    Deleted-image metadata

    About 23.62 million user records, 666.4 million metadata records and 432 images — The 432 images belonged to 133 users. Metadata comprises about 490 million, 2.4 million and 174 million records. Counts include overseas usage and are not unique people. The 432 images and 133 users are not added to the reference sums because their correspondence with already counted data is unresolved. A November 5 correction said the 2.4 million records cover images uploaded mainly during about two days from January 1, 2016 and from January 1, 2020 (about 0.07% of all images), and that the about 174 million records relate to about 1.12 million accounts, of which about 57,000 have been closed.

    Approximately 174 million additional records confirmed in the second notice; deleted image files themselves are excluded. The third report retains this exposed-data count. The 432 images and 133 users are not added.

    Official source
  21. Moi7 reported items

    7 personal-data records (scope and scale of the server log data under investigation) — The seven records with confirmed traces of external access are one record of a card expiry date and encrypted cardholder name, and six records of email addresses, activity history and similar data. The company says it does not hold card numbers or security codes. Separately, access to server log data partly containing account IDs and email addresses was confirmed; its scope and scale were still under review as of November 5.

    Counts the seven personal-data records with confirmed traces of external access (one card-expiry record and six email and related records). Server log data whose scale is under investigation are not added.

    Official source
  22. Data on 209 people at three client companies — Items include names, departments, employee numbers, survey answers, short-survey results and stress-check results. The figures are based on a report from the provider Lafool and may change or grow. No unauthorized access to the systems of Ashita no Team or Wellness Communications has been found.

    Counts the data on 209 people at three client companies confirmed as improperly obtained.

    Official source
  23. 387, 715, 52 and 93 people (four groups) — On TAITO Odekake Navi, 387 photo-download applicants (organization, name, email, phone, purpose and IP address), 715 people who requested materials or made inquiries (organization, name, address, email, phone and inquiry content) and 52 site-operation contacts; on the Tsutaju site, 93 people who made inquiries (name, email, address, phone, inquiry content and other data). The scope was finalized on October 26.

    Counts the 387 TAITO Odekake Navi photo-download applicants confirmed as leaked.

    Official source
  24. 387, 715, 52 and 93 people (four groups) — On TAITO Odekake Navi, 387 photo-download applicants (organization, name, email, phone, purpose and IP address), 715 people who requested materials or made inquiries (organization, name, address, email, phone and inquiry content) and 52 site-operation contacts; on the Tsutaju site, 93 people who made inquiries (name, email, address, phone, inquiry content and other data). The scope was finalized on October 26.

    Counts, as a separate group, the 715 people who requested materials or made inquiries, confirmed as leaked.

    Official source
  25. 387, 715, 52 and 93 people (four groups) — On TAITO Odekake Navi, 387 photo-download applicants (organization, name, email, phone, purpose and IP address), 715 people who requested materials or made inquiries (organization, name, address, email, phone and inquiry content) and 52 site-operation contacts; on the Tsutaju site, 93 people who made inquiries (name, email, address, phone, inquiry content and other data). The scope was finalized on October 26.

    Counts, as a separate group, the 52 site-operation contacts confirmed as leaked.

    Official source
  26. 387, 715, 52 and 93 people (four groups) — On TAITO Odekake Navi, 387 photo-download applicants (organization, name, email, phone, purpose and IP address), 715 people who requested materials or made inquiries (organization, name, address, email, phone and inquiry content) and 52 site-operation contacts; on the Tsutaju site, 93 people who made inquiries (name, email, address, phone, inquiry content and other data). The scope was finalized on October 26.

    Counts the 93 inquirers of the separate Tsutaju site confirmed as leaked.

    Official source
  27. Link Station317,971 reported items

    317,971 member IDs and other items (counted per item) — Counts are per data item, not people: 311,451 hashed passwords, 29,515 encrypted card-related records (first and last four digits and others), 309,759 names, 309,668 phone numbers and 311,426 emails, among others.

    Counts once the largest per-item figure, 317,971 member IDs; other per-item counts overlap with the same members and are not added.

    Official source
  28. Yakult Honsha39,505 reported items

    39,505 records — 31,781 email-inquiry records, 5,698 school-lunch site members (including encrypted passwords), 1,613 press inquiries, 354 web entrants to a cosmetics campaign and the names of 59 employees who handled inquiries.

    Counts the 39,505 records confirmed as leaked in the third report (the sum of the category counts, including 59 employee names).

    Official source
  29. 396,920 people — Names, phone numbers, email addresses and other data of applicants, contract signers and corporate users. The 30,067 people who signed employment contracts via ApplyNow Sign include, for some, My Number (number only), bank account data, basic pension numbers and residence-card numbers. ID-document images, interview videos and card data are not included.

    Counts the 396,920 applicants, contract signers and corporate users identified in the final report as affected by the leak. The 30,067 ApplyNow Sign employment-contract signers are presented as part of those people and are not added.

    Official source
  30. Basic4,317 reported items

    4,317 login email addresses and related data; 16,970 inquiry and other personal records of three client companies — The 4,317 records are ferret One users’ login email addresses and site names. The 16,970 records are 16,968 lead and inquiry records (names, contact details, etc.; de-duplicated) of one client and one inquiry record each of two other clients. Separately, non-public page content of four clients, containing no personal data, was viewed or taken. Login passwords and payment data are not confirmed as viewed or taken.

    Counts the 4,317 ferret One login email addresses and site names found to have been viewed or taken.

    Official source
  31. Basic16,968 reported items

    4,317 login email addresses and related data; 16,970 inquiry and other personal records of three client companies — The 4,317 records are ferret One users’ login email addresses and site names. The 16,970 records are 16,968 lead and inquiry records (names, contact details, etc.; de-duplicated) of one client and one inquiry record each of two other clients. Separately, non-public page content of four clients, containing no personal data, was viewed or taken. Login passwords and payment data are not confirmed as viewed or taken.

    Counts, as a separate group, the 16,968 de-duplicated lead and inquiry records of one client.

    Official source
  32. Basic2 reported items

    4,317 login email addresses and related data; 16,970 inquiry and other personal records of three client companies — The 4,317 records are ferret One users’ login email addresses and site names. The 16,970 records are 16,968 lead and inquiry records (names, contact details, etc.; de-duplicated) of one client and one inquiry record each of two other clients. Separately, non-public page content of four clients, containing no personal data, was viewed or taken. Login passwords and payment data are not confirmed as viewed or taken.

    Counts the two inquiry records, one each, of two other clients. The 16,970 total is not added on top of these figures.

    Official source
  33. 164,180, 4,762 and 209 records (three groups by data items) — Orderer (recipient) names in kana only: 164,180; names and addresses: 4,762; names, addresses, phone numbers and postal codes: 209. Order dates, store names and addresses and item names were also taken in some cases. Card data, IDs and passwords are stated not to have leaked. 7NOW is operating normally.

    Counts the 164,180 records of orderer (recipient) kana names alone confirmed as taken.

    Official source
  34. 164,180, 4,762 and 209 records (three groups by data items) — Orderer (recipient) names in kana only: 164,180; names and addresses: 4,762; names, addresses, phone numbers and postal codes: 209. Order dates, store names and addresses and item names were also taken in some cases. Card data, IDs and passwords are stated not to have leaked. 7NOW is operating normally.

    Counts, as a separate group with different items, the 4,762 records of kana names and addresses.

    Official source
  35. 164,180, 4,762 and 209 records (three groups by data items) — Orderer (recipient) names in kana only: 164,180; names and addresses: 4,762; names, addresses, phone numbers and postal codes: 209. Order dates, store names and addresses and item names were also taken in some cases. Card data, IDs and passwords are stated not to have leaked. 7NOW is operating normally.

    Counts, as a separate group with different items, the 209 records of kana names, addresses, phone numbers and postal codes.

    Official source
  36. istyle (@cosme)3,000,000 people

    Approx. 3 million people — User IDs, nicknames, names, postal codes, addresses, phone numbers, emails, gender, birth dates, skin type and hair type of members at the time of access, including those who later left. Login passwords and card data are stated to be excluded. This is a separate notice from the September file-transfer case.

    Counts the approximately 3 million @cosme common ID members confirmed as leaked.

    Official source
  37. Nojima7,000,000 reported items

    Approx. 7 million records — Names, birth dates, gender, addresses, phone numbers, login IDs, encrypted passwords and emails of members of the two sites. Former members are excluded. The company states it holds no card data.

    Counts the approximately 7 million member records of the two sites confirmed as leaked; former members are excluded.

    Official source
  38. IDC Frontier31 reported items

    Up to 31 personal-name/email records; 495 organizations affected — Registration data was queried for up to 71 customers, including up to 31 personal-data records at 31 customers. Four password changes are not added; the 495 affected organizations and 206 recoverable backups are not information counts.

    Counts up to 31 personal-data records confirmed queried without authorization; this is distinct from exfiltration. The former two records, 71 customer organizations, 495 affected organizations, 206 recoverable backups and four password changes are not added.

    Official source
  39. 69 accounts in total — Breakdown: 63 with names, emails, phone numbers and partial addresses; three with Vpreca numbers, dedicated security codes, expiry dates and names; three with partial Vpreca numbers. The three accounts with full card data were closed on October 31. The contractor GMO Payment Gateway describes the same data as possibly stolen. This is separate from the Ymirlink-related case announced on October 28.

    Counts the 69 accounts (63, three and three) that Life Card’s update says were found stolen; the breakdown is not added again.

    Official source
  40. Suntory Holdings90,000 people

    Approx. 90,000 people and six other groups — (1) About 90,000 group and partner-company employees (names and emails); (2) 7,323 Mal de Shine registrants; (3) 7,173 applicants for 2026 new-graduate business roles; (4) 1,097 contacts stored on two company phones; (5) 324 Monte Bussan and partner employees; (6) 96 Izutsu Maisen delivery customers and delivery staff; (7) 25 supplier employees. Payment data are not included.

    Counts the approximately 90,000 group and partner-company employees confirmed as leaked. The 1,097 phone contacts, 324 Monte Bussan and partner employees, 96 Izutsu Maisen records and 25 supplier employees are not added because overlap with this group is not disclosed.

    Official source
  41. Suntory Holdings7,323 people

    Approx. 90,000 people and six other groups — (1) About 90,000 group and partner-company employees (names and emails); (2) 7,323 Mal de Shine registrants; (3) 7,173 applicants for 2026 new-graduate business roles; (4) 1,097 contacts stored on two company phones; (5) 324 Monte Bussan and partner employees; (6) 96 Izutsu Maisen delivery customers and delivery staff; (7) 25 supplier employees. Payment data are not included.

    Counts the separate group of 7,323 Mal de Shine program registrants.

    Official source
  42. Suntory Holdings7,173 people

    Approx. 90,000 people and six other groups — (1) About 90,000 group and partner-company employees (names and emails); (2) 7,323 Mal de Shine registrants; (3) 7,173 applicants for 2026 new-graduate business roles; (4) 1,097 contacts stored on two company phones; (5) 324 Monte Bussan and partner employees; (6) 96 Izutsu Maisen delivery customers and delivery staff; (7) 25 supplier employees. Payment data are not included.

    Counts the separate group of 7,173 applicants for 2026 new-graduate roles.

    Official source
  43. 4,975 people

    Counts the updated 4,975 customers once. The prior 4,611, additional 364 and order/execution account counts are not added again.

    Official source
  44. 1,889 customers — 39 customers: names, emails, addresses, birth dates, phones, nationality, dividend accounts and suitability data; 1,850 customers: names and units purchased. No card data is held. No alteration of holdings or on-chain transfers has been found.

    Counts the 1,889 customers whose data was confirmed leaked (39 plus 1,850).

    Official source
  45. Matsuya Foods Holdings2,000 reported items

    2,000 app members (up to 3,000) and 2,377,127 Matsuben Net and other users — App-member data includes encrypted passwords; the 3,000 maximum includes the 2,000. Overlap between categories is not stated. The company says it holds no card data.

    Counts 2,000 app-member records listed as confirmed; the 3,000 maximum includes them and the difference is not added.

    Official source
  46. Matsuya Foods Holdings2,377,127 reported items

    2,000 app members (up to 3,000) and 2,377,127 Matsuben Net and other users — App-member data includes encrypted passwords; the 3,000 maximum includes the 2,000. Overlap between categories is not stated. The company says it holds no card data.

    Counts 2,377,127 Matsuben Net, mobile-order and delivery user records listed as confirmed.

    Official source
  47. Future Shop3,147,469 reported items

    3,147,469 member records at one store — Lindt discloses the same member records and is not added again. Credit card data is excluded. On October 30 Lindt revised its figure to 3,147,377 after removing double-counted members; the totals use the platform’s figure.

    Counts the identical 3,147,469 records disclosed by the platform and Lindt once, without multiplying by data fields.

    Official source
  48. Approximately 1.26 million records / 6,243 reservation-form entries — In addition to some fields in approximately 1.26 million H2O ID records, the second report found that 6,243 reservation-form entries (including participant application details; about 3% of 188,590 bookings) were leaked. The customer information at E-STORES and Remo Order mentioned in the first report was not found to have leaked.

    Counts once the approximate 1.26 million records explicitly described as having some personal information exposed on page 1. Unquantified purchase and card data under investigation on page 2 is not added.

    Official source
  49. Approximately 1.26 million records / 6,243 reservation-form entries — In addition to some fields in approximately 1.26 million H2O ID records, the second report found that 6,243 reservation-form entries (including participant application details; about 3% of 188,590 bookings) were leaked. The customer information at E-STORES and Remo Order mentioned in the first report was not found to have leaked.

    Counts the 6,243 reservation-form entries the second report found leaked (about 3% of 188,590 bookings) as data separate from the approximately 1.26 million H2O ID records; total bookings are not added.

    Official source
  50. Japan Atomic Energy Agency369 reported items

    369 files containing personal data (175 people as initially reported) — Updated from 367 to 369 files on October 30. Includes 200 identity documents, 146 health examination results and 23 radiation-worker certificates (up from 21); seven people had Individual Numbers included (up from six). No update to the 175-person figure was given. The total of 2,419 downloaded files is not added.

    Counts the 369 files containing personal data as updated on October 30; the earlier 367 is superseded.

    Official source
  51. GMO GlobalSign45,030 people

    2,492 companies and 45,030 people — Names, emails, linked-service names and custom attributes such as employee numbers in bulk-operation files (44,836 people), plus names, addresses, phone numbers and emails of billing contacts (194 people), de-duplicated by email. The third report updated the provisional 2,007 companies and 37,747 people. Passwords, MFA data and payment data are not included. Before June 7, 2021 no access logs exist, and that period is treated as one of possible acquisition.

    Counts the 45,030 people (de-duplicated by email) in files the third report judged obtained by third parties; the 2,492 companies and the provisional first-report figures are not added.

    Official source
  52. Approx. 37,800 ANA and 92,000 JAL/JTA customers — ANA: about 36,100 (names, booking references, flight details) and about 1,700 (also email, phone, passport number and nationality); JAL/JTA: about 90,000 and about 2,000 with similar items. Breakdowns are not added. Each airline’s figure covers its own reservation records. JAL states that card numbers and passwords were not exposed.

    Counts approximately 37,800 ANA customers whose reservation data showed viewing traces; breakdowns are not added.

    Official source
  53. Approx. 37,800 ANA and 92,000 JAL/JTA customers — ANA: about 36,100 (names, booking references, flight details) and about 1,700 (also email, phone, passport number and nationality); JAL/JTA: about 90,000 and about 2,000 with similar items. Breakdowns are not added. Each airline’s figure covers its own reservation records. JAL states that card numbers and passwords were not exposed.

    Counts approximately 92,000 JAL/JTA customers whose reservation records showed viewing traces; these are a different airline’s records from ANA’s, and the 90,000 and 2,000 breakdowns are not added.

    Official source
  54. Sony Life385,000 reported items

    Approx. 385,000 records — Names, birth dates, addresses, phones, policy numbers and contract details of Medicare Life policyholders and insureds handled by Sony Life as agent. Medicare Life’s identical figure is not added; the scope is still being identified.

    Counts the approximately 385,000 records listed as confirmed leaked; Medicare Life’s identical figure is not added.

    Official source
  55. 29,465 people — Names, kana, birth dates, gender, postcodes, emails, customer numbers and payment-management numbers; no card numbers. Credit Saison reports the same figure, which is not added.

    Counts the 29,465 Toku-Kai registrants whose data was reported downloaded; Credit Saison’s identical figure is not added.

    Official source
  56. ENEOS Power57 reported items

    57 customers — Names, addresses, customer-page login IDs and passwords and contract, usage and billing details; bank and card data are excluded.

    Counts the 57 customers whose data was found to have leaked.

    Official source
  57. Sony Network Communications2,141,986 reported items

    2,141,986 So-net member records and 443,495 plala (S course) member records — Names, phones, emails, user IDs, birth dates, gender and connection IDs (no passwords). Separately, email addresses with mail passwords (54,401 addresses across four services), 16 bank-account records and seven notice records leaked; they likely overlap with So-net members and are not added. No card data.

    Counts 2,141,986 current and former So-net member records; mail-password, bank and notice counts are not added because overlap with member records is unclear.

    Official source
  58. Sony Network Communications443,495 reported items

    2,141,986 So-net member records and 443,495 plala (S course) member records — Names, phones, emails, user IDs, birth dates, gender and connection IDs (no passwords). Separately, email addresses with mail passwords (54,401 addresses across four services), 16 bank-account records and seven notice records leaked; they likely overlap with So-net members and are not added. No card data.

    Counts the separate group of 443,495 plala (S course) member records; DOCOMO’s identical figure is not added.

    Official source
  59. Kufu Company1 people

    308 users, including one whose email was confirmed obtained — Birth dates and gender of 308 users were externally viewable; for one of them, the email address was obtained and could be linked.

    Counts the one user whose email address was confirmed obtained as confirmed exposure.

    Official source
  60. MICIN73 people

    Data on 73 patients viewed; unauthorized logins to 14 patient accounts and 6 accounts of 5 medical institutions — At three of the institutions whose accounts were accessed, data on 73 patients (names, email addresses, phone numbers, dates of birth, addresses, gender, medical record numbers, patient card numbers, consultation status and doctors’ notes) were viewed. Through patient accounts, names, email addresses, phone numbers, dates of birth, addresses, gender and patient codes may have been viewed. For some patients, prescription images, consultation records and service usage history are also affected. Names and email addresses of medical staff are also affected; their number is not stated. Identity documents and passwords are not included.

    Counts the 73 patients whose data were viewed through medical-institution accounts. The 14 patient accounts are not added because overlap with the 73 patients is not stated, and the medical staff, whose number is not given, are not added.

    Official source
  61. Smart Share14,034 reported items

    14,034 campaign participant records — Participant data from three MOS Burger social media campaigns (receipt challenge 2,995, Halloween giveaway 11,001 and VALX collaboration receipt campaign 38): X or LINE user names and IDs, entry times, draw and coupon status and similar data. Names, addresses, phone numbers, email addresses and card data were not collected and are not included.

    Counts the 14,034 participant records stated as the total leaked across the three campaigns (the sum of the per-campaign figures).

    Official source
  62. Bushiroad10,194 people

    10,194 closed beta applicants, 71 staff and related persons, 5 survey respondents and 3,034 customer support inquirers — Applicant data are email addresses, IP addresses, application times and device type. The 71 persons are employees of Bushiroad and affiliates (including names) and contractor employees (phone numbers). The 3,034 support inquirers contacted support between September 24 and October 14; besides inquiry text, the data include, depending on the inquiry, device information (2,832), player IDs (2,820), email addresses (311), names (257), phone numbers (11) and addresses/postcodes (6), all subsets of the 3,034. Passwords, card data and similar items are not confirmed as leaked.

    Counts the 10,194 closed beta applicants whose data were found to have leaked.

    Official source
  63. Bushiroad71 people

    10,194 closed beta applicants, 71 staff and related persons, 5 survey respondents and 3,034 customer support inquirers — Applicant data are email addresses, IP addresses, application times and device type. The 71 persons are employees of Bushiroad and affiliates (including names) and contractor employees (phone numbers). The 3,034 support inquirers contacted support between September 24 and October 14; besides inquiry text, the data include, depending on the inquiry, device information (2,832), player IDs (2,820), email addresses (311), names (257), phone numbers (11) and addresses/postcodes (6), all subsets of the 3,034. Passwords, card data and similar items are not confirmed as leaked.

    Counts, as a separate group, the 71 staff and related persons involved in running and developing the beta.

    Official source
  64. Bushiroad5 people

    10,194 closed beta applicants, 71 staff and related persons, 5 survey respondents and 3,034 customer support inquirers — Applicant data are email addresses, IP addresses, application times and device type. The 71 persons are employees of Bushiroad and affiliates (including names) and contractor employees (phone numbers). The 3,034 support inquirers contacted support between September 24 and October 14; besides inquiry text, the data include, depending on the inquiry, device information (2,832), player IDs (2,820), email addresses (311), names (257), phone numbers (11) and addresses/postcodes (6), all subsets of the 3,034. Passwords, card data and similar items are not confirmed as leaked.

    Counts the five survey responses containing personal data, published as a separate data set.

    Official source
  65. Bushiroad3,034 people

    10,194 closed beta applicants, 71 staff and related persons, 5 survey respondents and 3,034 customer support inquirers — Applicant data are email addresses, IP addresses, application times and device type. The 71 persons are employees of Bushiroad and affiliates (including names) and contractor employees (phone numbers). The 3,034 support inquirers contacted support between September 24 and October 14; besides inquiry text, the data include, depending on the inquiry, device information (2,832), player IDs (2,820), email addresses (311), names (257), phone numbers (11) and addresses/postcodes (6), all subsets of the 3,034. Passwords, card data and similar items are not confirmed as leaked.

    Counts the separate group of 3,034 customer support inquirers; the per-item counts are subsets and are not added.

    Official source
  66. Taito City (vendor Mirabo)197 reported items

    197 email addresses, relationship to the person with a disability, and disability category — No counts are given for the relationship and disability-category items. Names, addresses and phone numbers are stated to be excluded.

    Counts the 197 email addresses confirmed as leaked. The relationship and disability-category items, which have no count, are not added.

    Official source
  67. PingCAP50,000 reported items

    Up to about 50,000 records in Japan

    Counts the approximate maximum of 50,000 records in Japan explicitly described as leaked; individual fields are not added.

    Official source
  68. Chari-Loto373 people

    373 members — Member data, bank-account data, card data (last four digits, expiry and others), Charika account data and betting history.

    Counts the 373 Charika members whose data was found to have leaked.

    Official source
  69. 1,424,748 records (ID numbers, PINs and balances) — Of these, 569,224 were issued IDs and 855,524 unissued IDs. The company states no personal data were involved. Issued IDs were at risk of misuse but have been dealt with, and no actual loss is reported.

    Counts the 1,424,748 leaked records of ID numbers, PINs and balances, including unissued IDs. The 1,133,070 MOS Card records announced by MOS Food Services may fall within this figure and are not added.

    Official source
  70. Capcom11,774,247 reported items

    11,774,247 records worldwide — Additional attributes for 43 accounts, 196 unauthorized password changes and 19 Japanese retail accounts are subsets; the headline is not a Japan-only count.

    Counts the Japanese company’s worldwide 11,774,247 records. The 43, 196 and 19 Japanese account figures are subsets and are not added.

    Official source
  71. 6,628,007 Times Car records — Within the same account group, 1,464,800 ID images show exfiltration traces and 891,602 show access only. Overlap with Times Club’s five identity records, 135,436 linked IDs and other fields is unresolved.

    Replaces the previous approximate 6.6 million with 6,628,007 records confirmed exfiltrated in the fifth report. Images, attributes and authentication information concern the same account group; Times Club data is also excluded from addition because overlap is unresolved.

    Official source
  72. Treasure Factory746,277 reported items

    746,277 customer records; 750 business-contact/employee records; 1,000 device records — Eleven customer records also include names and addresses; overlap with other categories is unresolved.

    Counts 746,277 customer records once. The 11 with names and addresses are a subset. The 750 other records and 1,000 device records are not added because overlap is unresolved.

    Official source
  73. M325,775 people

    25,775 m3.com members and others; 2,260 pharmaceutical-company contacts — The six and 264 people with email-address exposure are subsets of their respective groups.

    Counts 25,775 members and other physicians; the six with email exposure are a subset.

    Official source
  74. M32,260 people

    25,775 m3.com members and others; 2,260 pharmaceutical-company contacts — The six and 264 people with email-address exposure are subsets of their respective groups.

    Counts the separate group of 2,260 pharmaceutical-company contacts; the 264 with email exposure are a subset.

    Official source
  75. Net Protections28,884 reported items

    28,884 transactions — Names and addresses (company and department for business users) and whether invoices were returned.

    Counts the 28,884 transactions whose data was confirmed accessed.

    Official source
  76. Six confirmed / up to 595 people including the six — Credentials for six people were confirmed exposed. The maximum 595 database subjects include these six; they are not added again.

    Counts the six people explicitly confirmed affected.

    Official source
  77. The Monogatari Corporation10,788,963 reported items

    10,788,963 records

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  78. Eyelash Garage49,191 reported items

    49,191 records — Company and salon names, names, phones, emails and password hashes; addresses, purchase history and card data are not found to have leaked.

    Counts the 49,191 customer records confirmed as leaked.

    Official source
  79. Nikkei (development cloud)1,830,000 reported items

    Approximately 1.83 million records — About 120,000 email records are within the 150,000 subset. The 1.83 million total is counted once; separate from the Google Workspace and Microsoft 365 incidents.

    Counts the published approximate 1.83 million once, comprising 150,000 personal-detail records and 1.68 million identifier-only records; 120,000 emails are not added.

    Official source
  80. Estore23,356,000 people

    Approximately 23,356,000 people across 7,858 stores — Final-report estimate after matching records; some duplication may remain. Partial card information for about 2,096,900 people is a subset. Store counts are not added, and this replaces the earlier maximum cumulative count.

    Counts the final published estimate of 23,356,000 matched people as confirmed. Some duplication may remain; the card subset and store count are not added.

    Official source
  81. Golf Digest Online1,789 reported items

    1,789 employee/vendor records; 55 customer records potentially affected

    Counts the 1,789 employee, former-employee and vendor records confirmed exfiltrated on October 16, separately from 55 customer records.

    Official source
  82. BK Japan Holdings11,180,000 reported items

    Approximately 11.18 million records — Published approximate record count; individual data fields are not added.

    Counts the published approximate 11.18 million member records whose exfiltration was confirmed.

    Official source
  83. nimoca521 reported items

    521 records

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  84. Tokyo Metro59,000 reported items

    About 59,000 email-address records — Email addresses of Metpo members whose delivery had been stopped because messages could not be delivered. The affected server held no member information other than email addresses.

    Counted once as confirmed: the October 15 update confirmed that about 59,000 email addresses whose delivery had been stopped were taken. No other member information was involved.

    Official source
  85. GMO Research & AI894,082 reported items

    894,082 records — The second report confirms the personal-data total. The previous maximum of 948,498, 9,068 records with personal data already deleted, 45,348 not extracted and 611 unauthorized point exchanges are not added.

    Counts only the second report’s confirmed 894,082 personal-data records. Excludes 9,068 records without personal data, 45,348 not extracted and the superseded maximum.

    Official source
  86. Kindal136,464 people

    136,464 people — Includes 109,311 people whose address information was involved; this subset is not added.

    The third report confirms 136,464 affected people. The 109,311 with address information are a subset and are not added. Reclassifies the existing possible amount as confirmed.

    Official source
  87. HOTELIER7,919 people

    7,919 people across 8 properties — The October 13 notice retains 7,919 people across 8 properties; property counts and related disclosures are not added.

    Rechecked 7,919 people in the notice dated October 13; the eight properties and related disclosures are not added.

    Official source
  88. Resorttrust26,000 reported items

    Group member information

    About 26,000 member records; about 36,000 reservation records

    Approximately 26,000 member records, separately disclosed from reservation information.

    Official source
  89. Resorttrust36,000 reported items

    Hotel reservation information

    About 26,000 member records; about 36,000 reservation records

    Approximately 36,000 reservation records; people are not deduplicated.

    Official source
  90. Saitama Prefecture2,200 people

    A list of about 2,200 people; details for 3 of them

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  91. White Essence1,050,000 accounts

    About 1.05 million accounts

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  92. Seicomart574,647 people

    574,647 people — Excludes people who had left the club by September 24; replaces the previous estimate of about 570,000 accounts.

    Counts the 574,647 people identified as subject to unauthorized viewing in the fourth report, replacing rather than adding to the prior possible scope of 570,000 accounts.

    Official source
  93. About 4.4 million policyholders and 40,000 agencies — About 220,000 people with account information are a subset. Policyholders and agencies are not added together.

    Information for about 4.4 million policyholders; the 220,000 bank-detail subset is not added.

    Official source
  94. Agency-related personal information

    About 4.4 million policyholders and 40,000 agencies — About 220,000 people with account information are a subset. Policyholders and agencies are not added together.

    Personal information for about 40,000 agencies, disclosed separately; not an outage count.

    Official source
  95. VOISING170,000 reported items

    About 170,000 records

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  96. Benefit One13,460 people

    13,460 people across 2,322 organizations

    People only; organization counts are not added. Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  97. 26 applicants — 26 applicants’ records were accessible; third-party viewing or downloading has not been established.

    Counts 26 applicants whose information was made accessible through the editing URL; this does not establish how many records third parties actually viewed or downloaded.

    Official source
  98. 177,426 people, potentially including duplicates — The figure may include the same person more than once.

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  99. eplus1,463 reported items

    1,463 records

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  100. EPARK Relax & Esthe22,180,000 records

    Leaked customer data records (EPARK)

    About 22.18 million records after review — Cannot be converted to unique people. Includes health information and five entries resembling card data.

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  101. Murauchi.com7,716,811 reported items

    7,716,811 records

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  102. LEAN BODY440,000 accounts

    About 440,000 accounts — The company expects the number of unique people to be lower than the account count.

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  103. Charm370,000 reported items

    Confirmed personal-information records

    About 370,000 confirmed; about 20,000 possibly affected records — Corrected on September 2. The 239 unauthorized logins are a separate measure.

    Uses the corrected figure of about 370,000; excludes the superseded 390,000 and 239 unauthorized logins.

    Official source
  104. KDDI12,231,954 people

    12,231,954 people — The 7,616,173 people with plaintext passwords are a subset. Related company figures are not added.

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  105. KAGA SOLNET165,587 people

    165,587 people

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  106. LY Corporation6,660,000 reported items

    Internal identifiers of domestic users

    About 5.74 million unique users in Japan — Distinct from about 6.66 million Japanese identifiers and about 6.1 million users worldwide.

    Uses about 6.66 million domestic identifiers rather than 5.74 million unique people. The 860,000 guest identifiers are not added separately because their relationship to the main count is not resolved here.

    Official source
  107. 2 Rinkan Yellow Hat3,179,454 people

    3,179,454 people

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source
  108. Universal Music Japan3,105,585 reported items

    3,105,585 records — A figure disclosed by a Japanese business, not necessarily a count of Japanese residents.

    Counted as information confirmed leaked, externally transmitted or viewed by a third party in the disclosure.

    Official source

Information potentially exposed — 259,552,988 reported items

  1. Club Tourism4,320,000 reported items

    Approx. 4.32 million records — Online members’ names, nationality, gender, birth dates, addresses, phone numbers, emails, member IDs and emergency contacts. Login passwords, passport, card and bank data are stated to be excluded.

    Counts the approximately 4.32 million online-member records described in the first notice as possibly leaked.

    Official source
  2. Ryohin Keikaku27,260,000 reported items

    Up to approx. 27.26 million records; approx. 1.09 million MUJI Card records and others — (1) Up to about 27.26 million MUJI app and online-store users, including former members: email address, birth date, gender and member ID; about 520,000 of them (so far) also include name, address and phone number. (2) About 1.09 million MUJI Card members who joined by July 2021: full card number, MUJI Card ID and birth date (about 345,000 cards still valid; cardholder name, expiry date and security code not included). (3) About 120 users who registered cards in the app or online store: first six and last two card digits and cardholder name. All may have been accessed externally. Some of the valid cards in (2) and the records in (3) were viewable together with user data in (1).

    Counts as possible the up to approximately 27.26 million MUJI app and online-store user records (including former members) that the second report said may have been accessed. The approximately 520,000 records that also include names and other data are a subset and are not added. The approximately 1.09 million MUJI Card records and approximately 120 partial card records are not added because they are stated to partly overlap with the users in (1) and the overlap cannot be separated.

    Official source
  3. Daiichikosho8,724,000 reported items

    About 8,724,000 records

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  4. Up to 15,128 records

    Counts the published maximum of 15,128 records as potentially exposed.

    Official source
  5. Doutor Coffee24,762 reported items

    24,762 member records and 9 delivery-address records

    Counts 24,762 member records; the separate 951-employee incident is excluded.

    Official source
  6. Doutor Coffee9 reported items

    24,762 member records and 9 delivery-address records

    Counts nine delivery-address records disclosed as a separate category; this is an information-record count, not unique people.

    Official source
  7. NTT Docomo300,000 reported items

    Up to about 300,000 records — The November 6 third report identified names, birth dates, addresses, phone numbers, email addresses, identity-document numbers and contract/plan data. Some records also contain legal-representative, employer, bank-account or childcare-program data. The maximum remains about 300,000 records; subsets are not added.

    Leakage of some customer data is confirmed, but scope and count are under investigation and the published figure is a maximum of about 300,000, so it is counted as possible under the rule for maxima that cannot be separated from a confirmed count.

    Official source
  8. SMBC Consumer Finance320,118 people

    Up to 320,118 people — Names, gender, dates of birth, addresses, home and mobile phone numbers, email addresses, driver’s licence numbers, employer information (phone numbers, annual income, etc.) and contract information (financial institution codes, customer numbers, guarantee amounts, guarantee start dates, etc.). Images of identity documents such as driver’s licences are not included. Affected people will be contacted after the scope is identified.

    The leak is confirmed but the scope is still being identified and the published figure is a maximum of 320,118 people, so it is counted as possible under the rule for maxima that cannot be separated from a confirmed count. Partner-bank disclosures are not added.

    Official source
  9. Arcadia3,136,000 email addresses

    SpeeCAN RAIDEN email addresses

    About 3,136,000 RAIDEN email addresses, 9,020 NET119 records and 97,000 119RAIDEN email addresses — The October 16 eleventh report corrected NET119 to 9,020 records. Phone/fax counts and customer subsets are not added.

    Approximately 3,136,000 potentially exposed email addresses. Phone/fax figures and customer subsets are not added.

    Official source
  10. Arcadia9,020 email addresses

    NET119 user information

    About 3,136,000 RAIDEN email addresses, 9,020 NET119 records and 97,000 119RAIDEN email addresses — The October 16 eleventh report corrected NET119 to 9,020 records. Phone/fax counts and customer subsets are not added.

    Counts personal information linked to 9,020 email addresses in the eleventh report, replacing the previous approximate 13,000. Individuals across services are not deduplicated.

    Official source
  11. Arcadia97,000 email addresses

    119RAIDEN email addresses

    About 3,136,000 RAIDEN email addresses, 9,020 NET119 records and 97,000 119RAIDEN email addresses — The October 16 eleventh report corrected NET119 to 9,020 records. Phone/fax counts and customer subsets are not added.

    Approximately 97,000 email addresses for 119RAIDEN after the URL correction. Its 17,000 phone numbers and 400 fax numbers are not added because overlap is unresolved.

    Official source
  12. Doutor Coffee951 people

    951 employees and former employees — 951 current and former employees at four stores. The November 6 update adds employee numbers, gender, nationality, employment/work/social-insurance details, relatives’ names, relationships and addresses, and bank-account data.

    Counts the 951 employees and former employees whose data may have leaked.

    Official source
  13. Member data

    About 7.7 million people (about 5.8 million members and 1.9 million non-members) — Total personal data stored in an external cloud service. The company has confirmed it may have been viewed or acquired; the actual number exposed and people affected remain under investigation. Member data (including former members) covers names, addresses, phone numbers, email addresses, gender, passwords (encrypted; excluding former members) and dates of birth; non-member data (purchasers without accounts, campaign entrants, etc.) covers names, addresses, phone numbers and email addresses. Fields vary by registration. Card data were not stored in that cloud and were unaffected, the company says.

    Counts, as possible, the about 5.8 million people in member data (including former members) that the second report says may have been exposed. The actual number exposed is under investigation.

    Official source
  14. Non-member data

    About 7.7 million people (about 5.8 million members and 1.9 million non-members) — Total personal data stored in an external cloud service. The company has confirmed it may have been viewed or acquired; the actual number exposed and people affected remain under investigation. Member data (including former members) covers names, addresses, phone numbers, email addresses, gender, passwords (encrypted; excluding former members) and dates of birth; non-member data (purchasers without accounts, campaign entrants, etc.) covers names, addresses, phone numbers and email addresses. Fields vary by registration. Card data were not stored in that cloud and were unaffected, the company says.

    Counts, as possible, the separately reported about 1.9 million people in non-member data (purchasers without accounts, campaign entrants, etc.). The total of about 7.7 million is the sum of the two categories and is not added separately.

    Official source
  15. Ymirlink51,628,280 reported items

    FC: 51,628,280 records in gross; BASE: 190 customer records — Exposure traces were found in 49 FC systems. The detailed table labels the gross figure as possible exposure; counts for 16 systems remain under investigation. The 190 BASE records are a separate customer-management dataset. Customer disclosures and the superseded approximate nine million are not added.

    Counts 51,628,280 once as possible exposure, following the detailed table. It is not confirmation of every record leaking. Customer disclosures such as 346,247 records and the former nine-million figure are not added. Counts for 16 systems remain under investigation.

    Official source
  16. 4,139 power-usage records — Consumption data (monthly and 30-minute values) with demand-side supply point numbers, and sales-of-power data (monthly and 30-minute values) with generation-side receiving point numbers. Names, addresses, phone numbers, email addresses, bank details and other contract information are not included, the company says.

    Counts, as possible, the 4,139 power-usage records described as possibly leaked externally.

    Official source
  17. Good Smile Company402,466 reported items

    Full card data possibly exposed for 2,800 people; last four digits etc. for 402,466 cards; order data for 5,356 people (all possible) — The number of people behind the 402,466 cards is still being confirmed. Up to 202 of 7,774 orders from 5,356 customers were viewed but cannot be identified. The 384 ordering customers and 185 card-change customers are subsets of the 2,800. Overlap between groups is not disclosed. Only the largest group, 402,466 cards, is used in the totals.

    Counts 402,466 de-duplicated cards whose last four digits and expiry may have leaked (people still being confirmed). The 2,800 people with full card data and 5,356 order customers are not added because overlap between groups is not disclosed.

    Official source
  18. BUSINESS TEC8,800 people

    About 8,800 people

    Counts the reported approximately 8,800 people once; the same Ashikaga incident is not counted separately.

    Official source
  19. and ST Holdings2,740,000 reported items

    About 2.74 million customer records; about 10,000 business contacts; about 24,000 employee records — Customer data: name, birth date, gender, address, phone number, email and member ID (no payment data or passwords). Employee data cover social-insurance enrollees from June 2013 to November 2022, including some former employees: basic details and social-insurance calculation data, with no My Number data or special-care personal information. The approx. 10,000 business contacts are the October 23 figure.

    Counts the approximately 2.74 million customer records described as possibly exposed in the November 4 update.

    Official source
  20. and ST Holdings10,000 reported items

    About 2.74 million customer records; about 10,000 business contacts; about 24,000 employee records — Customer data: name, birth date, gender, address, phone number, email and member ID (no payment data or passwords). Employee data cover social-insurance enrollees from June 2013 to November 2022, including some former employees: basic details and social-insurance calculation data, with no My Number data or special-care personal information. The approx. 10,000 business contacts are the October 23 figure.

    Counts approximately 10,000 separately reported business-contact records (October 23 figure; not mentioned in the November 4 update).

    Official source
  21. and ST Holdings24,000 reported items

    About 2.74 million customer records; about 10,000 business contacts; about 24,000 employee records — Customer data: name, birth date, gender, address, phone number, email and member ID (no payment data or passwords). Employee data cover social-insurance enrollees from June 2013 to November 2022, including some former employees: basic details and social-insurance calculation data, with no My Number data or special-care personal information. The approx. 10,000 business contacts are the October 23 figure.

    Counts, as a separate group, the approximately 24,000 employee records (including some former employees) disclosed on November 4 as possibly exposed.

    Official source
  22. Uchicomi142,591 accounts

    Member data of 142,591 accounts — Member data that may have been affected. Items are names, email addresses, birth dates, gender, addresses and phone numbers, depending on the member. The company says it holds no card data.

    Counts, as possible, the 142,591 member accounts described as possibly affected.

    Official source
  23. WILLs5,490,000 people

    Up to approx. 5.49 million people (including former members) — Names, emails and other reward-exchange information. The company states it holds no card or My Number card data.

    Counts the up to approximately 5.49 million members, including former members, described as possibly leaked.

    Official source
  24. 14,594 records (excluding duplicate entries; revised from approx. 15,500 in gross) — Names, ages, gender, occupations, marital status, household composition, phone numbers, emails, addresses and survey answers. The second report also gives a combined 14,848 people including 254 who entered both campaigns. Licence, card and bank data are excluded. The contractor is not named. The October 27 blastmail-related notice is a separate incident.

    Counts the 14,594 records excluding duplicate entries from the second report; the combined 14,848 people describes the same group and the first report’s approximately 15,500 is superseded.

    Official source
  25. 19,933 records (including duplicates for the same customers) — Names, addresses, phone numbers, order details and delivery addresses of customers who ordered made-to-order curtains at MUJI from April 10, 2018 to January 25, 2022. Card data and emails are excluded. The server is managed by Nanotec, a subcontractor of MN Inter-Fashion. This is separate from the MUJI app case.

    Counts the 19,933 records (including duplicates for the same customers) described as possibly leaked.

    Official source
  26. Up to 9,086 people (54 of whom may have had bank-account numbers exposed) — Names, addresses, phone numbers, emails, birth dates, gender, bank-account numbers and holdings of customers who opened accounts to apply for the digital bonds. The 54 are a subset. No card data were entrusted. None of the notices state a link to the NTT DATA STdirectServices case.

    Counts the stated maximum of 9,086 people as possible because only a partial leak is confirmed and the confirmed number cannot be separated. The 54 with bank-account numbers are a subset; Starts Securities gives no count.

    Official source
  27. Hana Cupid4,238,242 reported items

    Up to 4,238,242 records — Login IDs, hashed passwords (wording corrected on October 30) and email addresses. The figure is customers possibly affected; confirmed leaks are not separated. Names, addresses and card numbers are stated not to have leaked.

    Partial leakage is confirmed but not separable, so the maximum 4,238,242 possibly affected records are counted only as possible exposure.

    Official source
  28. World (subsidiary Tin Pan Alley)1,200,000 reported items

    Approx. 1.2 million member records in gross — Names, addresses, phones, birth dates, gender and emails. The figure is gross and details are being confirmed; card or other payment data and facial data are not found to have leaked.

    Counts the approximately 1.2 million member records in gross described as possibly leaked.

    Official source
  29. LifeNet Insurance / KDDI4,524 reported items

    22,541 records across six categories — Six categories by data combination (4,524; 226; 8,434; 3,662; 4,888; 807). No total is printed. Passwords, card, bank, identity-document and insurance-contract data are excluded.

    Counts 4,524 records in the table category (name, postcode, phone, email and member identifier); categories are distinct data combinations with no stated overlap.

    Official source
  30. LifeNet Insurance / KDDI226 reported items

    22,541 records across six categories — Six categories by data combination (4,524; 226; 8,434; 3,662; 4,888; 807). No total is printed. Passwords, card, bank, identity-document and insurance-contract data are excluded.

    Counts 226 records in the table category (name, postcode, phone and member identifier); categories are distinct data combinations with no stated overlap.

    Official source
  31. LifeNet Insurance / KDDI8,434 reported items

    22,541 records across six categories — Six categories by data combination (4,524; 226; 8,434; 3,662; 4,888; 807). No total is printed. Passwords, card, bank, identity-document and insurance-contract data are excluded.

    Counts 8,434 records in the table category (name, postcode, email and member identifier); categories are distinct data combinations with no stated overlap.

    Official source
  32. LifeNet Insurance / KDDI3,662 reported items

    22,541 records across six categories — Six categories by data combination (4,524; 226; 8,434; 3,662; 4,888; 807). No total is printed. Passwords, card, bank, identity-document and insurance-contract data are excluded.

    Counts 3,662 records in the table category (name, postcode and member identifier); categories are distinct data combinations with no stated overlap.

    Official source
  33. LifeNet Insurance / KDDI4,888 reported items

    22,541 records across six categories — Six categories by data combination (4,524; 226; 8,434; 3,662; 4,888; 807). No total is printed. Passwords, card, bank, identity-document and insurance-contract data are excluded.

    Counts 4,888 records in the table category (email and member identifier); categories are distinct data combinations with no stated overlap.

    Official source
  34. LifeNet Insurance / KDDI807 reported items

    22,541 records across six categories — Six categories by data combination (4,524; 226; 8,434; 3,662; 4,888; 807). No total is printed. Passwords, card, bank, identity-document and insurance-contract data are excluded.

    Counts 807 records in the table category (member identifier only); categories are distinct data combinations with no stated overlap.

    Official source
  35. Saga University80,000 people

    Approx. 80,000 people; patient-data count under investigation — Students, staff, former students and staff and other parties; includes names, birth dates, addresses, contacts, passwords and sensitive data such as clinical department and diagnoses. Patient-data counts remain under investigation and are not included.

    Counts approximately 80,000 students, staff and related people as possible exposure; patient data still being counted is not included.

    Official source
  36. Tokyu Land4,079 reported items

    4,079 member registrations and three inquiries — Counts are per site; overlap is not stated.

    Counts 4,079 GREEN CROSS PARK member registrations as possible exposure.

    Official source
  37. Tokyu Land3 reported items

    4,079 member registrations and three inquiries — Counts are per site; overlap is not stated.

    Counts three inquiry-form entries on the separate GREENUP Cooldown site as possible exposure.

    Official source
  38. Nihon Kotsu292,900 people

    About 292,900 people across six groups (leaked or possibly leaked) — About 13,100 hire-car customers, 60,100 drivers and staff, 107,900 job applicants, 37,700 family members, 2,100 business contacts and 72,000 accident counterparties. Some records include ID documents, My Number or health data; taxi passenger data is not included.

    Sums six groups disclosed as leaked or possibly leaked (about 13,100, 60,100, 107,900, 37,700, 2,100 and 72,000 people); counted as possible because confirmed cases are not separated.

    Official source
  39. Ministry of Foreign Affairs3,600 reported items

    Approx. 3,600 records, including about 900 relating to non-ministry people — Email addresses, names and other data. The closed network for classified information and consular systems such as passports were not affected, according to the ministry.

    Counts the approximately 3,600 records that may have leaked; the approximately 900 are a subset.

    Official source
  40. Coade7,622 people

    Up to 7,622 people — Names, addresses, phone numbers, emails and purchase history, still under review; card data is stated not to have leaked.

    Counts the stated maximum of 7,622 people as possible exposure.

    Official source
  41. 24,480 customer records — Names, vehicle registration numbers, store and staff names and cost or repair amounts for customers from November 2024 to September 2026; no addresses, phone, bank or card data. The 825 spoofed emails in the first report are messages sent and are not added.

    Counts the 24,480 customer records described in the second report as possibly leaked; spoofed-message counts are not added.

    Official source
  42. DHC5,096 accounts

    5,096 accounts altered — Member numbers, delivery details, purchase history and last four card digits of altered accounts may have been viewed. Up to 5,520 delivery addresses belong to the same accounts and are not added; 27 suspicious orders and 71 fraudulent registrations are counts of actions.

    Counts the 5,096 altered accounts whose data may have been viewed; the up to 5,520 addresses in the same accounts and counts of fraudulent actions are not added.

    Official source
  43. Fines1,536,322 reported items

    1,536,322 records

    Leakage of bookers’ names and contact details is confirmed, but the confirmed count cannot be separated from the 1,536,322 records, so the full scope is counted only as possible exposure.

    Official source
  44. ELESTYLE7,162 reported items

    7,162 merchant registration records — User names (company or personal names), email addresses, internal system identifiers and similar data. Login passwords, end-user data, card data, bank-account data, transaction data and ID documents are stated to be excluded. Order intake and payment processing were not affected.

    Counts, as possible, the 7,162 merchant registration records described as possibly obtained externally.

    Official source
  45. JFE Chemical230,000 reported items

    Up to about 230,000 personal-data records (obtained or possibly obtained) — Names, affiliations, phone numbers and emails, among others. Includes duplicates and data that cannot identify individuals on its own; under review. No card or bank data of business partners or external parties leaked, according to the company.

    Counts the up to about 230,000 records obtained or possibly obtained as possible, because confirmed records are not separated; duplicates are still under review.

    Official source
  46. Kufu Company307 people

    308 users, including one whose email was confirmed obtained — Birth dates and gender of 308 users were externally viewable; for one of them, the email address was obtained and could be linked.

    Counts 307 users whose birth dates and gender were viewable as possible exposure, excluding the one user already counted as confirmed within the 308.

    Official source
  47. Up to 133 records — Names, emails, telephone, mobile and fax numbers. This concerns a different system from the separately reported 743-record JETRO website incident.

    Counts the stated maximum 133 e-Venue records as possible exposure; this is a separate system from the existing JETRO website incident.

    Official source
  48. About 124,000 people — About 54,000 employees and 70,000 former employees; about 96,000 involve only addresses and phone numbers. Updated from about 120,000.

    Counts the updated about 124,000 people; the earlier about 120,000 is superseded.

    Official source
  49. Daito Gas124,000 reported items

    About 124,000 records

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  50. Joshin Denki6,000,000 reported items

    Up to about 6 million member records, 230,000 subscription records and 800 renovation photo records (possible) — All are maximum counts of possible exposure; the renovation photos include two driver-licence images, one My Number card and five bank account numbers. The company says these are not confirmed leak counts and it holds no card data.

    Counts up to about 6 million member-database records that may have leaked.

    Official source
  51. Joshin Denki230,000 reported items

    Up to about 6 million member records, 230,000 subscription records and 800 renovation photo records (possible) — All are maximum counts of possible exposure; the renovation photos include two driver-licence images, one My Number card and five bank account numbers. The company says these are not confirmed leak counts and it holds no card data.

    Counts up to about 230,000 records in the separate subscription system.

    Official source
  52. Joshin Denki800 reported items

    Up to about 6 million member records, 230,000 subscription records and 800 renovation photo records (possible) — All are maximum counts of possible exposure; the renovation photos include two driver-licence images, one My Number card and five bank account numbers. The company says these are not confirmed leak counts and it holds no card data.

    Counts up to about 800 renovation-photo records; the eight ID-image and account items are a subset and not added.

    Official source
  53. Rakuten Group860,000 reported items

    Up to approx. 860,000 logged-in users and up to approx. 40,000 property-staff accounts — Users’ names, emails, phones and countries of residence, and property staff’s account names and emails on the admin screen.

    Counts up to approximately 860,000 logged-in user records described as targeted, as possible exposure.

    Official source
  54. Rakuten Group40,000 accounts

    Up to approx. 860,000 logged-in users and up to approx. 40,000 property-staff accounts — Users’ names, emails, phones and countries of residence, and property staff’s account names and emails on the admin screen.

    Counts the separate group of up to approximately 40,000 property-staff accounts as possible exposure.

    Official source
  55. Green Monster6,190,000 reported items

    About 6.19 million user-information records — Includes information that is not personal data. Approximately 66,003 email addresses and other fields are subsets.

    Counts approximately 6.19 million user-information records once; email, nickname and other field counts are not added.

    Official source
  56. Sagawa Express53,230,000 reported items

    Up to approximately 53.23 million records, including duplicates — Substantial duplication remains after partial deduplication. This is neither a unique-person count nor a count of confirmed exfiltration.

    Counts the disclosed approximate maximum of 53.23 million records as possible exposure. Duplicates remain after partial deduplication; this is not a unique-person count. Component categories are not added.

    Official source
  57. Up to about 730,000 customers; up to 6,000 license images in a separate database remain under investigation — The confirmed portion is not separately quantified. The 6,000 images in a separate database are not added to the customer maximum.

    Some leakage is confirmed but its count cannot be separated from the approximate maximum of 730,000 customers, so the maximum is counted only as possible. Up to 6,000 license images are not added because overlap is unresolved.

    Official source
  58. Six confirmed / up to 595 people including the six — Credentials for six people were confirmed exposed. The maximum 595 database subjects include these six; they are not added again.

    The maximum 595 includes the six confirmed cases; 595 minus 6 gives up to 589 additional people counted as potentially exposed.

    Official source
  59. Recruit3,709,551 reported items

    Up to 3,709,551 records — Total across inquiries, reviews, dealers and staff. The 447,670 records with detailed addresses are a subset.

    Counts the reported maximum total across four categories once; the 447,670 detailed-address records are a subset.

    Official source
  60. UP Inc.13 people

    10 applicants and three administrators

    Counts 13 records for the separately reported groups of 10 applicants and three administrators; restored website counts are excluded.

    Official source
  61. NIFTY18,000 reported items

    Up to 18,000 records — Revised from the first report’s up to 542,513 records across three services after narrowing the scope to @nifty Hikari.

    Counts the up to 18,000 records in the second report; the first report figure of 542,513 is superseded.

    Official source
  62. Z-kai13 accounts

    13 accounts

    Counts the 13 accounts with unauthorized password changes and possible viewing of registered information.

    Official source
  63. Fuji Television730 reported items

    Up to 730 records

    Counts the current maximum of 730 records in the official PDF as potentially exposed.

    Official source
  64. 23,918 people at 16,950 businesses, preliminary — People and business counts describe the same scope and are not added together.

    Counts the preliminary 23,918 people once. The 16,950 businesses describe the same scope and are not added.

    Official source
  65. Account data by year (up to 11,106 student records and others) — School names, names, kana, account names and passwords of elementary and junior-high students and staff by year (2020, 2025, 2026; likely overlapping) and admin passwords for all 39 schools. Hokuyo High School files hold 179–200 records each. No total is published.

    Year-by-year counts likely overlap and no total is published, so only the largest figure, 11,106 student records for 2020, is counted as possible exposure; other years, staff and high-school files are not added.

    Official source
  66. Aena817,215 people

    Up to 817,215 people — Unauthorized viewing is confirmed; the maximum scope is counted only as possible exposure.

    Counts the maximum 817,215 people only as possible exposure because a confirmed-viewing subset is not separately quantified.

    Official source
  67. Sourcenext22,519,960 reported items

    22,519,960 possibly exposed records — Exfiltration is confirmed, but not for all 22,519,960 records; the full scope is counted only as possible exposure.

    Counts 22,519,960 potentially exposed member records only as possible; the confirmed subset is not separately quantified.

    Official source
  68. Golf Digest Online55 reported items

    1,789 employee/vendor records; 55 customer records potentially affected

    Counts the 55 potentially queried customer records; the 51 identifier-only and four personal-data records are subsets and are not added again.

    Official source
  69. Kobo (Hassha Orai Net)5,614 reported items

    Up to 8,341 bookings (5,614 people) — Katakana booking names, phone numbers and booked-bus details. The 8,341 bookings and 5,614 people describe the same scope and are still being finalized. Card, bank, address, email and password data were not stored.

    Counts the 5,614 people-based figure for the maximum possibly affected scope; the 8,341 bookings for the same scope and Hokkaido Chuo Bus’s cited figure are not added.

    Official source
  70. MoonStar593,000 people

    Up to 593,000 people — Theft was inferred from impersonation emails containing private order data; the maximum scope is counted only as possible exposure.

    Counts up to 593,000 people only as possible exposure; the confirmed-theft subset is not separately quantified.

    Official source
  71. Suzuki Nirin (Suzuki World)4,400 reported items

    Approx. 4,400 records — Names, emails, phones, addresses and inquiry text in the inquiry-form log; no sign of outflow found. The site operator Chubu Insatsu published the same notice.

    Counts approximately 4,400 inquiry-log entries that may have been viewed or obtained; the operator’s identical figure is not added.

    Official source
  72. Toypo697,209 people

    697,209 users — Phone numbers and user IDs, plus names, emails, birth dates, gender and addresses where registered; not every item for every user. Passwords, payment data and usage history are excluded. Disclosures by adopting stores are not added.

    Counts the 697,209 affected users as possible exposure; figures from adopting stores are not added.

    Official source
  73. Ride On Express Holdings6,500,000 reported items

    Up to about 6.5 million records — Not the number of confirmed leaked records.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  74. Temairazu4,450,000 people

    Up to about 4.45 million people — Reservation holders’ contact details such as names, phones and emails, and booking data; no card data is held. Individual hotel notices are not added.

    Counts the up to about 4.45 million people whose data may have been viewed or taken; individual hotel notices are not added.

    Official source
  75. BOOKOFF Group Holdings6,430,000 reported items

    Up to about 6.43 million membership-number records — Count of membership numbers, not unique people.

    Some leakage or access was confirmed, but a confirmed count cannot be separated from this scope. The entire figure is counted only under possible exposure.

    Official source
  76. dip3,885,771 reported items

    Up to 3,885,771 records — Leakage of every record in the maximum figure has not been confirmed.

    Some leakage or access was confirmed, but a confirmed count cannot be separated from this scope. The entire figure is counted only under possible exposure.

    Official source
  77. Anabuki Housing Service207,773 reported items

    207,773 possibly affected records — The figure does not confirm leakage of all 207,773 records.

    Some leakage or access was confirmed, but a confirmed count cannot be separated from this scope. The entire figure is counted only under possible exposure.

    Official source
  78. Scala Communications713,126 reported items

    Up to 713,126 cumulative inquiry records — Count of inquiries, not unique people.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  79. Hi-Ho38,509 contracts

    Contracts affected by unauthorized logins (Hi-Ho)

    38,509 contracts — A customer with multiple contracts may be counted more than once.

    Some leakage or access was confirmed, but a confirmed count cannot be separated from this scope. The entire figure is counted only under possible exposure.

    Official source
  80. Up to 627 people — Phone numbers, addresses, email addresses and card data were not included.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  81. MrMax1,735,154 people

    Up to 1,735,154 people

    Some leakage or access was confirmed, but a confirmed count cannot be separated from this scope. The entire figure is counted only under possible exposure.

    Official source
  82. Daiki Suisan174,933 people

    174,933 people

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  83. Medical-professional information

    About 514,000 healthcare professionals, plus other categories — About 44,000 with email addresses and other data are a subset. Separately, about 700 employees.

    Up to approximately 514,000 people; the 44,000-person email subset is not added.

    Official source
  84. Employee information

    About 514,000 healthcare professionals, plus other categories — About 44,000 with email addresses and other data are a subset. Separately, about 700 employees.

    Approximately 700 employees, disclosed as a separate information category.

    Official source
  85. About 200 images

    Counts about 200 images as about 200 information items, not patient headcount or image-metadata records.

    Official source
  86. Evergreen Marketing237 reported items

    237 agency and partner contacts and 763 corporate customers — Partner contacts: organization names and email addresses. Corporate electricity customers: organization names, addresses, account details containing personal names and billing amounts.

    Counts 237 agency and partner contact records that may have been viewed.

    Official source
  87. Evergreen Marketing763 reported items

    237 agency and partner contacts and 763 corporate customers — Partner contacts: organization names and email addresses. Corporate electricity customers: organization names, addresses, account details containing personal names and billing amounts.

    Counts the separate group of 763 corporate-customer records, including account details with personal names.

    Official source
  88. Active54,916 reported items

    Up to 54,916 records

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  89. SOFTSU159,850 phone numbers

    Phone numbers in potentially exposed call data (Softsu)

    159,850 telephone numbers — Count of telephone numbers, not unique people.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  90. i-plug / OfferBox314,009 people

    Theoretical maximum: 314,009 students — Not the number actually viewed.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  91. Nikkei1,646 people

    1,646 people — Readers and news sources are excluded. Separate from the Microsoft 365 incident.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  92. Recruit3,687 email addresses

    Email addresses whose registration may have been identified (Study Sapuri)

    3,687 email addresses

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  93. 55 members — Names, phones, emails, login IDs, usage history and reservations; for members who registered them, driver-licence details (number, address, birth date) and card last four digits and holder names may also have been viewed. This is a separate intrusion from the previously listed first event.

    Counts the 55 members whose pages were accessed and whose data may have been viewed.

    Official source
  94. Up to 2,272 people

    Counts the stated maximum 2,272 people once: 1,261 children, 953 guardians and 58 staff. The 114 children with additional care information are a subset.

    Official source
  95. Nabari Kintetsu Gas6,800 reported items

    About 6,800 records

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  96. G-PLAN70,000 reported items

    Up to about 70,000 member identifiers

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  97. Two patient photographs and data for two staff members

    Counts two patient photographs as two information items, not image metadata.

    Official source
  98. Two patient photographs and data for two staff members

    Counts the separate group of two staff members.

    Official source
  99. 1,409 people

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  100. 41 people — Card data is limited to the last four digits and cardholder names. The notice does not state leakage of license images.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  101. LEGOLAND Japan1,557 reservations

    Hotel reservations potentially affected by unauthorized access (LEGOLAND Japan Hotel)

    1,557 reservations

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  102. REQREA1,060,338 people

    1,060,338 people — The figure is not limited to residents of Japan.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  103. istyle10,997 people

    10,997 people

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  104. 214,916 people on the portal and three other systems (overlapping) — Portal 214,916; design-change approvals 29,621; sales system 86,015; quality reporting 46,445. The same people appear in several systems, according to the notice. Only authorized system users could view the data; no passwords are included. Separate from the June 16 disclosure.

    Because the notice says the same people appear across systems, only the largest group, 214,916 portal users, is counted as possible exposure; the other three systems are not added.

    Official source
  105. Digital Agency246,000 reported items

    About 246,000 records

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  106. SAKURA internet1,360,563 accounts

    1,360,563 accounts — Includes 951 rental-server accounts. A link between the two system compromises was not established.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  107. FUSO DENTSU26,489 reported items

    26,489 records

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  108. FIVE FOXes73,185 reported items

    Customers 59,504, inquiry customers 8,403, employees 5,278 in total (possible) — Employees: 2,450 at Five Foxes and 2,828 at COMME CA; card and My Number data are not included.

    Sums four separately disclosed groups (59,504 customers, 8,403 inquiry customers, 2,450 Five Foxes employees and 2,828 COMME CA employees).

    Official source
  109. Charm20,000 reported items

    Possibly exposed personal-information records

    About 370,000 confirmed; about 20,000 possibly affected records — Corrected on September 2. The 239 unauthorized logins are a separate measure.

    The approximately 20,000 records are disclosed separately from the 370,000 confirmed records.

    Official source
  110. Yellow Hat1,801,499 people

    Up to 1,801,499 people

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  111. Tokushima Prefecture460,000 reported items

    About 460,000 cumulative records — About 180,000 cumulative records containing My Number identifiers are a subset.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  112. Toshiba Tec382,123 people

    382,123 people

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  113. ASKUL600,000 reported items

    About 600,000 additional records — External leakage or misuse of the newly added information was not confirmed.

    Only the additional scope in this update; earlier figures are not added. Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  114. Komatsu139,302 people

    139,302 people — The disclosure does not describe unrestricted public access.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  115. Customer information on missing media, counted in supply points (Kyushu Electric Power Transmission and Distribution)

    Up to 10.9 million supply-contract records — Count of supply contracts, not unique people.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  116. Medica Shuppan641,000 people

    About 641,000 people, potentially including duplicates — May include the same person more than once.

    Counted as a disclosed scope of possible exposure, accessibility or continuing investigation.

    Official source
  117. Enessance Holdings365,000 reported items

    About 365,000 potentially affected records — The figure does not mean leakage of every record was confirmed.

    Some leakage or access was confirmed, but a confirmed count cannot be separated from this scope. The entire figure is counted only under possible exposure.

    Official source
Excluded incidents and reasons (102 incidents)

No settled figure: undisclosed, under investigation or not specified (74 incidents)

  1. Affected count undisclosed

    Official source
  2. No personal-data leak confirmed so far — The investigation was completed, as announced on November 6. It found no confirmed leak of personal or card data and no confirmed unauthorized logins.

    Official source
  3. 26,739 potentially affected servers; exposed-data count undisclosed — Server counts are not converted into leaked-information counts.

    Official source
  4. No external leak of personal or confidential data found — The source does not disclose an information count.

    Official source
  5. Count not disclosed — Names, birth dates, gender, phone numbers, addresses, emails, career history and password hashes (items vary by member).

    Official source
  6. Developer's investigation found no evidence of malicious activity on this store — From 19:06 on October 14 to about 1:32 on October 15, malicious code redirecting to a fake checkout may have loaded on some shops using the app; customers may have entered card details on the fake site. No data were taken from the shop’s database. The wishlist feature is suspended as the vendor’s precaution.

    Official source
  7. Number under investigation

    Official source
  8. Count under investigation — Some customers who used the old Denny's app are affected. Items are member codes, email addresses, birth dates, gender, prefecture, favorite restaurant and children's birthdays. The company says it does not hold names, addresses, phone numbers, passwords or card data. Only access records for October 7 have been reviewed; whether data were taken and how many people are affected are under investigation.

    Official source
  9. Count and number of client companies not disclosed — Affected data include information on client companies’ admin-screen users (names, email addresses and encrypted passwords), LINE official account settings, and personal data of the clients’ end users (items vary by client). No card data are held. Client UCC Ueshima Coffee announced that 5,529 of its email addresses were confirmed as leaked.

    Official source
  10. Count not disclosed (login email addresses) — Users’ login email addresses may have been viewed or obtained; other registration data such as names are stated to be excluded.

    Official source
  11. Count under investigation; distributors and issuers disclose separately — NTT DATA gives no count. Rakuten Securities’ gross 362 records span three bond issues and include the Kagome (109) and JR West (2) figures. Kintetsu Group Holdings’ 2,678 records (names and purchase amounts) may overlap with distributors’ figures. All are shown as related disclosures and not added.

    Official source
  12. Personal-data count and fields under review — Potentially includes sales and transaction information and personal data of customers, inquirers and employees. No count disclosed.

    Official source
  13. Count under investigation (reservation data of guests at some contracted facilities) — Reservation data including names and contact details; the exact items and count are under investigation. Card data are not stored. No site-controller integration data leaked.

    Official source
  14. No external leak of personal or customer data confirmed; investigation continues — The source does not disclose an information count.

    Official source
  15. Whether data leaked is being checked — The source does not disclose an information count.

    Official source
  16. Count not disclosed — Names and partial addresses and phone numbers of customers who requested watch repairs at group stores since September 2025.

    Official source
  17. No personal-data leak confirmed — Expected loss of about JPY 550 million (a monetary amount, not an information count). This is separate from the RAKUS Lite Cloud blastmail incident.

    Official source
  18. Whether data leaked is under investigation — The source does not disclose an information count.

    Official source
  19. Count under investigation — The source does not disclose an information count.

    Official source
  20. Count under investigation — The source does not disclose an information count.

    Official source
  21. Number under investigation

    Official source
  22. Count undisclosed — Four counts stopped servers, not leaked information records. An external investigation is being arranged.

    Official source
  23. Affected people and document count unknown — Approximately 300 forms is the caller’s claim, not a verified count, and is not included in totals.

    Official source
  24. Personal-data impact under investigation — The source does not disclose an information count.

    Official source
  25. Under investigation; overall count undisclosed — Customer disclosures are related information within the same incident and are not added to an unknown overall count.

    Official source
  26. Count under investigation

    Official source
  27. Affected count undisclosed

    Official source
  28. Affected count undisclosed

    Official source
  29. Personal data of 1,932 people (four hard drives) — 1,037 people from companies, the national government and municipalities, and 895 local residents and others. Most entries contain only names; some include addresses or phone numbers. No leak or other secondary harm has been confirmed so far.

    Official source
  30. Count undisclosed

    Official source
  31. Affected count undisclosed

    Official source
  32. Affected count undisclosed

    Official source
  33. No personal-data exposure found in the investigation

    Official source
  34. Scale not disclosed

    Official source
  35. Affected number and period under investigation — The source does not disclose an information count.

    Official source
  36. Affected scope and count under investigation — The affected sites and information count have not been disclosed.

    Official source
  37. Number undisclosed

    Official source
  38. Number undisclosed

    Official source
  39. Number not disclosed

    Official source
  40. Number under investigation

    Official source
  41. 483 files sent by 139 schools — Counts viewed attachments. The number containing personal information and the number of affected people were not disclosed; excluded from gross information totals.

    Official source
  42. Multiple accounts; information count undisclosed — The source does not disclose an information count.

    Official source
  43. Number not disclosed

    Official source
  44. Number under investigation — Traces of file exfiltration were found; customer-data exposure remains under investigation.

    Official source
  45. Number not disclosed

    Official source
  46. Leak count under investigation — About 9,000 counts impersonation emails sent, not leaked records.

    Official source
  47. Count undisclosed — Leakage of internal information is confirmed; whether it includes personal information and its scale are undisclosed.

    Official source
  48. Number under investigation

    Official source
  49. Approx. 9,000 customers — Names, account numbers, closure amounts, reasons and last transaction dates for accounts closed from July 1992 to March 2001 at predecessor banks; the records were most likely discarded by mistake.

    Official source
  50. Number not disclosed — As of September 25, no traces of external transfer or unauthorized access to personal information had been found.

    Official source
  51. Data alteration affecting 14 users — The company reported no leakage. The 14 users concern alteration, not exposed information, and are excluded from exposure totals.

    Official source
  52. 426 affected accounts — Accounts affected by unauthorized access to web-server storage; not a disclosed exposure count.

    Official source
  53. Number not disclosed — Separate from the August ransomware incident at REXT.

    Official source
  54. Number not disclosed — One employee refers to the compromised account holder, not the number of exposed people.

    Official source
  55. 233 application documents (172 applicants) — 79 certificate and 154 medical-support applications, covering 172 applicants after removing overlap; they include names, addresses, Individual Numbers, diagnosis details such as illness and medical history, and family information.

    Official source
  56. Affected scope under investigation — Approximately 200,000 head-office backup files are being investigated; this is not a count of lost or exposed files.

    Official source
  57. Number not disclosed

    Official source
  58. Number not disclosed — As of August 21, full system recovery was expected around the end of October.

    Official source
  59. See the announcement for category figures

    Official source
  60. Number of affected users not disclosed — This does not establish full recovery of all functions or dotgift.

    Official source
  61. Number not disclosed — This does not mean all international transport operations stopped.

    Official source
  62. Number not disclosed

    Official source
  63. Affected systems; personal-data count not disclosed — The company reported no traces of transfer of information received from customers or partners.

    Official source
  64. Number not disclosed

    Official source
  65. Number not disclosed

    Official source
  66. Number of affected people not disclosed

    Official source
  67. Number not disclosed

    Official source
  68. Number not disclosed

    Official source
  69. Number not disclosed

    Official source
  70. Number not disclosed — The company reported no impact on internal core operations.

    Official source
  71. Some shared-hosting plans — Separate from the email-information breach.

    Official source
  72. Number not disclosed

    Official source
  73. Number not disclosed

    Official source
  74. Number not disclosed

    Official source

Multiple categories or scopes require further reconciliation (18 incidents)

  1. All customer-contract information; non-contract information exposed for 421 contracts — 421 counts contracts, not all exposed records or recipients. For the 76 contracts newly identified on November 4, no exposure of reader data (recipient addresses, customer lists, etc.) or email bodies has been confirmed. Overlap with the information of all customers cannot be separated. Customer disclosures are related information for the same incident.

    Official source
  2. 319 registration records and up to about 4.2 million log records — Logs may include repeated information about the same users. Their overlap and scope relative to registration records remain unresolved, so neither figure is added to the reference sums.

    Official source
  3. Up to approx. 40,000 bookers and up to approx. 2.6 million logged-in users — Payment data (issuer number, last four digits, name, expiry) for up to about 36,000 bookers is a subset. Overlap between bookers and logged-in users is not stated. Full card numbers, passwords, ID documents and addresses are excluded.

    Official source
  4. 1,213 customer company records and sales data for 875 companies; personal-information count under investigation — Overlap between the company and sales-data figures and the number of personal-information records are unconfirmed; neither figure is included in the gross information total.

    Official source
  5. About 307,000 members (estimated) — Includes about 126,000 with email addresses and about 42,000 employee and demo accounts.

    Official source
  6. 310 files publicly exposed; 1,044,906 records potentially affected — 27 applicants and employees were notified. These figures use different units and scopes and are not added.

    Official source
  7. Up to 323,000 email records; 362,000 partial card-data records — Maximum figures for separate data fields, not a combined count of people.

    Official source
  8. 449 resumes; 1,845 employment-history documents

    Official source
  9. Up to 7,200 email addresses; up to 6,000 transaction records — Separately, data for 4,778 employees. Categories are not added together.

    Official source
  10. About 1,100 staff and 7,400 external email addresses — Counts of email addresses, not unique people.

    Official source
  11. 2,835 blogger records; other categories listed separately — Separately: 630 project records, 11,237 emails and 10,780 business-contact records.

    Official source
  12. Up to 19,000 employee-related and 36,000 external-contact records

    Official source
  13. 3,308 delivery; 6,849 partner; 43,709 employee-related records — Separately, 43,709 employee-related records. Categories are not added together.

    Official source
  14. 69,586 / 143,126 / 365 / 4,218 records by category — Categories are not added together. The 143,126-record category includes Coco Card numbers and PINs.

    Official source
  15. About 40,000 Azas and 20,000 Sloop accounts

    Official source
  16. About 192 individual and 722 corporate contacts; about 7,670 email-only contacts — Separately, about 7,670 email-only contacts. About 31 with account information are a subset.

    Official source
  17. 1.525 million customer-inquiry records; 378,000 partner records, and other categories — Separately: 117,000 ceremonial contacts, 107,000 employee records and 162,000 family records. The confirmed scope announced on February 18 was not revised.

    Official source
  18. 602,000 / 404,000 / 33,000 / 2,044 records by category — Separately, 33,000 sales-contact records and 2,044 employee/family records. No aggregate total.

    Official source

Overlap between separate events at the same service is unresolved (10 incidents)

  1. Number under investigation — A separate route from the October 14 incident. Scope and overlap remain unresolved; no numerical amount counted.

    Official source
  2. About 14.64 million customer records and card data of up to 6,140 people; 32,341 refund bank accounts (leaked); about 936,000 partial card records and about 118,000 travel insurance records (possible) — About 4.13 million hashed-password records are a subset. Including the third report’s 32,341 refund bank accounts (confirmed), about 936,000 masked card records (about 414,000 people, 12 with full numbers) and about 118,000 travel-insurance records (possible), overlap between groups and with the other two events is unresolved, so they are not added.

    Official source
  3. 2,155,345 records

    Official source
  4. 26 records — Not added to the LAWSON ID event.

    Official source
  5. About 5.26 million customer records, 50,000 delivery-recipient records and 4,100 merchant records — About 490,000 email records are a customer-data subset. Overlap across customer, recipient and merchant categories is unresolved; excluded from the gross reference sum.

    Official source
  6. 17,780 records, including duplicates — Other affected information is still being counted. Not added to the other two events.

    Official source
  7. About 12,000 reservations — Not a count of people including companions. Not added to the other two events.

    Official source
  8. 687 accounts — The three events are not added because overlap is unknown. The date is the information cutoff stated in the notice.

    Official source
  9. 313 accounts — The three events are not added because overlap is unknown. The date is the information cutoff stated in the notice.

    Official source
  10. 15,382 accounts — The three events are not added because overlap is unknown. The date is the information cutoff stated in the notice.

    Official source

ContactAI Legal Lab