Summit Consolidated Group reported a data breach to the Montana Attorney General. The breach was reported on 2023-07-05. The breach occurred on 11/7/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Jul 5, 2023. View entity profile → Other incidents for this victim →
incident inc_3c6ce3e497cc4320 · 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.
Identity (basic) · Government ID
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 7, 2022
When the intrusion reportedly occurred, per the linked filings
May 30, 2023
Reported by MAINE AG filing
Summit Consolidated Group reported a data breach to the Montana Attorney General. The breach was reported on 2023-07-05. The breach occurred on 11/7/2022. 1 Montana residents were affected.
Affected (this filing): 1
Summit Consolidated Group reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred on November 7, 2022. The breach was discovered on May 30, 2023, and affected one Maine resident. The compromised information included names and Social Security numbers. The company provided written notification to the affected individual on July 3, 2023, and offered identity theft protection services.
Affected (this filing): 1
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.