A threat actor claims to have breached Ridgecrest Regional Hospital in Ridgecrest, California, and to be releasing its full database, including patient identities, Social Security numbers, clinical records, billing data and staff files. The November 16, 2026 allegation comes a week after the hospital confirmed a cyber incident and took systems offline. The hospital has not confirmed that any patient or staff data was stolen or released.
Ridgecrest Regional Hospital is a non-profit, DNV-accredited critical access hospital in Ridgecrest, in Kern County’s Indian Wells Valley. Its about page describes a 25-bed acute care hospital, a 125-bed skilled nursing facility, clinics and other services, supported by more than 860 employees. The claim names the hospital’s public website, rrh.org. The same actor recently alleged a database leak at Medina Regional Hospital in Texas and a database leak at Spencer’s. The account registered in September 2026 and has limited posting history.
Hospital confirmed an incident, not a data leak
On November 9, 2026, the hospital issued a statement, published by the Ridgecrest Daily Independent, saying it “experienced a cyber incident on Nov. 9” and “proactively took systems offline in order to investigate the matter.” It described the event as “manageable” and said it would keep the community informed. Later hospital news releases, also carried by the newspaper, said phones were restored on November 10, clinics including urgent care remained open, and the lab draw station reopened by November 11. Those statements confirm a cyber incident and temporary disruptions. They do not confirm ransomware, a data theft, the claimed record counts or any public release of a database. The hospital’s own news pages did not contain a notice about a data incident at time of publication.
Record totals are not a patient count
The actor claims 35,437 unique Social Security numbers inside 84,559 person records, with 35,674 of those records said to carry a Social Security number, date of birth and sex. It also lists 199,170 patient records, 43,017 guarantors and 48,173 billing patients. Those figures come from the actor and are not verified. Many of the other totals describe table rows, such as billing, clinical or sensor entries, and must not be read as a count of affected people. The 199,170 patient records, and the 84,559 person records, are the closest figures the claim offers to a people count. The actor also claims 113,640 addresses, 148,897 phone numbers, 67,008 emergency contacts, 5,245 email addresses and 56 mailbox messages. It posted a purported sample of patient-record fields. BreachNews is not reproducing that material or any personal information from it.
Clinical, billing and staff data also claimed
Beyond identity and contact records, the actor claims a wide range of clinical, billing, visit and staff tables, including:
- Clinical records: 2,200,204 notes, 4,350,097 patient problem rows, 2,673,339 vital sign rows, 2,628,033 medication rows, which the actor described as legacy and SureScripts records, 225,701 immunizations, 106,381 family history rows, 25,604 allergies and 24,222 consents
- Billing and visits: 702,190 invoices, 713,896 insurance rows, 1,273,172 payments, 852,018 guarantor statements, 618,742 payment sources, 693,324 transactions, 1,452,569 billing patient-problem rows, 568,068 visits, 2,342,912 diagnoses, including 450,628 the actor described as ICD-10, 3,910 care-coordination rows and 15,879 records the actor labeled frequent flyers
- Staff, files and systems: 3,593 HR employee records, 986,968 payroll rows, 49,589 benefit enrollments, 33,363 security-person rows, 2,971 password rows, 517 portal users, and 423,383 files, including 98,577 described as patient files, 207,365 as staff files and 117,438 as financial or legal files, among them 251,882 PDFs, 37,558 images and 732 database exports, plus 13,869,550 temperature readings, 414,176 sensor summaries and 268,530 notification rows
None of these counts has been independently verified. The actor did not describe how access was supposedly obtained, when the intrusion allegedly occurred or whether a ransom was demanded. The post presents the material as a free release of a full database.
Why the alleged mix of data would be serious
If genuine, Social Security numbers, dates of birth and addresses would be highly useful for identity theft and tax or benefits fraud. Clinical notes, medications, allergies and related records would add protected health information that can support targeted medical or insurance scams. HR, payroll and benefits data could expose employee details, while password rows and portal user records could help an attacker impersonate staff or patients if those credentials are valid. The claim does not establish whether the password rows are hashed, encrypted or stored in plaintext.
People who have been patients at Ridgecrest Regional Hospital or its clinics can watch for phishing and unexpected calls that reference real appointments, bills or medical details. Those steps are precautions and do not confirm that any particular person’s data was taken. Guidance is in the BreachNews guide What to Do If Your Medical Information Was Exposed in a Data Breach.
No confirmation of a data theft so far
No listing matching this data-release claim was identified in the U.S. Department of Health and Human Services Office for Civil Rights breach report or in the California attorney general’s published data-breach notices in the sources reviewed. Readers can track reported U.S. healthcare incidents in the BreachNews HIPAA breach tracker.
The hospital has previously notified patients about a separate incident. In 2024, it said a ransomware attack on its billing vendor, Designed Receivable Solutions Inc., may have exposed patient names, dates of birth, Social Security numbers and billing details. In a later FAQ, the hospital said that vendor incident did not involve its electronic medical records or networks. That earlier breach does not confirm the new allegation. The alleged access method, timing, authenticity and scope of the data-release claim remain unresolved. Because the account behind the claim is relatively new and has a limited history, the figures should be treated with particular caution until the hospital, regulators or another independent source confirm whether any data was taken or released.












