Baughman
bd_13a73dbadbcb7e9b · schema v1 · pii pii-v1
Full breach record for Baughman →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x 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: LockBit 3.x 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
Post text · scraped from the leak site
In 1930, Clyde Baughman founded Baughman (pronounced BOFF-man) with the goal of creating an honest, reliable company that would make a difference. When Clyde planted the company’s roots in Wichita, he had bigger ambitions than to simply become succes...
Source provenance
- Source URL
- https://www.ransomware.live/id/YmF1Z2htYW5jby5jb21AbG9ja2JpdDM=
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Apr 7, 2023
- Raw hash
- 7262662a2681753daaabc513a00b34a6c8d2a09011b7938f21f6bb2d922f26c9
Reporting entity
- Name
- lockbit3norm: lockbit_3
Victim entity
- Name
- Baughmannorm: baughman
- Domain
- baughmanco.com
- Industry
- Manufacturing
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· lockbit_3
- Threat actor
- LockBit 3.xExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.