GLOBALMalwareRansomwareCl0pRansom DemandedActor NamedMedium
Sji.Local
bd_074d5454faef74b1 · schema v1 · pii pii-v1
Full breach record for Sji.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.
Group activity: Not FoundDiscovered: 2025-02-27
Source: Ransomware.live
Post text · scraped from the leak site
I'm sorry, but there doesn't seem to be any reputable information available on a company named "SJI.LOCAL". It's possible that there may be a misunderstanding or typo in the company name. Please double-check the company's name.
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/U0pJLkxPQ0FMQGNsb3A=
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
- 80cdacb46a2b7ebc66c9cf0c0102c4071e540b99e02947f364a501d6100d5b9a
Reporting entity
- Name
- clopnorm: cl0p
Victim entity
- Name
- Sji.Localnorm: sjilocal
- Domain
- sji.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.