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

HIGHTOWER HOLDING, LLC — January 2026 breach

Clustered 9 filings across 8 jurisdictions · filing window Mar 1, 2026 → Mar 25, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

131,483

First → last filing

Mar 1, 2026 → Mar 25, 2026

Merge confidence

100%

incident inc_e0c23c26c79f4e5a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Jan 8, 2026–Jan 20, 2026, discovered Jan 9, 2026 — the first regulatory filing landed 51 days later (flagged late). 131,483 individuals reported across the linked filings. Data reported: Government ID, Authentication, Identity (basic), and 2 more. Notifications rolled out on a 24-day schedule across 9 filings beginning Mar 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
51days

Discovered → first regulatory filing

Discovery variance
62days

Range of discovered_at dates across filings

Filing span
24days

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 bdayWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 73dMassachusetts⏱ MA AG >30dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Jan 8, 2026breach begins
Jan 9, 2026discovered · members disagree
notification delay · 51 days
Mar 1, 2026first filing
Mar 25, 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. MAR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 23WA AGWA AG notice7,528 WA residents+22d
  3. MAR 23NH AGNH AG notice975 NH residents+22d
  4. MAR 23IN AGIN AG noticestates nationwide total 131,483+22d
  5. MAR 23ME AGME AG noticestates nationwide total 131,483+22d
  6. MAR 23VT AGVT AG notice225 VT residents+22d
  7. MAR 24ME AGME AG noticestates nationwide total 131,483+23d
  8. MAR 24MA AGMA AG notice4,888 MA residents+23d
  9. MAR 25TX AGTX AG noticemost recent · states nationwide total 131,483+24d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 8, 2026 – Jan 20, 2026
WA AG
Discovered
Jan 9, 2026WA AG + NH AG + ME AG +2Mar 12, 2026IL AG + TX AGfilings disagree on discovery
Data types
Authentication · Financial account · Identity (basic) · Government ID · PII
IL AG + WA AG + NH AG +4
Attack vector
Unauthorized Access
WA 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)

131,483

Sum of filed state slices

16,940· 12.9% of stated

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

US131,483
WA7,528
MA4,888
ME1,557
IN1,204
NH975
TX563
VT225

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 filing9 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 Jun 12, 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

24 days

Cadence

~1 / 3d

vs. multi-state median

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