Fairfield Memorial Hospital
bd_44b173dcc22738e9 · schema v1 · pii pii-v1
Full breach record for Fairfield Memorial Hospital →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Sanctions caution: LockBit 3.x carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
Fairfield Memorial Hospital is a fully accredited, not-for-profit critical access hospital. The hospital has 25 acute-care beds and a workforce of over 400 employees. The medical staff at Fairfield Memorial Hospital is comprised of over 90 creden...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 2, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitelockbit_3bd_100f8e0a1110f1092024-06-20 · +12dVerified by operator
Regulatory filings (4) · sorted by filing gap
- HHS OCRbd_394bf6c7c63034892024-08-15 · +44dVerified
- Illinois State AGbd_5157448dc4025e4b2024-10-01 · +91dVerified
- Montana State AGbd_58f5d1200c1151352024-10-21 · +111dVerified by operator
- Indiana State AGbd_90409acca46b4dd12024-10-21 · +111dVerified by operator
Filing propagation · 5 filings · 3 states
View merged incident ↗Pattern: first filing Jul 2, last Oct 21 (IN) — a 111-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.