DisclosureLens
GLOBALMalwareInformationRansomwareCl0pRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

cgm

bd_247af53703d72860 · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Jan 5, 2023

To disclose

—

Affected

Not disclosed

Linked

15 records

Confidence

50%

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.

Group activity: Not FoundDiscovered: 2023-01-05

Source: Ransomware.live

Post text · scraped from the leak site

CGM, LLC

Incident timeline — mostly unverified

? — ?

Breach window unknown

Jan 5, 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

This leak-site claim is one of 15 records about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (10) · sorted by filing gap

Show 6 more filings ↓up to 406d gap

Showing first 10 of 14 linked disclosures.

Filing propagation · 10 filings · 9 states

View merged incident ↗

Pattern: first filing Jun 7 (OR), last Feb 15 (SC) — a 253-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 14 — the full spread may be wider.

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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.