Confirmed breach. Intrusion Aug 8, 2024–Aug 9, 2024, discovered Aug 9, 2024 — the first regulatory filing landed 230 days later (flagged late). 69,938 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)
69,938
Data types
2
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
Aug 8, 2024 → Aug 9, 2024
When the intrusion reportedly occurred, per the linked filings
AOD Federal Credit Union notified consumers of a data breach detected on August 9, 2024. Unauthorized access occurred between August 8-9, 2024, potentially exposing personal information including names and government IDs. The FBI was notified, and forensic investigators were engaged. The credit union offered complimentary credit monitoring services to affected individuals.
VT AG >45 bday
🏎️Indiana State AGMost recentlinked via multistate filing link · 100%
AOD Federal Credit Union reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-08 and was reported on 2025-03-27. 59 Indiana residents were affected. 69,938 individuals affected in total.
Affected (this filing): 69,938
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.