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

HUB INTERNATIONAL LIMITED — December 2022 breach

Clustered 10 filings across 10 jurisdictions · filing window Aug 11, 2023 → Aug 14, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

479,261

First → last filing

Aug 11, 2023 → Aug 14, 2023

Merge confidence

100%

incident inc_db88d7bdfa604fb0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Dec 1, 2022–Jan 31, 2023, discovered Jan 17, 2023 — the first regulatory filing landed 206 days later (flagged late). 479,261 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
206days

Discovered → first regulatory filing

Discovery variance
191days

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 clocksVermont✗ VT AG >45 bdayWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 206dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 15dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Dec 1, 2022breach begins
Jan 17, 2023discovered · members disagree
notification delay · 206 days
Aug 11, 2023first filing
Aug 14, 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. AUG 11VT AGVT AG noticefirst filing · no count statedday 0
  2. AUG 11WA AGWA AG notice31,755 WA residentsday 0
  3. AUG 11NH AGNH AG notice688 NH residentsday 0
  4. AUG 11MT AGMT AG notice18,907 MT residentsday 0
  5. AUG 11IN AGIN AG noticestates nationwide total 479,261day 0
  6. AUG 11OR AGOR AG noticestates nationwide total 479,261day 0
  7. AUG 11MA AGMA AG notice21,267 MA residentsday 0
  8. AUG 11ME AGME AG noticestates nationwide total 479,261day 0
  9. AUG 11CA AGCA AG noticeno count statedday 0
  10. AUG 14SC AGSC AG noticemost recent · 13,597 SC residents+3d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 1, 2022 – Jan 31, 2023
VT AG
Discovered
Jan 17, 2023VT AG + WA AG + NH AG +3Jul 27, 2023OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + WA AG + NH AG +5
Attack vector
Unauthorized Access
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)

479,261

Sum of filed state slices

93,568· 19.5% of stated

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

US479,261
WA31,755
MA21,267
MT18,907
SC13,597
ME4,980
IN2,374
NH688

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

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.