Ptidom.Local
bd_ee42bb2eac091d7c · schema v1 · pii pii-v1
Full breach record for Ptidom.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 seems to be a misunderstanding. "PTIDOM.LOCAL" appears to be a type of local domain name used in certain IT system configurations, especially for internal network settings, not a company. It might refer to a specific device or service within a private network. Please provide more specific information so I can give a more accurate description.
Source provenance
- Source URL
- https://www.ransomware.live/id/UFRJRE9NLkxPQ0FMQGNsb3A=
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
- 445596c3f61e56004ebd303bc10c099501d2d2b134caf12a6d77f3f835302627
Reporting entity
- Name
- clopnorm: cl0p
Victim entity
- Name
- Ptidom.Localnorm: ptidomlocal
- Domain
- ptidom.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.