Confirmed breach. Intrusion Feb 12, 2026, discovered Feb 12, 2026 — the first regulatory filing landed 42 days later. 2,251 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.
Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
2,251
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 12, 2026
When the intrusion reportedly occurred, per the linked filings
Five States Energy Company LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-12 and was reported on 2026-03-26. 6 Indiana residents were affected. 2,251 individuals affected in total.
Affected (this filing): 2,251
Leak >30d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
Five States Energy Company, L.L.C. notified the New Hampshire Attorney General on April 2, 2026, of a network compromise detected on February 12, 2026. The incident affected 10 New Hampshire residents, exposing names, SSNs, DOBs, contact info, and bank account numbers. The company engaged forensic experts, notified law enforcement, and provided 24 months of credit monitoring via CyberScout. The incident is contained.
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.