Confirmed breach. Intrusion Feb 18, 2020, discovered Feb 28, 2020 — the first regulatory filing landed 202 days later (flagged late). 8 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 · 202dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
8
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
ME MT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 18, 2020
When the intrusion reportedly occurred, per the linked filings
BankNorth, a financial services company, reported an external system breach that occurred on February 18, 2020. The breach was discovered on February 28, 2020, and affected 2 Maine residents. The compromised information includes names and Social Security numbers. BankNorth offered one year of credit monitoring services to the affected individuals.
Affected (this filing): 2
ME AG >90d · 202dME resident >180d · 201d
🦬Montana State AGMost recentlinked via multistate filing link · 100%
BankNorth reported a data breach to the Montana Attorney General. The breach was reported on 2020-09-17. The breach occurred from 2/18/2020 to 7/17/2020. 6 Montana residents were affected.
Affected (this filing): 6
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.