Arvest Bank reported a data breach to the Montana Attorney General. The breach was reported on 2022-10-31. The breach occurred from 5/26/2022 to 7/5/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Oct 31, 2022 → Nov 1, 2022. View entity profile → Other incidents for this victim →
incident inc_72126441c937402b · merge_method llm · confidence 57%
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 26, 2022
When the intrusion reportedly occurred, per the linked filings
Jul 11, 2022
Reported by MAINE AG filing
Arvest Bank reported a data breach to the Montana Attorney General. The breach was reported on 2022-10-31. The breach occurred from 5/26/2022 to 7/5/2022. 1 Montana residents were affected.
Affected (this filing): 1
Arvest Bank reported a data breach caused by an internal issue at a third-party vendor. The breach occurred on May 26, 2022, and was discovered on July 11, 2022. The incident affected 2 Maine residents, who were notified on October 31, 2022. Arvest Bank offered one year of identity theft protection services to the individuals affected.
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.