The Loretto Hospital
bd_3adbab8320c53929 · schema v1 · pii pii-v1
Full breach record for The Loretto Hospital →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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.
Source: Ransomware.live
Post text · scraped from the leak site
Established in 1923, Loretto Hospital serves more than 33,000 patients each year. They provide quality healthcare services including: primary care, geriatric medicine, vision care, behavioral health services, women’s health, podiatric medicine, and dental services. In addition, they are the largest non-governmental employer in the Austin community with more than 600 employees many of whom live in Austin.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 1, 2025
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteransomhousebd_30be714b83c1f8d72025-02-02 · +58dVerified by operator
Regulatory filings (2) · sorted by filing gap
- HHS OCRbd_3a57054c89ece8292025-04-04 · +3dVerified
- Indiana State AGbd_09fbc998dfc6f9f72025-07-24 · +114dVerified by operator
Filing propagation · 2 filings · 2 states
View merged incident ↗Pattern: first filing Apr 4 (IL), last Jul 24 (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.