Kirkwood Bank & Trust reported a data breach to the Montana Attorney General. The breach was reported on 2023-12-07. The breach occurred from 5/27/2023 to 5/31/2023. 59 Montana residents were affected.
Affected (this filing): 59
Clustered 2 filings across 2 jurisdictions · filing window Dec 7, 2023 → Dec 8, 2023. View entity profile → Other incidents for this victim →
incident inc_226b3d9792dd472f · 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
May 27, 2023
When the intrusion reportedly occurred, per the linked filings
Nov 15, 2023
Reported by MAINE AG filing
Kirkwood Bank & Trust reported a data breach to the Montana Attorney General. The breach was reported on 2023-12-07. The breach occurred from 5/27/2023 to 5/31/2023. 59 Montana residents were affected.
Affected (this filing): 59
Kirkwood Bank & Trust reported a data breach affecting 8,719 individuals, including 3 Maine residents. The breach, which occurred between May 27 and May 31, 2023, and was discovered on November 15, 2023, involved an external system hack. The compromised information included names and Social Security numbers. The bank notified affected individuals on December 7, 2023, and offered 24 months of free identity monitoring services from Kroll.
Affected (this filing): 3
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.