Healthcare Sector Disclosed 100 Ransomware Attacks in Q3 – The HIPAA Journal
Healthcare Sector Disclosed 100 Ransomware Attacks in Q3
Ransomware groups are running riot, with 353 disclosed attacks in Q3 2026 and 2,668 undisclosed attacks, an increase of 20% in disclosed attacks and an increase of 77% in undisclosed attacks from Q3 2025, according to the Q3 2026 State of Ransomware Report from BlackFog. More attacks were disclosed in Q3 2026 than in any other quarter since BlackFog began tracking ransomware attacks in 2020, and each month in Q3 had more disclosed attacks than any Q3 month in previous years.
Across all industry sectors, there were 123 disclosed attacks in July, 116 in August, and 114 in September. Healthcare topped the list with 100 disclosed attacks in the quarter, followed by government (41), services (38), Technology (30), and manufacturing (28).
Disclosed attacks only account for a small percentage of total attacks. Factor in claims of attacks on data leak sites, and the picture changes considerably. For undisclosed attacks, services topped the list (575 claimed attacks), followed by manufacturing (548), and technology (294), with healthcare in fourth spot with 239 claimed attacks. Combined, that places healthcare in third place with 339 attacks in the quarter.
Out of all disclosed attacks, 98% involved data exfiltration, and in one-third of attacks the group responsible could not be determined. The biggest ransom demand – $13 million – came from the ShinyHunters attack on the U.S. data center operator CyrusOne, with an average ransom demand across Q3 of $763,253. BlackFog reports that, on average, 697 GB of data was exfiltrated per victim, with the most common payment deadline of just 3 days.
Data exfiltration occurs in the vast majority of attacks, and since data breaches require individual notifications in healthcare under the Health Insurance Portability and Accountability Act, victims of healthcare ransomware attacks should be informed if their data is stolen, but that’s certainly not the case with other sectors. Across all sectors, only 1 in 9 ransomware attacks is publicly disclosed. For most victims, they are not notified, there is no announcement, and they may be totally unaware that their data has been leaked on a dark web data leak site.
In terms of confirmed data breaches, the ransomware attack on Saber Healthcare Group was the most impactful of the quarter, involving the personal and health information of a confirmed 282,727 individuals. Saber Healthcare did not disclose the group responsible, and it was not added to any data leak site, which could indicate that the ransom was paid.
In Q3, there were 116 active ransomware groups, with 21 new ransomware groups emerging, although two groups dominate the ransomware landscape – The Gentlemen and Qilin. BlackFog reports that both groups tied with 347 entries each on data leak sites in Q3. The Gentlemen operation has rapidly scaled, with a massive increase in attacks, helped by the group’s ability to attract new affiliates with a 90% share of ransoms paid, compared to a more typical 70-80% by other groups, and a full attack toolkit available to affiliates. The two groups accounted for 26% of all leak site activity in the quarter. The United States remained the most targeted country, accounting for 53% of disclosed attacks and 39% of undisclosed attacks.
The post Healthcare Sector Disclosed 100 Ransomware Attacks in Q3 appeared first on The HIPAA Journal.
6 Medical Practice Compliance Risks to Avoid In 2027 – Medscape
Access Dental Management Breach Affects Over 341,000 Individuals
A data breach at Access Dental Management has affected more than 341,000 individuals in Texas. Monadnock Community Hospital is investigating a cybersecurity-related outage, and data breaches have been confirmed by Valley Family Health Care and Ochsner Health.
Access Dental Management
Access Dental Management LLC, a dental management company based in Irving, Dallas, has notified the Texas Attorney General about a significant data breach that has affected 341,039 individuals in Texas. Access Dental Management provides services in multiple U.S. states. It is currently unclear how many individuals have been affected in total. Based on the filing, the information potentially involved includes names, addresses, birth dates, Social Security numbers, health records, medical information, and health insurance information. Notification letters have been mailed to the affected individuals; however, the HIPAA Journal has been unable to find a copy of the breach notice.
A ransomware/data extortion group called Worldleaks claimed responsibility for an attack on Access Dental Management in June 2026 and claimed to have exfiltrated files containing patient data. A threat was issued to publish the stolen data if a ransom was not paid.
Monadnock Community Hospital
Monadnock Community Hospital, a critical access hospital in Peterborough, New Hampshire, has experienced an outage affecting its network and phone system. The server outage started on November 9, and in a November 19, 2026, website notice, the hospital explained that it is continuing to deal with the incident and that the disruption continues. Without access to key systems, the decision was taken to cancel certain elective surgeries out of patient safety concerns, although certain minor procedures have continued as scheduled. While its Emergency Department remains open, ambulances were placed on diversion, and as of November 19, 2026, the diversion remains in place. Clinician offices are open and continue to see patients, and rehabilitation and physical therapy appointments are continuing as scheduled.
While the hospital and practice phone lines are operational, phone issues are still being experienced at its Jaffrey and Antrim offices, and the hospital confirmed that outpatient radiology services, outpatient lab testing, scheduling for radiology and laboratory appointments, and its fax service remain temporarily unavailable and that is likely to remain the case until Monday, November 23, 2026. It has yet to be determined if any patient data has been stolen in the incident. Notifications will be issued in due course should that turn out to be the case.
Valley Family Health Care
Valley Family Health Care, Inc., a Payette, Idaho-based healthcare provider with multiple clinics in eastern Oregon and southwestern Idaho, has started issuing notifications about a cybersecurity incident earlier this year. According to its notification letters, a network disruption was experienced on March 13, 2026. Steps were taken to secure its systems, and an investigation determined that an unauthorized third party accessed its network and may have viewed or obtained files containing patient information. The file review process was formally completed on October 9, 2026, and individual notification letters were mailed in November.
The types of information involved vary from individual to individual and may include names in combination with Social Security numbers, driver’s license/state identification numbers, dates of birth, financial account information, medical information, and/or health insurance information. Valley Family Health Care has taken steps to enhance security and reduce the risk of similar incidents in the future. Complimentary credit monitoring services have been made available to certain individuals. No ransomware group appears to have claimed responsibility for the attack, and the incident is not yet shown on the HHS’ Office for Civil Rights breach portal, so it is currently unclear how many individuals have been affected.
Ochsner Health
Ochsner Health, a nonprofit Louisiana-based health system serving the New Orleans metropolitan area, has identified unauthorized access to two user accounts. While it is unclear from the breach notice exactly when the unauthorized access was detected, the health system said its investigation confirmed that the accounts were accessed by an unauthorized third party between September 18, 2026, and September 21, 2026.
A third-party digital forensics team was engaged to assist with the investigation and confirmed on October 1, 2026, that patient data had been exposed and potentially copied. The accounts were reviewed, and on November 18, 2026, it was confirmed that the impacted information included names, demographic information, Social Security numbers, and health information, although the data review is continuing to determine the full extent of data exposure.
Notification letters will be mailed to the affected individuals when the review is completed. Additional steps have been taken to better safeguard patient data, and Ochsner Health will continue to evaluate opportunities to further enhance data security. The incident is not yet shown on the HHS’ Office for Civil Rights breach portal, so it is currently unclear how many individuals have been affected.
The post Access Dental Management Breach Affects Over 341,000 Individuals appeared first on The HIPAA Journal.
Vulnerabilities OFFIS DCMTK Toolkit Can Result in Data Deletion – The HIPAA Journal
Vulnerabilities OFFIS DCMTK Toolkit Can Result in Data Deletion
Two more vulnerabilities have been identified in the OFFIS DCMTK toolkit that could result in the deletion of medical imaging data. The most serious vulnerability is tracked as CVE-2026-125130 and has a CVSS v3.1 severity score of 9.1. The vulnerability is due to a read-only archive area accepting network stores. Each unauthorized store can trigger the archive’s own quota cleanup, which would delete existing studies, potentially resulting in total data deletion from the archive. The vulnerability can be exploited by a network peer without credentials.
The vulnerabilities were identified by security researcher Abhinav Agarwal, who demonstrated in tests on DCMTK 3.7.0 that the server accepted 200 unauthorized stores, triggering the archive cleanup resulting in the deletion of 200 original synthetic image files. The final query confirmed that all 200 original image files had been deleted. Agarwal determined that while DCMTK enforced read-only access, that only occurred when a connection was set up. “If a peer asked to use the storage service on a read-only area, the server refused. It still accepted the Verification service (DICOM “echo”), which is harmless by itself,” explained Agarwal. “Once connected, however, the server executed whatever command arrived without checking that it matched the service negotiated for that connection. A peer could negotiate Verification only and then send storage commands over it.” Data deletion occurs when the read-only area is full, resulting in the deletion of the least recent imaging data to provide space for the most recent store.
The second vulnerability is tracked as CVE-2026-126500 and has a CVSS v3.1 score of 5.9 (medium severity). The vulnerability is due to the cleanup process deleting studies by prefix, rather than using exact matching. “To evict a study, cleanup picks the oldest one, then deletes every index record whose Study Instance UID starts with the selected UID,” said Agarwal. “Study selection elsewhere in the same backend uses exact matching. Cleanup did not.”
Agarwal demonstrated in tests that evicting the study ending .1 also deleted the studies ending .10–.19 and .100–.199 – resulting in 111 studies deleted in a single eviction. Data deletion could occur without any attacker involvement and could result in data loss from unrelated studies. Agarwal also uncovered five unrelated vulnerabilities in the same toolkit earlier this year, which have since been fixed. The latest two vulnerabilities were reported to the developer and CISA and affect versions 3.5.4 to 3.7.0. The developer fixed both vulnerabilities in DCMTK version 3.7.1, which was released on October 15, 2026.
While the new version fixes the vulnerabilities, they may still be present in products that incorporate the DCMTK archive server, including certain Debian, Ubuntu, and Fedora package sources. “An SBOM line that says ‘DCMTK’ doesn’t answer the question. Hospitals and suppliers need to know whether the archive server or its backend is in the build, which revision it came from, and whether both fixes made it downstream”, said Agarwal.”
The post Vulnerabilities OFFIS DCMTK Toolkit Can Result in Data Deletion appeared first on The HIPAA Journal.
Yuma Regional Medical Center Pays $1,985,000 to Settle Data Breach Lawsuit
Yuma Regional Medical Center, a 406-bed general and teaching hospital in Yuma, Arizona, that now operates as Onvida Health, has agreed to settle class action litigation stemming from an April 2022 cybersecurity incident. Hackers accessed its computer systems between April 21, 2022, and April 25, 2022, and used ransomware to encrypt files. Prior to encryption, the ransomware group exfiltrated files containing patient information, including names, Social Security numbers, health insurance information, and limited medical information. The data breach was reported to the HHS’ Office for Civil Rights as involving the protected health information of 738,145 individuals. Court documents suggest that notification letters were mailed to 720,217 current and former patients.
Multiple class action lawsuits were filed in response to the data breach. The lawsuits asserted similar claims and were consolidated into a single complaint with 13 named plaintiffs. The consolidated lawsuit – Dillon Clarke, et al. v. Yuma Regional Medical Center – is pending in the United States District Court for the District of Arizona. The consolidated complaint alleges Yuma Regional Medical Center was at fault for the data breach, as it failed to ensure the privacy and security of data in its possession. The lawsuit claimed it failed to implement appropriate cybersecurity measures, failed to detect the incident until the attackers made contact and explained that data had been stolen, and then failed to issue timely notification letters to the affected individuals.
The lawsuit asserted claims for negligence, breach of implied contract/implied duty of good faith and fair dealing, unjust enrichment, breach of fiduciary duty, and violation of the Arizona Consumer Fraud Act. Yuma Regional Medical Center denies the claims and contentions in the lawsuit, including the allegations of wrongdoing and liability. During mediation, all parties were able to reach an agreement on suitable settlement terms, thereby avoiding the cost of continued litigation and the risks associated with a trial and related appeals. Under the terms of the settlement, Yuma Regional Medical Center has agreed to establish a $1,985,000 settlement fund to pay benefits to class members after attorneys’ fees and expenses, settlement administration costs, and service awards for the class representatives have been deducted.
Class members may submit a claim for reimbursement of documented, unreimbursed out-of-pocket losses incurred due to the data breach between April 21, 2022, and February 1, 2027, up to a maximum of $4,000 per class member. In addition, class members are entitled to claim a pro rata cash payment, which will be paid from the remaining settlement funds. The amount will be determined by the number of claims received. All class members will also automatically receive one year of medical data monitoring services. Yuma Regional Medical Center has already invested, or will invest more than $750,000 in data security measures to better protect patient data. Individuals wishing to opt out of the settlement must do so by January 4, 2026. Objections must be filed by the same date, and claims must be submitted by February 1, 2027. The final fairness hearing has been scheduled for March 1, 2027.
The post Yuma Regional Medical Center Pays $1,985,000 to Settle Data Breach Lawsuit appeared first on The HIPAA Journal.
OCR Says Most Practices Fail the Security Risk Analysis. Here’s How to Make Yours Easy
When the HHS Office for Civil Rights (OCR) investigates a healthcare provider, one of the first documents it asks to see is the Security Risk Analysis. For most practices, that is where the trouble starts.
At OCR’s cybersecurity conference earlier this year, senior OCR officials returned to the same point again and again: most organizations they investigate cannot provide a compliant risk analysis. [Insert attributed quote: speaker name, title, exact wording]. In OCR’s view, a practice without an accurate and thorough risk analysis cannot be HIPAA compliant, because every other security decision depends on it.
This is not a new problem, and it is not limited to large health systems. The good news is that a compliant risk analysis does not need to be a burden on a busy practice. This article explains what the Security Risk Analysis is, what OCR expects to see, why so many practices fall short, and how to complete yours quickly with the right tool.
What OCR found when it looked
The clearest evidence comes from OCR’s own audit program. In 2016 and 2017, OCR audited 166 HIPAA-covered entities and 41 business associates. Its industry report found that only 14% of covered entities had substantially fulfilled the requirement to conduct an accurate and thorough risk analysis. Put another way, 86% fell short.
The results for the next step were worse. Only 6% of covered entities adequately implemented risk management, which is the process of acting on what the risk analysis finds.
Those audits are several years old, but OCR’s comments this year suggest little has changed. The risk analysis remains the most commonly cited failure in OCR’s enforcement actions, and OCR has built a dedicated enforcement program around it.
Why the Security Risk Analysis is the foundation of HIPAA compliance
The HIPAA Security Rule requires covered entities to “conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability” of the electronic protected health information (ePHI) they hold (45 CFR 164.308(a)(1)(ii)(A)).
The Security Rule is deliberately flexible. It does not tell a three-doctor family practice to use the same safeguards as a 500-bed hospital. Instead, it asks each organization to decide which safeguards are “reasonable and appropriate” for its own size, systems and risks. That flexibility only works if you know what your risks are.
That is why the risk analysis comes first. It tells you:
- Where ePHI lives in your practice, and who and what can access it.
- Which threats are realistic for you, from phishing and ransomware to a lost laptop or an unlocked records room.
- Which of your current safeguards are working, and where the gaps are.
- Which risks matter most, so you spend time and money in the right places.
Your policies, staff training, access controls, backup plans and vendor agreements should all follow from it. Without a risk analysis, a practice is making security decisions without a map.
What an “accurate and thorough” risk analysis covers
OCR’s guidance on risk analysis sets out what it expects to see. A compliant SRA should:
Cover all ePHI, wherever it is created, received, stored or sent: your EHR, practice management system, email, laptops, phones, tablets, backups, cloud services and systems run by vendors.
Identify realistic threats and vulnerabilities, including human error, cyberattacks, equipment failure and natural events.
Assess your current security measures and whether they are being used properly.
Estimate the likelihood and impact of each threat, and assign a risk level.
Be documented, with the analysis kept for at least six years.
Be reviewed and updated regularly, and whenever something significant changes, such as a new EHR, a new location or a security incident.
It also needs to look across the three types of safeguard in the Security Rule:
Safeguard Examples of what the SRA looks at
Administrative Security officer responsibilities, staff training, access approval, sanctions policy, incident response, contingency planning, business associate agreements
Physical Facility access, workstation placement and use, device and media disposal, protection of servers and paper records
Technical Unique user logins, automatic logoff, encryption, audit logs, multi-factor authentication, secure email and messaging, backups
A generic template downloaded from the internet rarely meets this standard, because it does not describe your practice, your systems or your risks. OCR has made clear that a “check the box” document is not an accurate and thorough analysis.
The cost of getting it wrong
In 2024, OCR launched its Risk Analysis Initiative, an enforcement program aimed specifically at organizations that have not carried out a compliant risk analysis. By July 2026, it had produced 14 enforcement actions, and risk analysis failures also feature in many of OCR’s ransomware settlements.
Recent examples show that size is no protection:
Top of the World Ranch Treatment Center agreed to pay $103,000 and adopt a two-year corrective action plan after a phishing attack exposed the ePHI of 1,980 people. OCR found the organization had not conducted an accurate and thorough risk analysis.
BST & Co. CPAs, an accounting firm acting as a business associate, paid $175,000 after a ransomware attack. Again, OCR cited the failure to conduct a risk analysis.
Financial penalties are only part of the cost. Corrective action plans typically last two years and require the organization to complete a risk analysis, put a risk management plan in place, update policies and train staff, all under OCR monitoring. That work has to be done anyway. Doing it before an investigation is far cheaper and less disruptive than doing it after one.
The post OCR Says Most Practices Fail the Security Risk Analysis. Here’s How to Make Yours Easy appeared first on The HIPAA Journal.

