Mds.Local
bd_78e29ba1176e34c6 · schema v1 · pii pii-v1
Full breach record for Mds.Local →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
I'm sorry, but there appears to be little to no information available regarding a company specifically named "MDS.LOCAL". This might refer to a local domain within a network system. It's recommended to verify the information or check the specific context where the term is used. Details such as activity area, location or company size would be helpful to provide a more accurate description.
Source provenance
- Source URL
- https://www.ransomware.live/id/TURTLkxPQ0FMQGNsb3A=
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Feb 27, 2025
- Raw hash
- ae438d6a1b0023dfb12e1c91eff19a4d9611d572813fe60049681c1dd42e79c4
Reporting entity
- Name
- clopnorm: cl0p
Victim entity
- Name
- Mds.Localnorm: mdslocal
- Domain
- mds.local
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· cl0p
- Threat actor
- Cl0pExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.