Suchen Sie nach Unternehmen, Land, Branche, Jahr und Angriffsmethode. Prüfen Sie betroffene Daten, Umfang, Bestätigungsstatus, Maßnahmen und Quellen.
Possible data leak: An unauthorised party accessed the network for two days in late May 2025; the hospital believes files were acquired from part of the network but found no definitive proof that files with personal or health information were taken.
Possible ransomware infection found July 8, 2026 with immediate server shutdown; first notice July 14. September 8 follow-up disclosed possible personal-data exfiltration and began individual notices.
Certain files were accessed and acquired without authorisation on April 4, 2026.
System outage and server cyberattack confirmed July 13, 2026 (first notice), affecting cold warehouses and frozen-food shipping. Seventh notice (Sep 18) confirmed personal-data leakage. disclosedOn stays the first notice date.
Possible data leak: First notice Jul 13, 2026 reported ransomware on some servers. Second notice (Sep 30) details Jul 8 intrusion / Jul 10 encryption of files including current/former students, applicants, guardians, staff and retirees. No clear exfiltration traces, but log deletion prevents fully ruling out leakage. No count. First disclosure remains Jul 13.
Possible data leak: Nippon TeleNet, which handled fax sending in 2014, was attacked on March 9, 2026; on June 19 it told Lind that 2014-provided customer data remained in the hit environment. Disclosed July 13. Vendor investigation has not confirmed exfiltration.
Possible data leak: Unusual network activity on June 5, 2026 means employee personal information could have been accessed or downloaded.
On April 14, 2026 Osaka Prefectural Kogei HS (full-time) found a CD of FY2025 student ID-photo data missing; it was not recovered. Checkout log rules had not been followed. Prefecture press release July 10.
Possible data leak: Vendor Nostrum’s SMART SPI server was intruded, encrypted and backdoored on April 17, 2026; outage noticed April 19. No direct theft evidence, but a leak-site posting threat means exposure cannot be ruled out; disclosed July 9.
On July 2, 2026 the moving CRM database was deleted after unauthorized access. Attackers demanded crypto and claimed they would publish data; technical confirmation of exfiltration was not possible; disclosed July 9. PPC and police notified July 8.
Possible data leak: Third-party intrusion into the official online shop was found; fearing partial personal-data exposure, card payments were paused and an external investigation begun. Details still unknown; a later update also paused direct sales.
Unauthorised access to information on the network occurred between February 3 and 6, 2026; review of the potentially affected data is ongoing.
Around 15:00 on July 1, 2026 a vendor mis-sent emails to some GR Yaris special-edition lottery applicants containing another waitlisted person’s name and related fields; disclosed July 8. Winners’ data out of scope.
Possible data leak: On June 26, 2026 a faculty member clicked a scam site while working at home and allowed remote access. The PC held names/addresses of students, faculty and society members; disclosed July 8. Forensics planned; no harm confirmed yet.
On June 18, 2026 staff mis-attached a file with non-shareable personal data to a customer-opinion email for agencies. After a recipient report and follow-up checks, three agencies were affected; disclosed July 7. Deletion at recipients confirmed.
July 7, 2026 first notice said the firm was investigating press reports. September 14 follow-up confirmed a Tama-branch ex-agent had taken customer forms while employed and lost them after leaving in March 2026; discovered via a June finder report. Forms recovered.
Possible data leak: Vendor reported management-server intrusion on June 30, 2026; first notice July 7. Second notice found brute-force admin login and download of inquiry-mail bodies from before June 29, 2026.
On June 25, 2026 staff found names/lot numbers in published bid drawings; posting paused July 2; first notice July 6. July 24 results finalized people counts for bid drawings and public-works evaluation sheets. No secondary harm found.
Possible data leak: On July 6, 2026 IPSJ disclosed that some young-researchers’ personal data remained technically viewable via lingering ex-officer access and unrevoked sharing links from accounting work; access has been closed and individuals notified.
Server intrusion noticed April 28, 2026; possible personal-data exposure found June 19; first notice July 3. Second notice cites possible theft/misuse of an auth-federation account.