Mainstreet Credit Union reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-12 and was reported on 2026-05-04. 1 Indiana residents were affected. 4,123 individuals affected in total.
Affected (this filing): 4,123
Clustered 2 filings across 2 jurisdictions · filing window May 4, 2026 → Jun 18, 2026. View entity profile → Other incidents for this victim →
incident inc_4c4cea0e05fd4f12 · merge_method deterministic · confidence 95%
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 12, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 12, 2026
Reported by NEW HAMPSHIRE AG filing
Mainstreet Credit Union reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-12 and was reported on 2026-05-04. 1 Indiana residents were affected. 4,123 individuals affected in total.
Affected (this filing): 4,123
Mainstreet Credit Union notified the NH Attorney General of a cybersecurity event affecting one NH resident. An unauthorized actor accessed an employee's email account between Jan 12-20, 2026, likely via phishing. The actor accessed one resident's name and financial account number. MCU secured the account, engaged forensic investigators, and mailed notification on June 18, 2026.
Affected (this filing): 1
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.