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

U-Haul International, Inc. — November 2021 breach

Clustered 11 filings across 11 jurisdictions · filing window Sep 9, 2022 → Sep 12, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

2,195,831

First → last filing

Sep 9, 2022 → Sep 12, 2022

Merge confidence

100%

incident inc_a4f31a55f3514cde · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Nov 4, 2021–Apr 5, 2022, discovered Jul 12, 2022 — the first regulatory filing landed 59 days later. 2,195,831 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
57days

Range of discovered_at dates across filings

Filing span
3days

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 clocksHawaii✓ HI CRA notice dueOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 39dSouth Carolina✓ SC CRA notice dueMaine✓ ME AG ≤30d · 2dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 4, 2021breach begins
Jul 12, 2022discovered · members disagree
notification delay · 59 days
Sep 9, 2022first filing
Sep 12, 2022most 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. SEP 9MT AGMT AG noticefirst filing · 5,568 MT residentsday 0
  2. SEP 9DE AGDE AG notice4,903 DE residentsday 0
  3. SEP 9MA AGMA AG notice37,202 MA residentsday 0
  4. SEP 9WA AGWA AG notice61,770 WA residentsday 0
  5. SEP 9HI AGHI AG notice4,608 HI residentsday 0
  6. SEP 9OR AGOR AG noticestates nationwide total 2,195,831day 0
  7. SEP 9CA AGCA AG noticeno count statedday 0
  8. SEP 9IN AGIN AG noticestates nationwide total 2,195,831day 0
  9. SEP 9SC AGSC AG notice36,165 SC residentsday 0
  10. SEP 9ME AGME AG noticestates nationwide total 2,195,831day 0
  11. SEP 12NH AGNH AG noticemost recent · 7,948 NH residents+3d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 5, 2021 – Apr 5, 2022
MT AG
Discovered
Jul 12, 2022DE AG + WA AG + NH AGAug 1, 2022CA AG + SC AGSep 7, 2022MT AG + HI AG + OR AG +1filings disagree on discovery
Data types
Identity (basic) · Government ID
MT AG + DE AG + WA AG +6
Attack vector
Unauthorized Access
MT 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,195,831

Sum of filed state slices

201,902· 9.2% of stated

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

US2,195,831
WA61,770
MA37,202
IN36,557
SC36,165
NH7,948
ME7,181
MT5,568
DE4,903
HI4,608

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 filing11 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

3 days

Cadence

~1 / 0.3d

vs. multi-state median

2.7× faster

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.