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.
Clustered 3 filings across 2 jurisdictions · filing window Jul 3, 2023 → Aug 23, 2023. View entity profile → Other incidents for this victim →
incident inc_de7051b438fb484d · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 1, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 1, 2023
Reported by VERMONT AG filing
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.
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.
Ohio History Connection suffered a ransomware attack in early July 2023. Cybercriminals encrypted data servers and demanded a multi-million dollar ransom. The breach exposed names, addresses, and SSNs of ~7,600 current/former employees and vendors, plus check images. OHC notified the FBI, engaged forensic consultants, and offered one year of credit monitoring.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 7,600