DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddragonforcehigh sensitivity
Merged incident · 9 filings

FIVE STATES ENERGY COMPANY, L.L.C. — February 2026 breach

Clustered 9 filings across 8 jurisdictions · filing window Feb 12, 2026 → Jul 17, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

2,251

First → last filing

Feb 12, 2026 → Jul 17, 2026

Merge confidence

100%

incident inc_c18d8d8fc4e64fc3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Feb 12, 2026, discovered Feb 12, 2026 — the first regulatory filing landed 42 days later (flagged late). 2,251 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 155-day schedule across 7 filings beginning Feb 12, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
42days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
42days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
155days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMassachusetts✗ MA AG >90dLeak gap⏱ Leak >30dVermont⏱ VT AG >14 bdayMaine⏱ ME AG >30d · 49dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 12, 2026breach begins
Feb 12, 2026discovered
notification delay · 42 days
Mar 26, 2026first filing
Jul 17, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. FEB 12Leak sitedragonforce postfirst filing · attacker claim · unverifiedday 0
  2. FEB 19Leak sitedragonforce postattacker claim · unverified+8d
  3. MAR 26IN AGIN AG noticestates nationwide total 2,251+42d
  4. MAR 26NE AGNE AG noticeno count stated+42d
  5. APR 2NH AGNH AG notice10 NH residents+49d
  6. APR 2VT AGVT AG noticeno count stated+49d
  7. APR 2ME AGME AG noticestates nationwide total 2,251+49d
  8. APR 6TX AGTX AG noticestates nationwide total 2,251+53d
  9. JUL 17MA AGMA AG noticemost recent · 26 MA residents+155d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 12, 2026
IN AG
Discovered
Feb 12, 2026
NE AG + NH AG + VT AG +3
Data types
Financial account · Identity (basic) · Government ID · PII
NE AG + NH AG + VT AG +3
Attack vector
Unauthorized Access
NE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

2,251

Sum of filed state slices

704· 31.3% of stated

69% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US2,251
TX653
MA26
NH10
ME9
IN6

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

155 days

Cadence

~1 / 19.4d

vs. multi-state median

19.4× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.