DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed10 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 10 filings

ENSTAR (US) INC. — May 2023 breach

Clustered 10 filings across 8 jurisdictions · filing window Nov 20, 2023 → Dec 21, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

64,934

First → last filing

Nov 20, 2023 → Dec 21, 2023

Merge confidence

100%

incident inc_2e397c943e894751 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion May 29, 2023–May 31, 2023, discovered May 31, 2023 — the first regulatory filing landed 173 days later (flagged late). 64,934 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 31-day schedule across 10 filings beginning Nov 20, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
173days

Discovered → first regulatory filing

Discovery variance
143days

Range of discovered_at dates across filings

Filing span
31days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 173 days
Nov 20, 2023first filing
Dec 21, 2023most 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. NOV 20VT AGVT AG noticefirst filing · no count statedday 0
  2. NOV 20MA AGMA AG notice240 MA residentsday 0
  3. NOV 20ME AGME AG noticestates nationwide total 64,934day 0
  4. NOV 20NH AGNH AG notice105 NH residentsday 0
  5. NOV 20DE AGDE AG noticeno count statedday 0
  6. NOV 20MT AGMT AG notice53 MT residentsday 0
  7. NOV 20CA AGCA AG noticeno count statedday 0
  8. NOV 21SC AGSC AG notice1,274 SC residents+1d
  9. DEC 19VT AGVT AG noticeno count stated+29d
  10. DEC 21CA AGCA AG noticemost recent · no count stated+31d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2023 – May 31, 2023
VT AG
Discovered
May 31, 2023DE AG + MT AG + VT AGOct 21, 2023VT AG + ME AG + SC AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
VT AG + ME AG + NH AG +5
Attack vector
Unauthorized Access· CL0P
VT 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)

64,934

Sum of filed state slices

1,741· 2.7% of stated

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

US64,934
SC1,274
MA240
NH105
ME69
MT53

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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
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

31 days

Cadence

~1 / 3.4d

vs. multi-state median

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