DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed5 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Form Energy — September 2025 breach

Clustered 5 filings across 4 jurisdictions · filing window Oct 28, 2025 → Nov 14, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

663

First → last dated filing

Oct 28, 2025 → Nov 14, 2025

Merge confidence

100%

incident inc_db4efdc2d8b54034 · merged by llm · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filing describes a ransomware attack. Intrusion Sep 16, 2025, discovered Sep 16, 2025. 663 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 17-day schedule across 4 dated filings beginning Oct 28, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Filing span
17days

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.

Regulatory clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 16, 2025breach begins
Sep 16, 2025discovered
Oct 28, 2025first dated filing
Nov 14, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. OCT 22NE AGNE AG noticefiling day not on record · no count stated—
  2. OCT 28NH AGNH AG noticefirst filing · 23 NH residentsday 0
  3. OCT 28MA AGMA AG notice640 MA residentsday 0
  4. OCT 28CA AGCA AG noticeno count statedday 0
  5. NOV 14CA AGCA AG noticemost recent · no count stated+17d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 16, 2025
CA AG
Discovered
Sep 16, 2025
NH AG
Data types
Employment · Financial account · Identity (basic) · Government ID
NE AG + NH AG + CA AG +1
Attack vector
Ransomware
NH AG

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

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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
llm
Confidence
1.00 · above the 0.85 auto-merge floor
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

17 days

Cadence

~1 / 5.7d

vs. multi-state median

2.8× 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.