Confirmed breach. Intrusion Jul 1, 2023–Sep 25, 2023, discovered Sep 25, 2023 — the first regulatory filing landed 336 days later (flagged late). 3,555 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 clocksVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
3,555
Data types
3
PII · Identity (basic) · Government ID
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jul 31, 2023
When the intrusion reportedly occurred, per the linked filings
56 days
Breach discovered
Sep 25, 2023
Reported by VERMONT AG filing
336 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Legacy Capital Advisors LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2023-07-31 and was reported on 2024-08-26. 2 Indiana residents were affected. 3,555 individuals affected in total.
Legacy Capital Advisors LLC notified consumers of a cybersecurity incident where an unauthorized actor accessed employee email accounts starting in late July 2023. The breach was discovered on September 25, 2023. The incident likely involved PII and government IDs. Legacy engaged forensic specialists, secured accounts, and offered credit monitoring.
VT AG >45 bday
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.