All Breaches
August 8, 2025 Verified Sensitive Record Business Services

Mazzola Mardon Data Breach

The 2025 Mazzola Mardon data breach affected 2,123 people according to the HHS record. The incident involved information belonging to members of the Management-ILA Managed Health Care Trust Fund, which the law firm served.

2.1 Thousand
Affected People
14
Data Types
Low
Severity
Oct 9, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

7 sensitive14

About This Breach

Mazzola Mardon is a New York law firm that provides legal services to labor unions and pension, health, and welfare benefit funds.

How Did the Incident Occur?

According to the publicly reported incident summary, unusual activity on the firm's network was investigated and an unauthorized person was found to have accessed the network and downloaded files on August 8, 2025. The review of the affected files was completed on January 27, 2026, and individual notices were mailed on March 23, 2026.

What Information Was Affected?

The information varied by person. The disclosed scope includes names, addresses, dates of birth, Social Security numbers, driver's license or state identification numbers, and financial-account information. Mental or physical conditions, diagnoses and treatment, dates of service, provider names, procedure types, prescriptions, medical record numbers, Medicare identifiers, health-insurance information, and billing or claim information may also have been involved.

How Did Mazzola Mardon Respond?

The firm said it mailed notices to affected people and was reviewing and strengthening its cybersecurity practices to help prevent similar incidents. The HHS record classifies the event as a hacking or IT incident involving a network server.

What Should Affected People Do?

Notice recipients should review credit reports and financial accounts for transactions they do not recognize and examine health-insurance explanations of benefits, medical bills, and records for services they did not receive. They should contact the relevant financial institution, health insurer, or healthcare provider directly if they find a suspicious entry.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information