GLOBALClaimed by Cl0pFirst sightinglinked via shared-victim match · 100%
Posted to leak site Jun 29, 2023bd_2a6a38a4fce50e7f
Clustered 4 filings across 3 jurisdictions · filing window Jun 29, 2023 → Jun 12, 2024. View entity profile → Other incidents for this victim →
incident inc_cfa39fa720854cca · 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 WA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 27, 2023 → May 31, 2023
When the intrusion reportedly occurred, per the linked filings
May 31, 2023
Reported by WASHINGTON AG filing
Home - Kirkland & Ellis LLP
Jan 23, 2024
Reported by MAINE AG filing
Kirkland & Ellis LLP reported a data breach affecting 155 Maine residents, which occurred between May 27, 2023, and May 31, 2023. The breach was discovered on January 23, 2024, and consumers were notified on May 28, 2024. The firm offered 24 months of identity protection and credit monitoring services through Experian. The specific details of the breach and the types of information compromised were not specified in the notification.
Kirkland & Ellis LLP, a business sector entity reported a other incident to the Washington Attorney General. The organization became aware of the incident on 2023-05-31 and filed notice on 2024-06-12. 810 Washington residents were affected. 378 days elapsed between awareness and notification. 4 days to identify the breach. 0 days to contain the breach.
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): 155
Affected (this filing): 810