Ohio History Connection
ent_087bc0c067c2a803377b06cb
Disclosures
5
State AG · Leak Site · 3 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
7,600
nationwide · State AG VT
Leak-site claims
3
unverified actor claims
Identity resolution
- Canonical name
- Ohio History Connection
- Normalized
- ohio history connection— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- ohiohistory.org
Disclosure history (5)newest first
- Vermont State AGas victim2023-08-23
Ohio History Connection suffered a ransomware attack in early July 2023, encrypting internal data servers. Cybercriminals demanded a ransom in the millions. The breach potentially exposed names, addresses, and Social Security numbers of 7,600 current and former employees, vendors, and donors. OHC notified the FBI, retained forensic consultants, and is offering credit monitoring. Systems have been migrated to the cloud with enhanced security measures.
- GLOBALLeak Siteas victim2023-07-27
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.
- GLOBALLeak Siteas victim2023-07-26
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.
- GLOBALLeak Siteas victim2023-07-03
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.
- Oregon State AGas victim2020-09-01
Ohio History Connection reported a data breach to the Oregon Attorney General. The breach was reported on 2020-09-01. The breach occurred during 2/7/2020 - 5/20/2020. The breach was discovered on 5/20/2020. Notice was sent on 8/12/2020.