MUFG Union Bank reported a data breach to the Montana Attorney General. The breach was reported on 2018-12-07. The breach occurred from 11/9/2018 to 11/22/2018. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Dec 7, 2018 → Dec 11, 2018. View entity profile → Other incidents for this victim →
incident inc_672f32b512ae470a · merge_method deterministic · confidence 100%
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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 9, 2018
When the intrusion reportedly occurred, per the linked filings
MUFG Union Bank reported a data breach to the Montana Attorney General. The breach was reported on 2018-12-07. The breach occurred from 11/9/2018 to 11/22/2018. 1 Montana residents were affected.
Affected (this filing): 1
MUFG Union Bank, N.A. notified customers that an unauthorized third party used login credentials to access Union Bank Online and/or Mobile Banking accounts between November 9 and November 22, 2018. The compromised credentials were likely obtained from third-party sources, not Union Bank systems. Affected data included User IDs, passwords, names, partial or full bank account numbers, account balances, and transaction information. The bank blocked unauthorized access, reset passwords, and offered 12 months of complimentary credit monitoring.
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.