Confirmed breach. Intrusion May 15, 2017, discovered May 17, 2017 — the first regulatory filing landed 14 days later. 38,391 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 clocksOregon✓ OR AG ≤45dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
38,391
Data types
—
Jurisdictions
2
CA OR
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 15, 2017
When the intrusion reportedly occurred, per the linked filings
BMO Harris Bank N.A. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-05-31. The breach occurred during 5/15/2017 - 5/15/2017. The breach was discovered on 5/17/2017. 38,391 individuals were affected. Notice was sent on 5/25/2017.
Affected (this filing): 38,391
OR AG ≤45d
🐻California State AGMost recentlinked via multistate filing link · 100%
BMO Harris Bank N.A. notified customers of a misdelivery error during the production of 2016 IRS Form 5498. Some customers received their own form along with another customer's form, while others did not receive their form. The exposed data included name, address, last four digits of SSN, account number, IRA contributions, and Fair Market Value. The bank is mailing replacement forms and offering 12 months of 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.