STU
bd_5d4c0a1e46df41b1 · schema v1 · pii pii-v1
Full breach record for STU →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/U1RVQGxvY2tiaXQy
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- May 16, 2022
- Raw hash
- aa0f3c7e6bd1c1660ebd4d714c2995f3dcfffa26d5fa3086a969e9ad508e8df5
Reporting entity
- Name
- lockbit2
Victim entity
- Name
- STUnorm: stu
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.