Ohio History Connection
bd_15e2608dae4ada29 · schema v1 · pii pii-v1
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
The Ohio History Fund was created to support the preservation and sharing of Ohio's heritage by funding local, regional, and statewide projects, programs, and events related to the broad sweep of the state's history and pre-history.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 27, 2023
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitelockbit_3bd_cc0d34f222cd3fd22023-07-03 · +24dVerified by operator
Regulatory filings (3) · sorted by filing gap
- Maine State AGbd_67ba20458f527e6b2023-08-23 · +27dCandidate
- New Hampshire State AGbd_7a49cabfe1afd57c2023-08-23 · +27dVerified by operator
- Vermont State AGbd_f6e7484647a602c92023-08-23 · +27dVerified by operator
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Jul 27, last Aug 23 (VT) — a 27-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.