Confirmed breach. Intrusion Jun 2, 2024, discovered Jun 2, 2024 — the first regulatory filing landed 137 days later (flagged late). 5 individuals reported across the linked filings.
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.
Regulatory clocksMaine✗ ME AG >90d · 137dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
5
Data types
—
Jurisdictions
2
ME MT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 2, 2024
When the intrusion reportedly occurred, per the linked filings
The City of Coon Rapids, Minnesota, a government entity, reported an external system breach (hacking) that occurred and was discovered on June 2, 2024. The breach affected 1 Maine resident. The city provided written notification to affected individuals on October 17, 2024, and offered 12 months of identity theft protection services through IDX.
Affected (this filing): 1
ME AG >90d · 137dME resident >60d · 137d
🦬Montana State AGMost recentlinked via multistate filing link · 100%
City of Coon Rapids, MN reported a data breach to the Montana Attorney General. The breach was reported on 2024-10-17. The breach occurred on 6/2/2024. 4 Montana residents were affected.
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.