tokyo-plant.co....
bd_db262cba99fa84c0 · schema v1 · pii pii-v1
Full breach record for tokyo-plant.co.... →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/dG9reW8tcGxhbnQuY28uLi4uQGxvY2tiaXQy
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Apr 11, 2022
- Raw hash
- c50c1826f1f2eda9bb7b0bcd928be330b49b539d1575e026ae0edf709d64238b
Reporting entity
- Name
- lockbit2
Victim entity
- Name
- tokyo-plant.co....norm: tokyo plantco
- Industry
- Manufacturingllm
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.