Limestone Bank (now Peoples Bank) reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-15. The breach occurred from 11/21/2022 to 3/23/2023. 20 Montana residents were affected.
Affected (this filing): 20
Clustered 2 filings across 2 jurisdictions · filed Sep 15, 2023. View entity profile → Other incidents for this victim →
incident inc_879d2eb6e05d4bb3 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 21, 2022
When the intrusion reportedly occurred, per the linked filings
Aug 16, 2023
Reported by NEW HAMPSHIRE AG filing
Limestone Bank (now Peoples Bank) reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-15. The breach occurred from 11/21/2022 to 3/23/2023. 20 Montana residents were affected.
Affected (this filing): 20
Limestone Bank (now Peoples Bank) notified the New Hampshire Attorney General of a cybersecurity incident involving unauthorized access to an employee email account. The breach occurred between November 21, 2022, and March 23, 2023. The bank determined on August 16, 2023, that personal information of 26 New Hampshire residents was compromised. Notifications were mailed on September 15, 2023, offering one year of credit monitoring.
Affected (this filing): 26
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.