Search incidents by company, country, industry, year and attack method. Review affected data, impact, verification status, company responses and sources.
On February 2, 2026, EP Wealth discovered unauthorised activity on its network involving one employee’s compromised credentials and terminated it within hours; the unauthorised party obtained copies of data, including from client relationship tools.
On August 23, 2025, the firm was advised of possible unauthorised access to its network; the investigation confirmed unauthorised access to a portion of the network on that day, followed by a review of the files there.
Tieu Dental became aware of unauthorised access to its network; the forensic investigation found the actor accessed the network between July 28 and 29, 2025, and personal and/or health information may have been accessed or acquired.
Possible data leak: Malicious code on the e-commerce site potentially captured card numbers, expiry dates and CVV codes for purchases from about March 12 to September 16, 2025.
On December 30, 2025, the firm discovered an unauthorised third party had accessed its network; the investigation found files were acquired from certain systems on December 25 and 26, 2025.
On December 12, 2025, CFPA learned that certain personal information had been inadvertently disclosed to an unknown third party that day; only individual broker information was affected, not policyholder data (except brokers who are also policyholders).
On January 21, 2026, an attack resulted in unauthorised read-only access to some backup systems, including limited access to users’ basic account details (metadata, contact details, usernames, dates of birth and names).
Investigation of an August 3, 2025 network disruption found an unknown actor accessed and acquired data.
On November 25, 2025, M&Y identified suspicious activity on a server used for historical record keeping; the investigation found an unknown actor viewed and downloaded files on or about November 23, 2025.
A document was intermixed with another claimant’s information and emailed to that claimant, disclosing name, Social Security number and work-injury medical information.
Exploitation of a then-unknown Oracle E-Business Suite vulnerability allowed a third party to access and obtain files from Maritz’s finance environment on August 10–13, 2025.
Possible data leak: Activity in the website environment from January 25 to 28, 2026 may have involved personal information.
On October 31, 2025, an unauthorised party accessed a third-party file-hosting system, affecting names, contact details and other fields.
An unauthorised person accessed data from the vendor-hosted Oracle E-Business Suite in August 2025; hiring and payment records included names and SSNs.
Network segments were accessed on August 22, 2025 and files were copied and potentially viewed.
An individual accessed the network from November 26 to December 4, 2025 and took copies of files that may contain names, SSNs and driver’s licence numbers.
Files on the network were viewed and copied by an unauthorised actor between August 8 and 14, 2025.
Possible data leak: Around August 14, 2025, Pyramid became aware of suspicious network activity, initially finding no indication data was affected; on September 30, 2025 it discovered data on its servers was impacted, and determined current and former employee data was likely affected.
Around December 3, 2025, EHG became aware of unauthorised activity in its cloud-based healthcare platform; preliminary investigation found evidence certain files may have been accessed by an unauthorised party.
Possible data leak: Around November 25, 2025, MEC discovered suspicious activity on its website; on November 26 it found an unauthorised party had added a script sending credit card data to a Google Analytics account it controlled.