South Florida Ransomware: Critical Daixin Claim Hits 200K
Daixin Claims a South Florida Hospice Network: What the Listing Means for Local Businesses

On November 16, 2026, the Daixin ransomware group listed Trustbridge & Empath Health on its dark-web leak site, naming Hospice of Palm Beach County and Hospice by the Sea and threatening to publish “100% of PII and PHI” for roughly 200,000 families across the region. As of this morning neither organization has confirmed an intrusion, the group has posted no samples, no file counts and no proof of encryption — and that gap between claim and confirmation is the entire story. Every South Florida ransomware headline starts this way, and most businesses read it wrong. Ransomware.live is tracking the listing.

What this covers: what the South Florida ransomware claim says · how the group gets in · why hospice data is the target · five readiness moves · if a partner is named · the phishing wave · common questions

What the South Florida ransomware claim actually says

A leak-site post is a negotiation tactic, not a diagnosis. Daixin’s pattern is to name the victim, publish a short deadline, and hold the proof until the victim responds — because a public count of stolen records is the pressure, not the point. South Florida ransomware claims follow a predictable script: a well-known local name, an unverified threat aimed at the people who trust that name, and a wave of opportunistic phishing that lands before the facts do.

What a listing does establish is that someone in the group believes a path in exists. What it does not establish is scope: how much data, which systems, whether anything was encrypted, or which of several affiliated entities under a parent brand was touched. Trustbridge & Empath Health operates across multiple counties, and a claim naming two hospice programs does not automatically mean patient records at every location moved.

So the honest read for a business watching this South Florida ransomware story: treat the listing as a signal to review your own exposure and your relationships, not as confirmation that a partner’s systems were compromised.

How the South Florida ransomware group gets in

Per CISA advisory AA23-284A, Daixin works through stolen or phished credentials on internet-facing VPN and firewall appliances, escalates into VMware vCenter, and exfiltrates data before encrypting ESXi hosts. It is a data-theft business first; locking the hypervisor is simply the leverage applied afterward.

That matters because it inverts the usual defensive assumption. Ransomware crews that lead with encryption can be slowed by good backups. Groups that lead with credential theft and virtualisation access are already inside the management plane before the first file is touched, and backups do not remove a stolen copy of the data.

For a small business that means two exposures, and they are separate problems. The first is your own edge: the VPN, firewall or remote-access tool nobody has reviewed since it went in. The second is your business associates — the billing service, the IT provider, the home-health agency holding records under a business associate agreement. When one of them is named, your name is in the queue behind it whether or not your own network was involved.

Dealing with this at your office? Talk to a local IT expert →

Why South Florida ransomware targets hospice data

South Florida ransomware crews go after healthcare records because they carry the longest tail of any data a small organization holds: diagnoses, medications, insurance identifiers and family contacts that do not expire when a patient is discharged. A hospice adds something worse — a family network already in crisis, primed to respond to a message that references a real case.

That is what makes a hospice claim so effective as leverage, and why the follow-on fraud matters more than the encryption in most of these events. Patient and family contact data fuels medical-identity fraud for years, and the families named in a leak-site post are the ideal audience for a convincing callback.

Five moves for South Florida ransomware readiness

  1. Inventory every internet-facing device — VPN concentrators, firewalls, remote monitoring agents — and confirm current firmware plus phishing-resistant multi-factor authentication.
  2. Retire shared and standing vendor credentials. Named accounts, rotated on a schedule, with no vendor holding a permanent key to your core systems.
  3. Map where PHI and PII actually live, including backups and SaaS copies, then prove a restore works rather than trusting that a backup job reported success.
  4. Alert on bulk outbound data. Rclone-style exfiltration looks like a large transfer at two in the morning; most small business networks never notice it.
  5. Write down the first 24 hours. Who calls counsel, who calls clients, who answers the press, and who confirms or denies a leak-site claim before rumour does it for you.

If the South Florida ransomware claim touches a partner of yours

Treat a listing as a trigger for your own review. Confirm the business associate agreement covers the data that partner actually holds, ask what access they have to your systems, and expect phishing that references the news by name. Ask for the partner’s incident status in writing rather than absorbing a rumour, and record the date you asked.

If you are the named party’s customer rather than the named party, your questions are narrower: does that vendor hold your records, in what form, and what have they told you about containment. Those questions have factual answers, and a vendor that cannot answer them quickly is telling you something too.

The phishing wave that follows a South Florida ransomware headline

Breach headlines generate their own scam wave within days, usually aimed at the patients, families and vendors named in the story. Expect calls from someone claiming to be hospital billing, emails offering breach-compensation registration, and texts pointing at a portal that wants your insurance details and a password.

Two controls blunt most of it: tell staff and clients that no legitimate organization will ask for credentials or payment by inbound call or text about this event, and make sure anyone who handles patient or client data knows exactly where to report a suspicious message. The second is the one organizations skip, and it is the one that catches a real intrusion early.

Common questions about South Florida ransomware claims

Does a leak-site listing mean the data is already public? No. Groups routinely publish a name and a deadline before releasing any sample. Treat the claim as unverified until the victim or an agency confirms it.

Should we notify anyone if a business associate is listed? Hold the notification decision to your own counsel and your contractual terms, but start the factual review immediately. Do not sit on the question waiting for the news cycle to resolve.

Is there anything to do if we are not a healthcare organization? Yes. The same credential path applies to every organization with a remote-access appliance, and the same phishing wave will reference this story regardless of your industry.

South Florida ransomware: what we recommend

We run these checks for practices, nonprofits and small businesses across Palm Beach, Broward and Miami-Dade every week — from Wellington to Fort Lauderdale and Kendall. If you cannot answer the five questions above with evidence, start with a cybersecurity assessment or our fully managed IT program, before a leak-site post does the review for you.

Want a second opinion on what a South Florida ransomware claim means for your own exposure? Call Nextek IT and we will walk your edge, your credentials and your restore evidence with you.

Need IT that actually answers?

Nextek IT supports South Florida practices and businesses — medical, dental, legal, accounting — with managed IT, cybersecurity and HIPAA-focused support.

Talk to a Local IT Expert → Or call 954-780-7159