
Following claims on the dark web, Cameron Regional Medical Center confirmed that it was the victim of a ransomware attack. The hospital discovered the breach on June 18, 2026.
On Aug. 3, 2026, a ransomware group known as Anubis claimed responsibility for the attack in a posting on the Tor network, a part of the dark web. The group claimed to have obtained a wide range of data from the hospital.
The compromised data reportedly includes patient records, internal investigations, HIPAA-related documents, employee information, medical records, operational documents and other sensitive healthcare information.
Anubis stated it intended to publish the stolen data within six days of its posting. The group's claims, if accurate, suggest the scope of the breach extends beyond patient records to include employee data and internal hospital documents.
The hospital's own investigation into the breach remains ongoing.
The types of personally identifiable information (PII) potentially exposed include patient names, addresses, dates of birth, Social Security numbers, driver's license numbers, financial account information, electronic or digital signatures and employer-assigned identification numbers.
Protected health information (PHI) potentially exposed include medical diagnosis and treatment information, dates of medical treatment, medical provider names, patient identification numbers, agency-assigned identification numbers, treatment cost information and health insurance information.
A total of 5,468 individuals were affected. The hospital posted a notice about the data incident, and affected individuals will receive written notification via U.S. Mail. The breach was reported to the U.S. Department of Health and Human Services on Sept. 18, 2026.
Cameron Regional Medical Center set up an Incident Response Team to answer questions about the incident. Individuals who have questions can call the team at 816-614-1141 or write to 1600 E. Evergreen St., Cameron, MO 64429.
Cameron Regional Medical Center encouraged potentially affected individuals to remain vigilant by reviewing their account statements, credit reports and explanations of benefits for any unusual activity.








.webp)
.webp)
.webp)

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