All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed5 filings · 3 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 5 filings

Arvest Bank — April 2025 breach

Clustered 5 filings across 3 jurisdictions · filing window May 9, 2025 → May 30, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

7,537

First → last filing

May 9, 2025 → May 30, 2025

Merge confidence

100%

incident inc_9f9314a6655540f3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a misconfiguration. Intrusion Apr 24, 2025–Apr 24, 2025, discovered Apr 24, 2025 — the first regulatory filing landed 15 days later. 7,537 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, and PII. Notifications rolled out on a 21-day schedule across 5 filings beginning May 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

15days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

21days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine✓ ME AG ≤30d · 18dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.