cgm
bd_247af53703d72860 · 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
CGM, LLC
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 5, 2023
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Oregon State AGbd_1a2025acb7c94a972023-06-07 · +153dVerified
- Washington State AGbd_2735fea22890668d2023-06-07 · +153dVerified
- Indiana State AGbd_5c2b629e07a673442023-06-07 · +153dVerified
- Vermont State AGbd_a22f66366c7582892023-06-07 · +153dVerified
Show 6 more filings ↓Show fewer ↑up to 406d gap
- California State AGbd_acd5ed6139e7a5a22023-06-07 · +153dVerified
- New Hampshire State AGbd_51a69c1950f8dead2023-06-12 · +158dVerified
- New Hampshire State AGbd_17cf47586e44d9732024-02-14 · +405dVerified
- Montana State AGbd_6c917269085812802024-02-14 · +405dVerified
- California State AGbd_edabe55eaf55e0422024-02-14 · +405dVerified
- South Carolina State AGbd_59bc55eb0803b05c2024-02-15 · +406dVerified
Showing first 10 of 13 linked disclosures.
Filing propagation · 11 filings · 8 states
View merged incident ↗Pattern: first filing Jan 5, last Feb 15 (SC) — a 406-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 13 — the full spread may be wider.
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.