Confirmed breach. Intrusion Jun 29, 2023–Jul 11, 2023, discovered Sep 10, 2024 — the first regulatory filing landed 9 days later (flagged late). 127,431 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.
Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
127,431
Data types
—
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 29, 2024
When the intrusion reportedly occurred, per the linked filings
73 days
Breach discovered
Sep 10, 2024
Reported by MAINE AG filing
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Wright Moore DeHart Dupuis & Hutchinson LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-29 and was reported on 2024-09-19. 128 Indiana residents were affected. 127,431 individuals affected in total.
Financial services firm Wright, Moore, DeHart, Dupuis & Hutchinson, LLC (WMDDH) reported an external hacking incident that occurred between June 29, 2023, and July 11, 2023. The breach was discovered on September 10, 2024. The incident affected 21 Maine residents. WMDDH began notifying affected individuals on September 19, 2024, and offered 12 months of credit monitoring and identity theft protection services through Experian.
Affected (this filing): 21
Leak >180d
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.