Search incidents by company, country, industry, year and attack method. Review affected data, impact, verification status, company responses and sources.
Around January 30, 2026, a manual error mismatched member IDs and names, so some members received Health Risk Assessment mailers showing another individual’s name, health plan name and programme name.
On April 24, 2026 the circular-society section sent a Plastic 3R business mail with mutually visible addresses; noticed the same day and disclosed April 27.
Possible data leak: After the ielove CLOUD intrusion, a April 25 first notice and May 2 second notice confirmed 2,092 leaked customer records and field list.
A March 2026 teacher-exam FOI electronic file had a flaw allowing personal data to be viewed with certain operations; noticed April 20 and disclosed April 24.
Possible data leak: After confirming third-party access to the site my-page from April 20, 2026 onward, Canet acknowledged external leakage of login credentials and disclosed April 24.
Possible data leak: The gift-catalogue e-commerce contractor detected anomalies on April 10, 2026, confirmed ransomware, reported April 16 and the co-op disclosed April 24.
Around March 24, 2025, GrayRobinson detected unauthorised network access; some files may have been accessed or removed between March 5 and 24, 2025, and on April 13, 2026 they were found to contain personal information.
The June 19 final report confirmed personal-information exposure affecting 3,179,454 people. The earlier maximum of 3,455,754 is not retained as an exact total.
Possible data leak: A desktop PC from Haneda T2, staged for disposal in the T1 warehouse, could not be found during an April 3, 2026 disposal check; disclosed April 23.
Unauthorised activity was identified around March 2, 2026; files were copied from the internal network on March 1, 2026.
Possible data leak: An imaging contractor mis-set cloud sharing so files were readable by unauthorised parties from early April 2023 to mid-December 2024; disclosed April 23, 2026.
Certain information may have been accessed by an unauthorised individual on March 6–7, 2026.
After ielove’s CLOUD-intrusion disclosure and an April 20 report saying some Taisei customer data may have leaked, the firm disclosed on April 22.
Possible data leak: Around April 8, 2026, the firm discovered an unauthorised individual had accessed its tax software system; tax returns were not directly affected, but exposure of personal information could not be ruled out.
On October 29, 2025, the company learned an unauthorised actor had temporary access to a limited portion of its Help Center; email addresses, IP addresses from activity between April 17 and October 29, 2025 and linked public social media information may have been accessed.
Possible data leak: After the April 2, 2026 attack on maintenance contractor YCC, paddy-conversion system data was found on the vendor server; disclosed April 20. Exfiltration not confirmed.
Possible data leak: ielove reported unauthorised access and data acquisition on April 5–6, 2026; Clearth’s April 20 notice and May 13 follow-up listed name, email, phone, address and preferences among leaked fields.
Possible data leak: After the April 2, 2026 attack on former contractor YCC, April 2019 welfare-medical data was found on the vendor server; disclosed April 17.
After receiving ielove’s April 16, 2026 investigation report on the April 5–6 CLOUD intrusion, Nihon Zaitaku disclosed possible customer-data leakage on April 17.
Possible data leak: After the April 2, 2026 YCC attack, clinic medical-admin data was found on the vendor server by April 16; disclosed April 17.