DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed14 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 14 filings

Evolve Bank & Trust — February 2024 breach

Clustered 14 filings across 11 jurisdictions · filing window Jul 8, 2024 → Jul 12, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

11

Affected · reported

7,640,112

First → last dated filing

Jul 8, 2024 → Jul 12, 2024

Merge confidence

100%

incident inc_a7879cfa3e4145b2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. Intrusion Feb 1, 2024–May 31, 2024, discovered May 29, 2024. 7,640,112 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
30days

Range of discovered_at dates across filings

Filing span
4days

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 clocksWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 40dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueCalifornia✓ 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
Jul 8, 2024first dated filing
Jul 12, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUL 8OR AGOR AG noticefirst filing · states nationwide total 64,904day 0
  3. JUL 8ID AGID AG notice29,728 ID residentsday 0
  4. JUL 8NH AGNH AG noticeno count statedday 0
  5. JUL 8WA AGWA AG noticestates nationwide total 275,716day 0
  6. JUL 8IN AGIN AG noticestates nationwide total 7,640,112day 0
  7. JUL 8ME AGME AG noticestates nationwide total 7,640,112day 0
  8. JUL 8ME AGME AG noticeno count statedday 0
  9. JUL 8MT AGMT AG notice38,740 MT residentsday 0
  10. JUL 8MA AGMA AG notice114,211 MA residentsday 0
  11. JUL 8SC AGSC AG notice362,896 SC residentsday 0
  12. JUL 8CA AGCA AG noticeno count statedday 0
  13. JUL 8MT AGMT AG notice1 MT residentsday 0
  14. JUL 12SC AGSC AG noticemost recent · 6,673 SC residents+4d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 9, 2024 – May 31, 2024
OR AG
Discovered
May 29, 2024OR AG + ID AG + NH AG +5May 31, 2024IL AGJun 28, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
ID AG + NH AG + WA AG +5
Attack vector
Unauthorized Access
ID AG

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

865,529· 11.3% of stated

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

US7,640,112
SC362,896
IN149,930
WA149,054
MA114,211
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 filing14 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

4 days

Cadence

~1 / 0.3d

vs. multi-state median

1.5× 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.