
On Feb. 4, 2025, Heartland Health Center discovered it was the victim of a ransomware attack carried out by the MEDUSA group. The types of information exposed are extensive and include both personally identifiable information (PII) and protected health information (PHI) of at least 43,728 current and former patients across the U.S.
The attackers claimed responsibility on their dark web portal, stating they had obtained sensitive data and threatening to publish it within 11 to 12 days. Sample screenshots of the stolen data were also posted online. Notably, this is not the first time Heartland Health Center has been targeted, as it previously suffered a LockBit ransomware attack on May 9, 2024.
The compromised data may include: name, Social Security number, date of birth, driver license number, financial information, medical information, and health insurance information.
The severity of this breach is heightened by the nature of the information accessed. The exposure of PII and PHI creates a risk of identity theft, financial fraud and medical identity theft. The MEDUSA ransomware group’s involvement and their public threats to leak data further elevate concerns for those affected.
For more information, see the public notice posted by Heartland Health Center. Beginning on Oct. 17, 2025, data breach was also disclosed to the U.S. Department of Health and Human Services, and the Attorney Generals' offices in Massachusetts and Montana.
Upon discovering the unauthorized access, Heartland Health Center immediately engaged forensic consultants to investigate the incident, secure its systems and prevent further unauthorized access. The organization conducted a thorough review of the compromised files to determine the extent of sensitive information involved. By June 3, 2025, this review was completed, and affected individuals were identified.
Heartland Health Center has taken several steps to support those impacted:
Given the nature of the breach, it is strongly recommended that affected individuals:








.webp)
.webp)
.webp)

.webp)
.webp)
.webp)
.webp)