Clustered 3 filings across 3 jurisdictions · filing window May 18, 2026 → Jun 1, 2026. View entity profile → Other incidents for this victim →
incident inc_34edea4309384c74 · 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.
Health (basic) · Identity (basic)
DC MA NH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 18, 2026 → Mar 20, 2026
When the intrusion reportedly occurred, per the linked filings
Mar 20, 2026
Reported by NEW HAMPSHIRE AG filing
Community Connections reported to HHS on 2026-05-18 a Hacking/IT Incident affecting 18943 individuals. Breached information located on Network Server.
Affected (this filing): 18,943
Community Connections, a not-for-profit healthcare provider, notified the New Hampshire Attorney General of a cybersecurity incident discovered on March 20, 2026. Unauthorized access occurred from March 18-20, 2026, potentially exposing names, SSNs, DOBs, medical, and financial information of one NH resident. The company engaged forensic investigators, isolated systems, and offered 12 months of credit monitoring.
Affected (this filing): 1
Community 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.
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.