GLOBALClaimed by Cl0pFirst sighting
Posted to leak site Jun 30, 2023bd_570679dab11b4556
City National Bank of Florida
Clustered 3 filings across 3 jurisdictions · filing window Jun 30, 2023 → Aug 7, 2023. View entity profile → Other incidents for this victim →
incident inc_ea9a0fe3bea9483c · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 29, 2023 → May 30, 2023
When the intrusion reportedly occurred, per the linked filings
Jun 3, 2023
Reported by NEW HAMPSHIRE AG, MAINE AG filings
City National Bank of Florida
City National Bank of Florida (CNBF) issued a supplemental notice regarding a MOVEit Transfer zero-day vulnerability incident. Unauthorized access occurred May 29-30, 2023. CNBF discovered the incident on June 3, 2023. Data exposed included names, DOB, SSNs, and bank account numbers. CNBF notified 18 New Hampshire residents and offered credit monitoring. The filing is a follow-up to an initial June 30, 2023 notification.
City National Bank of Florida experienced an external system breach between May 29 and May 30, 2023, discovered on June 3, 2023. The incident compromised names and financial account or card numbers with associated security codes or PINs for 40,670 individuals. The bank began notifying affected individuals on June 30, 2023, and offered 24 months of identity protection services through IDX.
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.
Affected (this filing): 18
Affected (this filing): 40,670