Search incidents by company, country, industry, year and attack method. Review affected data, impact, verification status, company responses and sources.
An unauthorised actor accessed Kaplan’s servers between October 30 and November 18, 2025 and took certain files; on February 21, 2026 Kaplan determined the files contained names, SSNs and/or driver’s licence numbers.
On January 7, 2026, OpenLoop learned that an unauthorised third party had gained access to certain systems and removed certain information; the access occurred from January 7 to 8, 2026.
In January 2026, RMS detected unusual activity in its email environment; a single email account was intermittently accessed without authorisation between November 24, 2025 and January 7, 2026, and information in it may have been accessed.
Possible data leak: Information may have been copied by an unauthorised individual in a December 2025 incident.
On December 19, 2025, the office detected unauthorised access to its network; some files may have been accessed or removed between December 18 and 19, 2025, and on February 19, 2026 they were found to possibly contain personal information.
Possible data leak: Health Gorilla, an HIE member, requested patient information citing treatment, but the HIE could not confirm the recipients were authorised; health information may have been disclosed without authorisation.
A previously unknown Oracle E-Business Suite vulnerability was exploited and files were obtained from Hypertherm’s EBS application in August 2025.
Possible data leak: Systems were accessed January 5–6, 2026 and files were likely copied.
An unauthorised actor accessed the network October 12–26, 2025 and copied files that may include names, SSNs and financial-account information.
Data was acquired without authorisation in an incident on or about December 18, 2025.
Unauthorised network access on or about February 18, 2026 affected files containing personal information.
After becoming aware of suspicious activity in its network, OSI found that certain files may have been accessed without authorisation; it completed its review of the affected files on February 10, 2026.
On January 23, 2026, personally identifiable information was inadvertently disclosed to a third party by email.
Possible data leak: An unauthorised user potentially accessed systems; names and SSNs may have been affected.
Possible data leak: Information on systems may have been viewed or taken without authorisation on August 4, 2025.
On January 29, 2026, a MetLife associate inadvertently emailed a file to a human resources administrator at another MetLife group customer; the recipient notified MetLife the same day and confirmed deletion.
Vendor DanubeNet, Inc. (Driving School Solutions), a driving-school management software provider, had unauthorised access to records between July 10 and August 19, 2025; the club learned of it on December 22, 2025 and identified records with names and driver’s permit/licence numbers.
Possible data leak: In late February 2026, the firm’s 2025 client data environment was affected by a breach; the investigation identified 13 clients whose information was used to file fraudulent tax returns, which were blocked by the IRS and California Franchise Tax Board.
Possible data leak: A limited subset of files on a service provider’s system may have been accessed or acquired between April 17 and 22, 2025.
Possible data leak: An employee email account was accessed October 23–30, 2025; personal information in it may have been exposed.