News
Amazon's One Medical Seniors Hit by ShinyHunters Extortion Group: 8.8TB of Legacy Patient Data at Risk · Data BreachOpenLoop Health Telehealth Infrastructure Vendor Breach Exposes Patient Data Across Multiple Digital Health Clients · Data BreachHealthcare AI Vendor Xsolis Breach Exposes 1.4 Million Records Across Seven Hospital Systems Including Mayo Clinic · Data BreachHHS Breach Portal Backlog: OCR Still Adding March 2026 Breaches in Late June — What the Delay Means for Compliance Teams · AnalysisKettering Health Refused to Pay the Ransom. The Data Leaked Anyway: What 1.7 Million Exposed Records Teach About Ransomware and HIPAA · Data BreachOCR Settles Ransomware Investigation with Employer-Sponsored Health Plan for $450,000 · OCR EnforcementWhy a Third of Healthcare Breaches Now Trace Back to a Vendor: A Mid-Year 2026 Analysis · AnalysisFrom 4 Million to 60+ Million: The Conduent Breach Shows How Far Third-Party Risk Reaches · Data BreachNYC Health + Hospitals Breach: 1.8 Million Records Exposed via Third-Party Vendor, Including Biometric Data · Data BreachWhen Your Vendor Is the Breach: Millions of Patient Records Just Hit the HHS Tracker, and the Common Thread Is Third-Party Risk · Data BreachDo I Need a BAA With My Vendor? A Plain-English Guide to Which Vendors Require a Business Associate Agreement · Business AssociatesAmazon's One Medical Seniors Hit by ShinyHunters Extortion Group: 8.8TB of Legacy Patient Data at Risk · Data BreachOpenLoop Health Telehealth Infrastructure Vendor Breach Exposes Patient Data Across Multiple Digital Health Clients · Data BreachHealthcare AI Vendor Xsolis Breach Exposes 1.4 Million Records Across Seven Hospital Systems Including Mayo Clinic · Data BreachHHS Breach Portal Backlog: OCR Still Adding March 2026 Breaches in Late June — What the Delay Means for Compliance Teams · AnalysisKettering Health Refused to Pay the Ransom. The Data Leaked Anyway: What 1.7 Million Exposed Records Teach About Ransomware and HIPAA · Data BreachOCR Settles Ransomware Investigation with Employer-Sponsored Health Plan for $450,000 · OCR EnforcementWhy a Third of Healthcare Breaches Now Trace Back to a Vendor: A Mid-Year 2026 Analysis · AnalysisFrom 4 Million to 60+ Million: The Conduent Breach Shows How Far Third-Party Risk Reaches · Data BreachNYC Health + Hospitals Breach: 1.8 Million Records Exposed via Third-Party Vendor, Including Biometric Data · Data BreachWhen Your Vendor Is the Breach: Millions of Patient Records Just Hit the HHS Tracker, and the Common Thread Is Third-Party Risk · Data BreachDo I Need a BAA With My Vendor? A Plain-English Guide to Which Vendors Require a Business Associate Agreement · Business Associates

OCR Enforcement

15 Million Records, a $10,000 Fine, and a Company That No Longer Exists: The MMG Fusion Story

TL;DR

MMG Fusion LLC exposed 15 million patients' protected health information in a 2020 breach that ended up on the dark web. OCR fined them $10,000 — one of the lowest fines relative to breach size in enforcement history — and issued a 3-year corrective action plan. The company has since dissolved. The case raises a question every covered entity must answer: what happens to your patients' data when a business associate fails, gets acquired, or goes out of business?

MMG Fusion LLC exposed 15 million patients' protected health information in a 2020 breach that ended up on the dark web. OCR fined them $10,000 — one of the lowest fines relative to breach size in enforcement history — and issued a 3-year corrective action plan. The company has since dissolved. The case raises a question every covered entity must answer: what happens to your patients' data when a business associate fails, gets acquired, or goes out of business?

