1st Lake Properties, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-07-22. The breach occurred on 12/25/2021. 7 Montana residents were affected.
Affected (this filing): 7
Clustered 2 filings across 2 jurisdictions · filing window Jul 22, 2022 → Aug 12, 2022. View entity profile → Other incidents for this victim →
incident inc_b87790f671fe42d0 · merge_method human · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 25, 2021
When the intrusion reportedly occurred, per the linked filings
Jul 11, 2022
Reported by MAINE AG filing
1st Lake Properties, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-07-22. The breach occurred on 12/25/2021. 7 Montana residents were affected.
Affected (this filing): 7
1st Lake Properties, Inc. reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred on December 24, 2021. The breach was discovered on July 11, 2022, and affected four Maine residents. The compromised information included names in combination with driver's license or non-driver identification card numbers. The company provided written notification to the affected individuals on July 22, 2022, and offered one year of identity theft protection services through Experian.
Affected (this filing): 4
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.