Confirmed breach. Intrusion Mar 28, 2025–Apr 10, 2025, discovered Apr 10, 2025 — the first regulatory filing landed 116 days later. 8,020 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.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
8,020
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 28, 2025
When the intrusion reportedly occurred, per the linked filings
Continental Bancorporation reported a data breach to the Indiana Attorney General. The breach occurred on 2025-03-28 and was reported on 2025-08-04. 3 Indiana residents were affected. 8,020 individuals affected in total.
Affected (this filing): 8,020
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
Continental Bancorporation notified the NH Attorney General of a cybersecurity incident involving one New Hampshire resident. An unauthorized party exploited a vulnerability in CrushFTP server software to access the internal network. Personal information (name, SSN, account number, DOB) of one resident was accessed between March 31 and April 10, 2025. Continental contained the network, engaged forensic investigators, and offered credit monitoring.
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.