Get started

Data breach, reported Aug 12, 2025

Whitfield Regional Hospital data breach

Tombigbee Healthcare Authority, doing business as Whitfield Regional Hospital, reported a breach of patient health information to the HHS Office for Civil Rights on Aug 12, 2025. HHS lists 58,081 people affected and describes the breach as a hacking or IT incident involving a network server. The hospital is listed as an Alabama healthcare provider.

Reported
Aug 12, 2025
People affected
58,081

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

Tombigbee Healthcare Authority, which HHS lists as doing business as Whitfield Regional Hospital, submitted a breach report to the HHS Office for Civil Rights on August 12, 2025. HHS lists it as a healthcare provider in Alabama 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 say how the incident happened or when it started. Claim did not find a notice from the hospital filed with a state attorney general or a hospital website notice in the sources it reviewed.

What information was exposed

The HHS portal lists breaches of unsecured protected health information affecting 500 or more people. That kind of information can include patient names, addresses, dates of birth, medical record numbers, diagnoses, treatment details and health insurance information. HHS does not publish which items were involved in this breach. Patients who were affected should receive a letter from the hospital that lists the items for them.

Who was notified

HHS lists 58,081 individuals affected. Claim did not find this breach on the California, Oregon, Texas, Washington, Delaware, Indiana or Vermont lists it reads, so Claim does not have state by state counts or a sample letter.

What the hospital is offering

The HHS report does not say whether Whitfield Regional Hospital 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 Whitfield Regional Hospital or Tombigbee Healthcare Authority and enroll in any monitoring it offers.
  • Read the explanation of benefits statements from your health plan, including Medicare or Medicaid, and report care you did not receive.
  • Ask the hospital for a copy of your records if you think someone used your identity for care.
  • If your letter lists your Social Security number, place a free credit freeze with Equifax, Experian and TransUnion.
  • Report identity theft at IdentityTheft.gov.

Lawsuits and settlements

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

Frequently asked questions

Is the Whitfield Regional Hospital data breach real?

Yes. Tombigbee Healthcare Authority, doing business as Whitfield Regional Hospital, reported it to the HHS Office for Civil Rights on Aug 12, 2025, and HHS lists it on its public breach portal.

Was I affected?

HHS lists 58,081 people but does not name them. Patients whose information was involved should receive a letter from the hospital.

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