First National Bank of Omaha reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-10. The breach occurred from 5/29/2023 to 5/30/2023. 6 Montana residents were affected.
Affected (this filing): 6
Clustered 2 filings across 2 jurisdictions · filing window Aug 10, 2023 → Aug 23, 2023. View entity profile → Other incidents for this victim →
incident inc_69e7814f9f3e4eb3 · 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 29, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 27, 2023
Reported by MAINE AG filing
First National Bank of Omaha reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-10. The breach occurred from 5/29/2023 to 5/30/2023. 6 Montana residents were affected.
Affected (this filing): 6
First National Bank of Omaha reported that a third-party vendor, PBI, was impacted by the MOVEit vulnerability, which resulted in a data breach affecting individuals' names and Social Security numbers. The incident occurred between May 29, 2023, and May 30, 2023, and was discovered on July 27, 2023. Two residents of Maine were affected. The bank has offered 12 months of credit monitoring and identity theft restoration services through Kroll to those impacted.
Affected (this filing): 2
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.