DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
SEC 8-KState AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

Evolve Bank & Trust — February 2024 breach

Clustered 9 filings across 9 jurisdictions · filing window Jul 1, 2024 → Jul 8, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

7,640,112

First → last filing

Jul 1, 2024 → Jul 8, 2024

Merge confidence

100%

incident inc_a7879cfa3e4145b2 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Feb 1, 2024–May 31, 2024, discovered May 29, 2024 — the first regulatory filing landed 33 days later. 7,640,112 individuals reported across the linked filings. Data reported: Government ID, PII, Financial account, and 1 more. Notifications rolled out on a 7-day schedule across 9 filings beginning Jul 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
33days

Discovered → first regulatory filing

Discovery variance
27days

Range of discovered_at dates across filings

Materiality delta
6days

Discovery to SEC materiality determination

SEC filing delay
0days

Materiality determination to SEC 8-K filing

Filing span
7days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksMaine⏱ ME AG >30d · 40dWashington⏱ WA AG >30dOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 40dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 1, 2024breach begins
May 29, 2024discovered · members disagree
notification delay · 33 days
Jul 1, 2024first filing
Jul 8, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 1SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUL 8IN AGIN AG noticestates nationwide total 7,640,112+7d
  3. JUL 8OR AGOR AG noticestates nationwide total 64,904+7d
  4. JUL 8ID AGID AG notice29,728 ID residents+7d
  5. JUL 8NH AGNH AG noticeno count stated+7d
  6. JUL 8ME AGME AG noticestates nationwide total 7,640,112+7d
  7. JUL 8MT AGMT AG notice38,740 MT residents+7d
  8. JUL 8CA AGCA AG noticeno count stated+7d
  9. JUL 8WA AGWA AG noticemost recent · states nationwide total 275,716+7d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 9, 2024
IN AG
Discovered
May 29, 2024OR AG + ID AG + NH AG +4Jun 25, 2024SEC 8-Kfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
SEC 8-K + NH AG + MT AG +4
Attack vector
Third-Party / Supply Chain
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

7,640,112

Sum of filed state slices

388,422· 5.1% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US7,640,112
IN149,930
WA149,054
MT38,740
ID29,728
ME20,970

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

7 days

Cadence

~1 / 0.9d

vs. multi-state median

1.1× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.