NuVista Federal Credit Union reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-03. The breach occurred on 3/9/2020. 37 Montana residents were affected.
Affected (this filing): 37
Clustered 2 filings across 2 jurisdictions · filing window Dec 3, 2020 → Dec 5, 2020. View entity profile → Other incidents for this victim →
incident inc_bc8671f7a1824cab · merge_method human · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 9, 2020
When the intrusion reportedly occurred, per the linked filings
Nov 3, 2020
Reported by MAINE AG filing
NuVista Federal Credit Union reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-03. The breach occurred on 3/9/2020. 37 Montana residents were affected.
Affected (this filing): 37
Nuvista Federal Credit Union reported a data breach to the Maine Attorney General, stating that an external system breach (hacking) occurred on March 9, 2020. The breach was discovered on November 3, 2020. The breach affected 10 Maine residents, and the compromised information included names in combination with financial account numbers or credit/debit card numbers. Nuvista began notifying affected consumers in writing on December 3, 2020, and offered 12 months of complimentary credit monitoring through Experian.
Affected (this filing): 10
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.