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

Confirmed8 filings · 6 statesUnverified claimConfirmedEnforcedcl0phigh sensitivity

Merged incident · 8 filings

City National Bank of Florida — May 2023 breach

Clustered 8 filings across 7 jurisdictions · filing window Jun 30, 2023 → Aug 7, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

Affected · reported

40,670

First → last filing

Jun 30, 2023 → Aug 7, 2023

Merge confidence

100%

incident inc_ea9a0fe3bea9483c · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 29, 2023–May 30, 2023, discovered Jun 3, 2023 — the first regulatory filing landed 27 days later (flagged late). 40,670 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 38-day schedule across 7 filings beginning Jun 30, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

27days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

Same day

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

38days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

May 29, 2023breach begins

Jun 3, 2023discovered

notification delay · 27 days

Jun 30, 2023first filing

Aug 7, 2023most recent filing

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

Member cascade — every filing about this breach

JUN 30MT AGMT AG noticefirst filing · 4 MT residentsoperator-confirmedday 0
JUN 30VT AGVT AG noticeno count statedoperator-confirmedday 0
JUN 30MA AGMA AG notice100 MA residentsoperator-confirmedday 0
JUN 30IN AGIN AG noticestates nationwide total 40,670operator-confirmedday 0
JUN 30Leak sitecl0p postattacker claim · unverifiedday 0
JUN 30ME AGME AG noticestates nationwide total 36,306operator-confirmedday 0
JUL 31NH AGNH AG notice18 NH residentsauto-linked+31d
AUG 7ME AGME AG noticemost recent · states nationwide total 40,670operator-confirmed+38d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: May 29, 2023 – May 30, 2023
Discovered: Jun 3, 2023· 5d undetected
Data types: Financial account · Financial credentials · Identity (basic) · Government ID
Attack vector: Unauthorized Access

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)

40,670

Sum of filed state slices

158· 0.4% of stated

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

US40,670

MA100

IN21

NH18

ME15

MT4

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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: human
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Aug 26, 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

38 days

Cadence

~1 / 5.4d

vs. multi-state median

4.2× slower

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.