Central One Federal Credit Union reported a data breach to the Montana Attorney General. The breach was reported on 2025-11-10. The breach occurred from 08/26/2025 to 08/30/2025. 26 Montana residents were affected.
Affected (this filing): 26
Clustered 2 filings across 2 jurisdictions · filing window Nov 10, 2025 → Nov 12, 2025. View entity profile → Other incidents for this victim →
incident inc_e709add9a5f048ec · 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.
MT TX
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 26, 2025
When the intrusion reportedly occurred, per the linked filings
Oct 17, 2025
Reported by TEXAS AG filing
Central One Federal Credit Union reported a data breach to the Montana Attorney General. The breach was reported on 2025-11-10. The breach occurred from 08/26/2025 to 08/30/2025. 26 Montana residents were affected.
Affected (this filing): 26
Central One Federal Credit Union based in Shrewsbury, Massachusetts, a financial services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-10-17 and reported on 2025-11-12. 274 Texas residents were affected. 66,554 individuals affected in total. Types of information involved: Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Medical Information;Health Insurance Information. Consumers were notified via U.S. Mail.
Affected (this filing): 274
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.