Community Connections
bd_67991cf185a26a97 · schema v1 · pii pii-v1
Full breach record for Community Connections →3 incidents on fileCommunity Connections, a healthcare entity based in Washington, DC, reported an external system breach (hacking) occurring on March 18, 2026, discovered on March 20, 2026. The incident affected 20,879 individuals, including 2 Maine residents. The breach involved the acquisition of personal identifiers. Community Connections provided written notification to affected individuals on June 3, 2026, and offered 12 months of credit monitoring and identity theft protection services through Cyberscout, a TransUnion company.
J jump to incidentP pin to compareR raw source
Incident timeline
Mar 18, 2026
Begins
Mar 20, 2026
Discovered
Jun 4, 2026
Filed
vs. sector median
1 wks faster
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- Indiana State AGbd_7536a02039173c3e2026-06-03 · +1dVerified
- New Hampshire State AGbd_77195f6440f4607c2026-06-01 · +3dCandidate
- Massachusetts State AGbd_8ba09a7d74e4806d2026-06-16 · +12dVerified
- HHS OCRbd_4d97651d818e54952026-05-18 · +17dVerified
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.