Clustered 2 filings across 2 jurisdictions · filed Dec 30, 2025. View entity profile → Other incidents for this victim →
incident inc_41fc4fdae44544db · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
Identity (basic) · Government ID · Financial account
IN VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 7, 2025
When the intrusion reportedly occurred, per the linked filings
Oct 7, 2025
Reported by VERMONT AG filing
Appalachian Community Federal Credit Union reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-07 and was reported on 2025-12-30. 36 Indiana residents were affected. 30,797 individuals affected in total.
Affected (this filing): 30,797
Appalachian Community Federal Credit Union notified consumers of a data event discovered on October 7, 2025. The incident involved unauthorized access to its network, resulting in the exfiltration of files containing names, Social Security numbers, and financial account information. The Credit Union took its network offline, engaged forensic specialists, reset passwords, and reported the incident to federal law enforcement. Affected individuals are offered credit monitoring services.
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.