Community Connections reported a data breach to the Indiana Attorney General. The breach occurred on 2026-03-18 and was reported on 2026-06-03. 2 Indiana residents were affected. 20,879 individuals affected in total.
Affected (this filing): 20,879
Clustered 2 filings across 2 jurisdictions · filing window Jun 3, 2026 → Jun 4, 2026. View entity profile → Other incidents for this victim →
incident inc_802ca6b2f62f40ed · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Government ID · Identity (basic)
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 18, 2026
When the intrusion reportedly occurred, per the linked filings
Mar 20, 2026
Reported by MAINE AG filing
Community Connections reported a data breach to the Indiana Attorney General. The breach occurred on 2026-03-18 and was reported on 2026-06-03. 2 Indiana residents were affected. 20,879 individuals affected in total.
Affected (this filing): 20,879
Community 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.
Affected (this filing): 20,879
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.