Skip to main content
Darkfield

Ransomware victim disclosure

← All victims

State of Florida

Claimed by Cl0p · listed 2 hours ago

541 GB
Data size
Hundreds of millions of records/rows records
Today
Age
since listed · data leaked

Status timeline

  1. ListedSep 20, 2026
  2. Data leakeddate unknown

At a glance

Group
Cl0p
Status
Data leaked
Country
United States
Sector
Government
Listed on leak site
Sep 20, 2026
Data size
541 GB
Records
Hundreds of millions of records/rows

About the victim

AI dossier — public-source company profile

The State of Florida is the executive and administrative apparatus of the U.S. state of Florida, responsible for public services, infrastructure, and governance across the state.

Industry
Government — State Administration

Attack summary

Severity: critical — Confirmed exfiltration of massive volumes of regulated government data including employee and customer PII at scale, PHI, security infrastructure documentation, access credentials, and operational security artifacts. Direct threat to state government operations and public safety.

Cl0p claims to have exfiltrated 541 GB+ of data from Florida state systems, including 12.9 million Salesforce records, 645 GB of SharePoint data, customer contact records, employee PII, security infrastructure drawings, access credentials, and internal policies. The group demanded $13 million and threatened data publication when the demand was not met.

critical

Data the group says was taken

AI dossier — extracted from the leak post
  • 12.9 million Salesforce records
  • 645 GB SharePoint internal data (369.6 GB compressed)
  • 182,000+ customer contact rows
  • 8,300+ employee PII records (names, emails, job titles, phone numbers)
  • Executed contracts, MSAs, NDAs, leases, SOWs
  • Physical key inventory logs and contractor audit documentation
  • Data center drawings, floor plans, electrical diagrams, security schematics
  • CERM process library
  • Physical and information security policies
  • Security scorecards and KPI workbooks
  • Credential and access-control artifacts (PasswordList.xlsx, Okta SSC Access lists, badge reports, data center access forms)

What the group claims

State of Florida failed to reach an agreement. Hundreds of millions of records/rows of data was compromised containing very sensitive information spanning from PII to PHI.

The leak post

captured from the group's site
**IF YOU WANT TO SAVE YOUR BRAND AND NOT DIE BY MY HANDS:** Email us from your official email at [email protected] and lets see how rich you really are. 2.333% of my networth is a 8 figure amount, I hope you can pay that much because that is the demand, negotiable. Get your bosses in front of the white board in the war room. Clock is ticking moron. Kindly excuse our unprofessionalism.
We are aware of the situation involving a number of our CDNs being unreachable. We are working on restoring them. We estimate 24 to 48 hours till they are back. 91.215.85.22 remains accessible and usable. **Update, July 27, 3:01 a.m. ET:** All CDN mirrors are back online; however, content synchronization across all three mirrors is still ongoing. Addicionally, we are still working on preparing the release of the torrents. We kindly ask our visitors to seed once they become available. A notification will be posted upon release. All CDN mirrors are currently experiencing a service disruption. **All files are fully backed up and no data has been lost.** At this time we do not have an estimated time of resolution.We are working to restore service promptly and will share updates as they become avail…

Data the group says was taken

  • PII
  • PHI

Screenshot of the leak post

Leak screenshot for State of Florida

Sources

Source

Indexed 2 hours ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About Cl0p

The Cl0p (also known as Clop) ransomware group is a financially motivated cybercriminal organization that emerged in March 2020, operating as part of the broader TA505/FIN11 threat landscape and conducting high-impact ransomware campaigns targeting organizations globally. The group is believed to operate from Russian-speaking territories and has been linked to the prolific TA505 cybercriminal consortium, functioning as a Ransomware-as-a-Service operation that collaborates with various affiliate groups to maximize their operational reach. Cl0p primarily gains initial access through exploitation of zero-day vulnerabilities in file transfer applications, phishing campaigns, and SQL injection attacks, employing double extortion tactics by exfiltrating sensitive data before deploying their custom ransomware payload, which uses strong encryption algorithms to render victim systems inoperable. The group has been responsible for several high-profile campaigns, most notably their exploitation of zero-day vulnerabilities in MOVEit Transfer software in 2023, which affected hundreds of organizations worldwide including major corporations and government entities, and their previous campaigns targeting Accellion FTA and other file transfer solutions that resulted in the compromise of sensitive data from numerous high-value targets. Cl0p remains active as of 2024, continuing to evolve their tactics and maintain their position as one of the most prolific ransomware groups globally, with over 1,490 documented victims primarily concentrated in the United States, Canada, United Kingdom, Germany, and Australia across technology, manufacturing, transportation, and consumer services sectors. The group has been linked to 2,750 public disclosures across our corpus. First observed on a leak site on March 13, 2020; most recent post September 20, 2026. The operation is currently active.

Also tracked as: Clop, TA505, FIN11.

Timeline of this disclosure

  • September 20, 2026State of Florida listed by Cl0p on the group's public leak site
Data size
541 GB
Records
Hundreds of millions of records/rows

Other recent disclosures by Cl0p

Cl0p has been linked to 2,750 public victims on Darkfield. A sample of the most recent:

See the full Cl0p dossier →

Sector and geography

This disclosure adds to ransomware activity in the Government sector, which has 685 disclosures indexed across all operators we track. Geographically, State of Florida is reported in United States, a country with 3,167 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Cl0p means State of Florida appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Report the incident to your national CERT, CISA (United States), as required for your jurisdiction.
  • Monitor for the data appearing on Cl0p's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.