依企業、國家、產業、發生年份和攻擊方式查詢事件，了解外洩資料、影響範圍、查證狀態、企業應對及來源。
A user-management misconfiguration allowed registered users to view each other’s directory data inside the system; discovered Apr 23, 2026 and disclosed June 16. Not exposed to the open internet.
Possible data leak: A PC discarded in late April 2026 still held data and briefly reached a third party. After recovery, exposure of 2013-09 to 2016-03 online-shop buyers could not be ruled out; disclosed June 16.
After card-brand alerts, card payments stopped March 9, 2026. Investigation found possible card leakage (Mar 21, 2025–Mar 10, 2026) with some misuse risk, plus customer-data exposure (Apr 6, 2021–Mar 10, 2026); disclosed June 15.
On June 10, 2026 an Oe JHS trip teacher booklet was lost in Tokyo, covering trip lists (120), allergy lists (11) and a class roster (126); disclosed June 15 (distinct from the NPO-portal redaction incident).
On June 8, 2026 staff meant to send a blank form but attached a personal-data contact list to one committee member; after deletion confirmation a June 12 press release followed.
On June 8, 2026 staff emailed a 4,363-row member file with personal data to two external recipients; deletion confirmed June 9; disclosed June 12.
Ransomware on a FAX file server confirmed June 1, 2026 after VPN intrusion. 633 partner/customer records in FAX PDFs from Aug 1, 2024–June 1, 2026 may have been exfiltrated; disclosed June 12.
On June 9, 2026 a billing email to 22 certified centers wrongly attached a citywide childcare roster. By June 11 all centers confirmed deletion without reuse; disclosed June 11.
In late May 2026 a faculty member left an unlocked university laptop on a train. 418 mail counterparts (including 47 students) were listed as possible exposure; disclosed June 9.
Possible data leak: After EHR refresh, some contracted-for-destruction HDDs were found circulating unbroken; disclosed June 8, 2026.
Possible data leak: Same-day disclosure pattern as the cancer center: contracted HDD destruction failed and media entered circulation; disclosed June 8, 2026.
Possible data leak: A backup SSD for wheeling/switching systems was found missing May 26, 2026; police report June 4; first public notices and METI information order June 8 (up to 10.9M contracts). Parent company’s July 8 second report published a refined total of 13.54M; no confirmed exfiltration yet.
On June 3, 2026 the designated manager sent lottery emails with addresses in To: instead of Bcc, exposing 552 winners across 25 classes; the city disclosed June 8.
Intrusion from about 18:00 June 4 to 09:00 June 5, 2026 detected June 5 with a same-day first notice. Confirmed leak of purchaser/shipping name, address, phone and group name. Count reported to PPC but withheld publicly; full report July 30.
Possible data leak: On May 29, 2026 hometown-tax personal data was posted publicly on SNS; deletion requested the same day, confirmed May 30, disclosed June 5. Cause under investigation.
Possible data leak: Unauthorized logins detected June 2, 2026. Between May 26 and June 2, credential stuffing produced 2,503 member-page logins; disclosed June 5. Passwords are hashed; no internal credential leak confirmed.
Possible data leak: After pre-release “anemoi” master data appeared online Apr 19, 2026, stolen cloud-storage credentials on the internal portal were identified. PPC flash report May 11; public notice June 4; second notice July 31 (full report June 29).
On Apr 17, 2026 the Iwate branch mailbox was abused to send spam. Up to 1,051 past email counterparts’ addresses, names and affiliations may have been viewed; disclosed June 4.
Possible data leak: A nurse’s personal PC holding patient data against policy was remotely compromised in a support scam on May 25, 2026; reported May 30 and disclosed June 3. No impact on hospital core systems was confirmed.
Unauthorised logins to the smartphone app may have allowed viewing of personal information. The completed external investigation reported June 19 found no traces of leakage or secondary harm.