Community Connections
bd_b49a93d718c00f46 · schema v1 · pii pii-v1
Full breach record for Community Connections →3 incidents on fileCommunity Connections reported to HHS on 2024-12-11 a Hacking/IT Incident affecting 18949 individuals. Breached information located on Network Server.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Dec 11, 2024
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Siteinc_ransombd_33101cbf45448ba22026-04-04 · +479dVerified by operator
- Leak Siteinc_ransombd_2c42919f7a34633d2024-10-21 · +51dVerified
Regulatory filings (4) · sorted by filing gap
- Massachusetts State AGbd_1165a7a7c65ed8e92025-08-27 · +259dCandidate
- Maine State AGbd_d6acebcf8b679d0e2025-08-27 · +259dVerified
- New Hampshire State AGbd_e4be22cbcdc301462025-08-27 · +259dVerified
- Indiana State AGbd_5aeb8944cfa7fec42025-08-28 · +260dVerified
Filing propagation · 5 filings · 5 states
View merged incident ↗Pattern: first filing Dec 11 (DC), last Aug 28 (IN) — a 260-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.