What happened
Community Health Northwest Florida disconnected its network after a cyberattack disrupted operations on Dec. 24, 2024. The nonprofit provider, legally Escambia Community Clinics, Inc., said in its March 2025 notice that the disruption affected access to data and systems. Outside cybersecurity specialists assisted with containment and investigation.
The Pensacola News Journal reported Dec. 27 that the provider had taken servers offline as a precaution. Phone, email and internet service were unavailable.
Operational significance
WEAR reported that clinics closed Dec. 26 because of the attack, following a scheduled Christmas closure. Dental appointments were canceled for later rescheduling. Primary and pediatric appointments were retained as services resumed with reduced technology access. Dental, pharmacy, X-ray and mammography services were affected.
All 17 locations were open Dec. 30 with limited connectivity, according to a provider update carried by La Costa Latina. Staff used paper charts and prescriptions, and patients were warned of longer waits. New prescriptions at the Jackson Street site required printed prescriptions; online refill availability remained conditional on connectivity.
A Jan. 10 recovery report said communications had returned and patients could again contact clinics for appointments and prescriptions. The provider retained its temporary hotline as a backup.
Confidence and uncertainty
The provider’s public statements establish a cyberattack and operational disruption. Early assurances about patient information reflected an incomplete investigation. In its Jan. 26, 2026, notice, the provider confirmed that an unauthorized party had accessed its network and certain stored files. Information varied by person and included medical, insurance, identity and financial information. That notice did not establish that files were copied or that information had been misused.
The HHS breach portal lists 143,969 affected individuals for the legal entity’s network-server hacking report submitted Feb. 3, 2025. That is the report submission date; the provider identifies Dec. 24 as the disruption date.
Analytic gaps
The initial entry method, full unauthorized-access period and exact day of complete clinical-system restoration remain unresolved. Communications recovery does not establish when every affected application returned. Comparitech reported Jan. 14, 2025 that RansomHub had claimed responsibility, alleged theft of 68 GB and demanded payment. The provider had not verified that claim. The reviewed official notices confirm unauthorized file access but do not identify a responsible group or confirm ransomware encryption. Ransomware.live independently recorded a listing for the provider’s exact domain Jan. 13, 2025; that observation is not the original actor-post timestamp.