2024 · United States · Q - Human health and social work activities · Ransomware attack with data theft and leak
Analysed 2026-11-06 by Hermes
Open this case in the tool →Ransomware attack with data theft and leak
Strategy to Execution
Evidence coverage: 3/6 stages, weight 21/60
Decisive stage: detection (clearest evidence) · Alternative: Expertise to Execution
(1) Omni Family Health is a HIPAA-regulated nonprofit network of 39 community health centers holding protected health information of hundreds of thousands of patients and employees; the strategic expectation on the victim side is the standing regulatory obligation to audit systems, detect unauthorized access and exfiltration of PHI, and notify affected individuals promptly - an expectation its own breach letter restates when it says the confidentiality, privacy, and security of the information it maintains is its top priority. (2) In practice a February 2024 cyberattack knocked its IT systems offline for about five days and its investigation at the time found no evidence of data theft; Omni's own controls never noticed anything different: it first learned of the theft on 7 August 2024 when Hunters International claimed it on the dark web, its follow-up investigation confirmed the posted data appeared to be its patients' and employees' data (the 2.7 TB volume is the attacker's unverified claim), the gang published everything on 23 August, and notification letters to individuals followed only in early October with the public disclosure on 18-19 October. The entry vector is undisclosed and is not load-bearing. (3) This is a Strategy to Execution gap: the expectation sat at the doctrinal level (HIPAA obligations, the victim's own stated priority), yet it did not translate into operational reality - monitoring did not surface an intrusion connected to an attack six months earlier, no egress control interrupted bulk exfiltration of crown-jewel PHI, and the mandated notification process only ran to the attacker's leak timeline; no source shows leadership deferred, under-resourced or knowingly accepted these controls, so the chain broke at execution rather than at the decision level, and recovery was not the constraint in this exfiltration-driven extortion. The decisive stage is detection (clearest evidence, documented in the victim's own notification); the February-to-August connection is the victim's own evidence-not-conclusive reading and is treated as supporting context, not a coded eradication failure. RM34 (Strategy to Execution lens): monitoring and alert-handling requirements (SOC, SIEM, EDR) were not operated as intended - no internal detection contributed to discovery, which instead came from the attacker's dark-web posting, and the February investigation cleared the network of data theft while the data was already gone (causal role: Obscuring). RM35 (Strategy to Execution lens): egress controls and DLP were never translated into effective operational barriers - bulk sensitive PHI left the network undetected and uninterruptedly, and Omni confirmed the exfiltration only from the posted data after the fact (causal role: Amplifying). RM39 (Strategy to Execution lens): notification criteria and workflows were not operationalised to the breach chronology - affected patients and employees were left unprotected for roughly seven weeks after the full dataset had been published, with the organization's disclosure cadence set by the leak rather than by its own process (causal role: Constraining).
RM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapRM39 — Breach notification / disclosure failureEuRepoC row; row description matches the victim (no mismatch). Victim's own notice page (omnifamilyhealth.org/notice-of-cybersecurity-incident) returned HTTP 403 to direct fetch; the victim's notification letter as filed with the California Attorney General was used as the primary disclosure instead. The 2.7 TB exfiltration volume is the ransomware gang's unverified claim (cited only as reported by established press); the fact of exfiltration is confirmed by the victim's investigation. The link between the February 2024 attack and the August dark-web data is described by the victim itself as evidence of a potential connection but not conclusive, so it is not coded as an eradication failure (RM38). Hunters International's initial-access methods (valid accounts, RDP, phishing) are the group's documented pattern, not incident-confirmed, and were not used for the classification. Disclosure timing: Omni reported to HHS OCR on 4 October 2024 and letters were mailed by 10 October, within HIPAA's outer limit, but roughly seven weeks after the attacker had published the full dataset; the response-stage gap rests on this leak-first chronology and is coded contributing, source type inference. Aftermath (context only): 21 class actions consolidated as Pace v. Omni Family Health (Kern County Superior Court) were resolved by a $6.5 million settlement with agreed security enhancements; Omni denied all wrongdoing.