GLOBALMalwareTechnologyInformationRansomwareEmbargoRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh
Seclore
bd_067345275e2e58a1 · schema v1 · pii pii-v1
Full breach record for Seclore →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Embargo 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: TechnologyDiscovered: 2026-03-11
Source: Ransomware.live
Post text · scraped from the leak site
At Seclore, we believe that cybersecurity should revolve around what matters most—your data. Traditional security perimeters are no longer enough in today’s hyp... - TOTAL QUANTITY 1.3 TB
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/c2VjbG9yZS5jb21AZW1iYXJnbw==
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Mar 11, 2026
- Raw hash
- b39818a2700f08a93cd3011f313a7632b5d8e0db94959743f29de831eec08697
Reporting entity
- Name
- embargo
Victim entity
- Name
- Seclorenorm: seclore
- Domain
- seclore.com
- Industry
- Technology
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· embargo
- Threat actor
- EmbargoExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.