Confirmed breach. Intrusion May 24, 2024–May 25, 2024, discovered May 28, 2024 — the first regulatory filing landed 259 days later. 1,458 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedphobos
Affected (total reported)
1,458
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 24, 2024
When the intrusion reportedly occurred, per the linked filings
Athens County Board of Developmental Disabilities reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-24 and was reported on 2025-02-11. 1 Indiana residents were affected. 1,458 individuals affected in total.
Affected (this filing): 1,458
37 days
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 95%
Athens County Board of Developmental Disabilities experienced a ransomware attack by the Phobos actor group between May 24-25, 2024. The breach affected 4 New Hampshire residents, exposing PHI and PII. ACBDD detected the incident on May 28, 2024, took systems offline, engaged forensic investigators, and notified affected individuals on February 11, 2025, offering credit monitoring services.
Affected (this filing): 4
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.