| Dc
bd_7c60d01fca7611f2 · schema v1 · pii pii-v1
Full breach record for | Dc →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x 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.
Sanctions caution: LockBit 3.x carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
1st batch of data: https://mega.nz/folder/lyUHGAoC#g1Qwh-OSXI4hRJq4l0J-Sw A bad negotiator disappeared at the end of the deal, so we are starting to release huge amount of sensitive data. Starting with 1 GB sample data and many extracted MSSQL...
Source provenance
- Source URL
- https://www.ransomware.live/
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Apr 18, 2024
- Raw hash
- ebf9f984a0a353dbc888c2d6f038a93128ab82f139f09ad6afc3b950adaea453
Reporting entity
- Name
- lockbit3norm: lockbit_3
Victim entity
- Name
- | Dcnorm: dc
- Domain
- dc.gov
- Industry
- Governmentllm
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· lockbit_3
- Threat actor
- LockBit 3.xExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.