Get started

Data breach, reported Jun 26, 2025

Local 342 Health Care Fund data breach

The Amalgamated Meat Cutters and Retail Food Store Employees Union Local 342 Health Care Fund, a New York health plan, reported a breach of health information to the HHS Office for Civil Rights on Jun 26, 2025. HHS lists 56,615 people affected and describes the breach as a hacking or IT incident involving a network server.

Reported
Jun 26, 2025
People affected
56,615

Key facts

Data exposed
Protected health information (HHS does not list the specific items)
States notified
Reported to HHS
Notice letter
Not published by HHS

What happened

The Amalgamated Meat Cutters and Retail Food Store Employees Union Local 342 Health Care Fund submitted a breach report to the HHS Office for Civil Rights on June 26, 2025. HHS lists the fund as a health plan in New York and says no business associate (an outside vendor) was involved.

The report classifies the breach as a hacking or IT incident, with the information held on a network server. The HHS listing does not describe how the incident happened or when it started. Claim did not find a notice letter from the fund in the sources it reviewed.

What information was exposed

HHS posts breaches of unsecured protected health information that affect 500 or more people. For a health plan, that can include member names, addresses, dates of birth, member ID numbers, Social Security numbers, claims and benefits information. HHS does not publish which items were involved in this breach. Members who were affected should receive a letter that lists the items for them.

Who was notified

HHS lists 56,615 individuals affected. The Indiana Attorney General's 2026 report lists a filing by "UFCW Local 342 et al" on March 9, 2026 with the same total, 56,615 people, and a breach date of April 25, 2025. Claim has not confirmed whether the two reports describe the same incident. That filing has its own page on this site. Claim did not find this breach on the other state lists it reads.

What the fund is offering

The HHS report does not say whether the fund is offering credit monitoring or identity protection. If you receive a letter, it should describe any offer, an enrollment deadline and a phone number for questions.

What to do now

  • Watch for a letter from the Local 342 Health Care Fund and enroll in any monitoring it offers.
  • Read the explanation of benefits statements from the fund and report any claim for care you did not receive.
  • If your letter lists your Social Security number, place a free credit freeze with Equifax, Experian and TransUnion and ask the IRS for an Identity Protection PIN.
  • Be careful with calls or emails about your union benefits that ask for personal or payment details. Call the fund at a number you already have.
  • Report identity theft at IdentityTheft.gov.

Lawsuits and settlements

As of November 16, 2026, Claim has not found an announced settlement for this breach in the sources it reviewed. Claim tracks new data breach settlements and lists them when they open.

Frequently asked questions

Is the Local 342 Health Care Fund data breach real?

Yes. The fund reported it to the HHS Office for Civil Rights on Jun 26, 2025, and HHS lists it on its public breach portal under the fund's full name.

Was I affected?

HHS lists 56,615 people but does not name them. Members whose information was involved should receive a letter from the fund.

Will there be a settlement?

No settlement had been announced as of Nov 16, 2026, in the sources Claim reviewed. Claim tracks new data breach settlements and lists them when they open.

What should I do if my Social Security number was exposed?

Freeze your credit at Equifax, Experian and TransUnion, which is free, and request an IRS Identity Protection PIN. Check your credit reports at annualcreditreport.com and report identity theft at IdentityTheft.gov.

Claim finds settlements you qualify for and helps you file.

Get alerts if a settlement opens

Related pages

Last updated Nov 17, 2026 by Dev Dixit, Head of Media at Claim. Claim works to keep these details accurate. If this page differs from an official source, the official source is correct.

Claim is not a law firm, a court, a government agency, or a settlement administrator, and does not give legal advice.

This page is a plain language summary, not legal advice, and does not create an attorney client relationship.

Company names are trademarks of their owners. Claim uses them only to identify the matter described on this page and is not affiliated with those companies.

Read our full disclaimer