Community Connections
bd_4d97651d818e5495 · schema v1 · pii pii-v1
Full breach record for Community Connections →3 incidents on fileCommunity Connections reported to HHS on 2026-05-18 a Hacking/IT Incident affecting 18943 individuals. Breached information located on Network Server.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
May 18, 2026
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?Regulatory filings (4) · sorted by filing gap
- New Hampshire State AGbd_77195f6440f4607c2026-06-01 · +14dCandidate
- Indiana State AGbd_7536a02039173c3e2026-06-03 · +16dVerified
- Maine State AGbd_67991cf185a26a972026-06-04 · +17dVerified
- Massachusetts State AGbd_8ba09a7d74e4806d2026-06-16 · +29dVerified
Filing propagation · 5 filings · 5 states
View merged incident ↗Pattern: first filing May 18 (DC), last Jun 16 (MA) — a 29-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.