OCR fined MMG Fusion just $10,000 for exposing 15 million patients' data — the company has since dissolved. The real story is what this means for every dental practice that trusted them with patient data.

medcomply.ai editorial teamPublished May 31, 2026Updated May 31, 20266 min read

There is a number that has been circulating in the HIPAA compliance community since March 2026 that stops compliance officers cold: $10,000.

That is what OCR collected from MMG Fusion LLC for exposing the protected health information of 15 million patients. Not $10 million. Not $1 million. Ten thousand dollars — less than many small practices pay for a single piece of medical equipment.

The settlement is officially OCR's 12th enforcement action under its Risk Analysis Initiative. Unofficially it is a case study in what happens at the intersection of cybersecurity failure, business associate accountability, and corporate dissolution.

What MMG Fusion was and what happened

MMG Fusion LLC helped oral healthcare professionals market, manage, and grow their practices and provided software that communicated with patients. As a company that created, received, maintained, and transmitted protected health information on behalf of dental practices, MMG was a HIPAA business associate — subject to the full Security Rule, directly liable for its own violations, and required to have signed BAAs with every dental practice it served.

In December 2020, a malicious actor infiltrated MMG's systems. Over 15 million patients' protected health information was exposed in the cybercrime and leaked to the dark web.

The exposed data included patient names, contact information, dates of birth, and appointment scheduling information — the kind of data that enables identity theft and targeted phishing attacks against healthcare patients.

OCR determined that MMG committed three distinct violations: impermissible disclosure of PHI, failure to conduct an accurate risk analysis, and — critically — failure to notify the affected covered entities of the breach within the required 60-day window.

45 CFR §164.410

The $10,000 fine — why so small

MMG agreed to a $10,000 settlement and a 3-year Corrective Action Plan.

For context: OCR's standard penalty for a single willful neglect violation starts at $73,011. A breach affecting 15 million individuals, involving three separate HIPAA violations, would ordinarily support a penalty in the millions of dollars.

The $10,000 figure almost certainly reflects MMG's financial condition. HIPAA requires OCR to consider the financial resources of the entity when calculating penalties. An entity on the verge of dissolution — or one with limited assets — cannot realistically pay a multi-million dollar penalty. OCR's practical choice is to accept a reduced amount that the entity can actually pay, paired with a corrective action plan that requires ongoing compliance investment.

The corrective action plan spans three years and requires MMG to implement all the compliance measures it neglected before the breach. For a company that has since dissolved, the practical enforceability of a three-year CAP raises its own questions.

The company that no longer exists

The company no longer exists.

This single fact transforms the MMG Fusion settlement from an unusual enforcement story into an important lesson about business associate risk that every covered entity needs to internalize.

When a business associate dissolves, the following happen simultaneously:

The BAA becomes effectively unenforceable. The legal obligations remain in theory, but there is no operating entity to hold accountable, no assets to attach, and no management to compel compliance.

The corrective action plan becomes a document with no one to execute it. A three-year CAP requiring ongoing risk analyses, policy updates, and OCR reporting requires a functioning organization. A dissolved company cannot fulfill these obligations.

The patient data question becomes urgent. Where is the PHI now? Who controls it? What security protections, if any, remain in place for data held by a company that no longer exists? These questions may have no satisfactory answer.

The covered entities that trusted MMG with patient data — the dental practices that executed BAAs, integrated MMG's software into their operations, and sent patient information to MMG's systems — had no meaningful recourse against a dissolved entity.

What this means for your vendor relationships

This settlement is OCR's 12th enforcement action under its Risk Analysis Initiative, which launched in approximately October 2024. The pattern across these 12 actions is consistent. Regardless of how the breach occurred — ransomware, phishing, unauthorized access — the common thread is that the organization had not conducted a compliant risk analysis before the incident.

