jaykal
bd_6d342961b79cc941 · schema v1 · pii pii-v1
Full breach record for jaykal →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Lockbit2 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: Lockbit2 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
Source provenance
- Source URL
- https://www.ransomware.live/id/amF5a2FsQGxvY2tiaXQy
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- May 17, 2022
- Raw hash
- 8b2b281e5b3dbf2b7e2172a4f108be3b7abb269835fb3aec593c8508680b52c5
Reporting entity
- Name
- lockbit2
Victim entity
- Name
- jaykal
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· lockbit2
- Threat actor
- Lockbit2ExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.