Suchen Sie nach Unternehmen, Land, Branche, Jahr und Angriffsmethode. Prüfen Sie betroffene Daten, Umfang, Bestätigungsstatus, Maßnahmen und Quellen.
Between January 2024 and May 2025, a County employee accessed personal information in electronic systems without a legitimate business reason, including names, case and CIN numbers, dates of birth, SSNs and public assistance benefit information.
Unauthorised access on April 9, 2026 resulted in files containing patient information being acquired. The notice posted June 11 (St. Mary’s patients) states acquisition; the notices posted July 29 say files may have been taken.
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.
An unauthorised actor accessed systems and servers between May 14 and 18, 2025 and removed stored information.
Suspicious activity was found around March 27, 2026; on May 1 the investigation found an unauthorised individual briefly accessed the network and may have accessed files.
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.
Possible data leak: An actor gained access via credential compromise around February 12, 2025; systems held names, addresses, dates of birth, SSNs and licence details. The college says there is no evidence data was removed.
Around February 17, 2026, one employee’s computer was accessed without authorisation; names, addresses, SSNs, dates of birth and licence or ID numbers may have been obtained.
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.
An unauthorised party accessed and copied certain files after unauthorised activity beginning around April 24, 2026.
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.
Files containing personal information may have been acquired by an unauthorised individual who accessed the network around December 25–26, 2025.
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.