Community Connections
bd_8ba09a7d74e4806d · schema v1 · pii pii-v1
Full breach record for Community Connections →3 incidents on fileCommunity Connections, a healthcare provider, issued a data breach notice dated June 3, 2026, regarding unauthorized access to patient information. The incident involved potential exposure of personal and government-issued identifiers (PII/identity_government). The organization responded by changing passwords, implementing technical safeguards, and offering 24 months of free credit monitoring and fraud assistance via Cyberscout. No evidence of misuse was found, but notification was sent out of an abundance of caution to current and former patients across multiple states.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jun 16, 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
- Maine State AGbd_67991cf185a26a972026-06-04 · +12dVerified
- Indiana State AGbd_7536a02039173c3e2026-06-03 · +13dVerified
- New Hampshire State AGbd_77195f6440f4607c2026-06-01 · +15dCandidate
- HHS OCRbd_4d97651d818e54952026-05-18 · +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.