GLOBALMalwareTelecom & MediaInformationRansomwareYanluowangRansom DemandedActor NamedMedium
Cincinnati bell didn’t pay the ransom
bd_1c2f364fc05820c0 · schema v1 · pii pii-v1
Full breach record for Cincinnati bell didn’t pay the ransom →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Yanluowang 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: TelecommunicationDiscovered: 2022-07-02
Source: Ransomware.live
Tracked as a single-filing incident — the only disclosure on record for this event so far.Unverified claimView incident
No regulatory filing corroborates this yet. If an SEC 8-K, state-AG notice, or victim statement lands, DisclosureLens will merge it into an incident and link it here.
Source provenance
- Source URL
- https://www.ransomware.live/id/Q2luY2lubmF0aSBiZWxsIGRpZG7igJl0IHBheSB0aGUgcmFuc29tQHlhbmx1b3dhbmc=
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Jul 2, 2022
- Raw hash
- 9a555a2176d4d6e97274b4945d16678e2e44457f835a6b0133cc4bce1ebd5a38
Reporting entity
- Name
- yanluowang
Victim entity
- Name
- Cincinnati bell didn’t pay the ransomnorm: cincinnati bell didn t pay the ransom
- Industry
- Telecom & Mediallm
What this source establishes
- Source ceiling
- A leak-site claim can't tell us: discovery date · materiality · notification · affected count · confirmed data types · compliance clock. These stay blank until a regulatory filing or victim disclosure lands.
- Attack vector
- Ransomware· yanluowang
- Threat actor
- YanluowangExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.