For covered entities, the MMG Fusion case adds a dimension to vendor risk that goes beyond the standard BAA checklist. The question is not just whether your business associate has signed a BAA and conducted a risk analysis. It is whether your business associate will still exist next year — and what happens to your patients' data if it doesn't.

Warning

The MMG Fusion settlement is a reminder that a BAA is a contract, not a guarantee. A business associate that dissolves, gets acquired, or becomes insolvent cannot fulfill its HIPAA obligations — and your patients bear the consequences. Vendor due diligence should include an assessment of financial stability, not just security practices.

Three things every covered entity should do in response:

Audit your current business associates. For each vendor that holds or accesses patient PHI, ask: what is their financial condition? Are they a stable, ongoing business? Do they carry cyber liability insurance? What happens to patient data in a wind-down scenario?

Review your BAA provisions. Standard BAA templates address data security obligations but rarely address business continuity scenarios. Consider adding provisions requiring notice of material financial distress, requirements to maintain cyber insurance, and data return or destruction obligations in the event of business closure.

Know what data each vendor holds. You cannot manage the risk of a vendor failure if you do not know what patient data that vendor has. Maintain a current inventory of what PHI each business associate holds, in what systems, and how it is protected.

OCR collected $10,000 from MMG Fusion for exposing 15 million patients' records. The company no longer exists. The patients' data was on the dark web. The dental practices that trusted MMG with their patients had limited recourse. The lesson is not that OCR under-enforced — it is that a BAA cannot protect your patients from a business associate that fails. Vendor risk management must go beyond contract execution.

Sources & citations

  • Health Tech Authority — MMG Fusion Settlement AnalysisOpen
  • Abyde — OCR Ransomware Settlements 2026Open
  • 45 CFR §164.410 — Business Associate Breach NotificationOpen

All content verified against official HHS guidance and the Code of Federal Regulations.

Frequently asked questions

Why was MMG Fusion's fine only $10,000 for a 15-million-patient breach?
OCR considers the financial condition of the entity when calculating penalties. MMG Fusion's low fine likely reflects the company's limited financial resources at the time of settlement — possibly connected to the company's subsequent dissolution. A financially insolvent entity cannot pay a multi-million dollar penalty, so OCR accepted a reduced amount in exchange for a 3-year corrective action plan.
What happens to a BAA when a business associate goes out of business?
When a business associate dissolves, the contractual obligations of the BAA become effectively unenforceable against the entity. The covered entity retains its own HIPAA obligations to affected patients but loses its ability to hold the business associate accountable. This is why vetting vendor financial stability and data handling practices before executing a BAA matters — not just at signing, but on an ongoing basis.
How did 15 million patient records end up on the dark web?
In December 2020, a malicious actor infiltrated MMG Fusion's systems and accessed protected health information including patient names, contact information, dates of birth, and appointment data. MMG failed to notify the affected dental practices of the breach within 60 days as required by HIPAA, meaning many covered entities whose patients were affected did not know about the breach for an extended period.
What is OCR's Risk Analysis Initiative and where does this settlement fit?
OCR launched the Risk Analysis Initiative to focus enforcement on compliance with the HIPAA Security Rule risk analysis requirement. The MMG Fusion settlement was OCR's 12th enforcement action under the initiative. Like every preceding case, OCR found that the entity had failed to conduct an accurate and thorough risk analysis — the foundational security requirement that, if met, would have identified the vulnerabilities that enabled the breach.
What should covered entities do to protect themselves from business associate failures?
Three things: First, conduct vendor due diligence before executing BAAs — including assessing the vendor's financial stability and security posture. Second, include BAA provisions requiring the business associate to maintain cyber insurance and notify you immediately of any financial distress that could affect data security. Third, understand what data the vendor holds and have a contingency plan for retrieving or securing that data if the vendor fails.

Not legal advice. medcomply.ai provides compliance intelligence for educational and operational planning. Consult qualified counsel for legal interpretation.