Suchen Sie nach Unternehmen, Land, Branche, Jahr und Angriffsmethode. Prüfen Sie betroffene Daten, Umfang, Bestätigungsstatus, Maßnahmen und Quellen.
Possible data leak: 83 leased staff laptops went missing/stolen; 3 held personal data including a 115,526-row resident file on a Civic Affairs PC; disclosed May 29, 2026 (distinct from the Minatogawa JHS HDD incident).
Possible data leak: Multi-child benefit notices for unlicensed-care households were mailed from a wrong address list; noticed May 27, 2026 and disclosed May 28.
Unauthorised satsuki logins exposed 27,163 guest records, 111 directly affected partner records and 14,400 other partner records. Different categories are neither summed nor treated as people.
DB overload on May 25, 2026 led to confirmed intrusion; possible exfiltration of operator name, ID, password and email was disclosed May 28.
Possible data leak: Mail-server intrusion confirmed May 19, 2026 (first notice May 27). Final report found no clear theft evidence but could not rule out exposure of mail counterparts and a legacy EC database.
After vendor Medica Publishing’s ransomware event, the university disclosed on May 27, 2026 possible exposure of 105 2022 nursing seniors’ data.
A scholarship admin system launched April 20, 2026 allowed other schools to view awardee data via certain operations; noticed May 1 and disclosed May 27.
Possible data leak: Unauthorized access to web/mail servers confirmed May 1, 2026 (first notice May 27; final June 22). cPanel/WHM vulnerability yielded admin rights. Theft traces rated low but exposure cannot be ruled out.
A May 27, 2026 newsletter data-join flaw showed another customer’s name/nickname to some recipients. Address, phone, cards and test results were not confirmed leaked.
On May 19, 2026 from 09:00–09:27 a Google Form “show summary” setting let other applicants view responses; disclosed May 26.
On May 25, 2026 a staff PC was remotely controlled after a fake warning; possible exposure of stored faculty/student data was disclosed May 26.
On May 25, 2026 a shared-system status mail put partner addresses in To: instead of Bcc; disclosed May 26 (distinct from the Hokulink member incident).
A May 20, 2026 review found missing access controls on TDA portal personal-data areas and prior CSV downloads in logs; disclosed May 25.
On Nov 11, 2025 students viewed student-info materials a teacher left in a classroom after a meeting; after parent handling a May 22, 2026 press release followed (distinct from the Nishinari temporary-loss incident).
On May 22, 2026 an info-session mail was sent with addresses in To:, exposing prospect emails to each other.
After CAMPFIRE reported a server intrusion, the club warned on May 22, 2026 that parade-project supporter personal data may have leaked.
After ICC reported an intrusion affecting bulk-collection systems, the school told guardians on May 20, 2026 that bank-account fields may have been exposed.
Possible data leak: Vulnerability abuse on an attachment-separation mail server was recognised May 14, 2026 and disclosed May 19; the final report still found no confirmed theft but listed definitive at-risk fields.
The April 2026 municipal mishap list published May 15 includes a Child/Youth Bureau misdelivery of a status-subject list affecting 104 people.
On May 8, 2026 an open-course mailing-list notice was sent with addresses in To:; disclosed May 15.