GLOBALClaimed by Cl0pFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Jan 13, 2023bd_1ca1ed92c9a697ae
New York City Bar Association
Clustered 3 filings across 3 jurisdictions · filing window Jan 13, 2023 → Nov 17, 2023. View entity profile → Other incidents for this victim →
incident inc_8b5a389d69dc4050 · 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.
Government ID · Identity (basic) · Financial account
ME VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 2, 2022 → Dec 24, 2022
When the intrusion reportedly occurred, per the linked filings
New York City Bar Association
Oct 18, 2023
Reported by MAINE AG, VERMONT AG filings
The New York City Bar Association reported an external system breach (hacking) occurring between December 2 and 24, 2022, discovered on October 18, 2023. The incident affected 27,226 individuals, including 7 Maine residents. Acquired data included names, financial account numbers, and credit/debit card numbers with security codes. The Association provided written notification on November 17, 2023, and offered 12 months of identity protection services through IDX.
Affected (this filing):
The New York City Bar Association notified consumers of a cybersecurity incident occurring between Dec 2-24, 2022. Unauthorized access resulted in the removal of files containing names. The incident was discovered on Oct 18, 2023. The organization offered free credit monitoring and identity theft protection services to affected individuals.
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.