Confirmed breach. Intrusion Mar 30, 2026–Apr 1, 2026, discovered Apr 1, 2026 — the first regulatory filing landed 42 days later. 78 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)
78
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 30, 2026
When the intrusion reportedly occurred, per the linked filings
Florida Reliability Coordinating Council Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-03-30 and was reported on 2026-05-13. 1 Indiana residents were affected. 78 individuals affected in total.
Affected (this filing): 78
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
Florida Reliability Coordinating Council (FRCC) notified the New Hampshire Attorney General on May 13, 2026, of a data event affecting one NH resident. Unauthorized access occurred between March 30 and April 1, 2026, resulting in the copying of names and Social Security numbers. FRCC discovered the activity on April 1, 2026, and notified federal law enforcement. Remediation included system recovery from backups and offering 12 months of credit monitoring via IDX.
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.