GLOBALMalwareRansomwareLeaktheanalystRansom DemandedActor NamedMedium
9 Cuz F5 has caused
bd_3ff4e0653c70f8fe · schema v1 · pii pii-v1
Full breach record for 9 Cuz F5 has caused →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Leaktheanalyst 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: 2022-01-01
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/OSBDdXogRjUgaGFzIGNhdXNlZEBsZWFrdGhlYW5hbHlzdA==
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Jan 1, 2022
- Raw hash
- 8a9816e212c4d6c2f0f36cfb0c93a1e521611bbd8a24644d728c2cfb62a671a8
Reporting entity
- Name
- leaktheanalyst
Victim entity
- Name
- 9 Cuz F5 has causednorm: 9 cuz f5 has caused
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· leaktheanalyst
- Threat actor
- LeaktheanalystExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.