New York City Bar Association
bd_1ca1ed92c9a697ae · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cl0p on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
New York City Bar Association
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 13, 2023
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Maine State AGbd_234bf5e43111fad82023-11-17 · +308dCandidate
- Massachusetts State AGbd_26a2b94754eed4972023-11-17 · +308dVerified by operator
- Vermont State AGbd_d703ea02ac6ee1122023-11-17 · +308dVerified
- Montana State AGbd_e3fcac51365005c02023-11-17 · +308dVerified
Show 1 more filing ↓Show fewer ↑up to 312d gap
- New Hampshire State AGbd_2dd6308b7df859b62023-11-21 · +312dVerified by operator
Filing propagation · 5 filings · 5 states
View merged incident ↗Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.