DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed12 records · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforceddunghillhigh sensitivity
Merged incident · 12 records

The Cannon Corporation — January 2023 breach

Clustered 12 records across 8 jurisdictions: 10 filings and 2 leak-site claims · filing window Aug 19, 2024 → Sep 16, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 records

States

8

Affected · reported

13,049

First → last dated filing

Aug 19, 2024 → Sep 16, 2024

Merge confidence

100%

incident inc_4a455fa5ac164872 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Jan 19, 2023–Jan 25, 2023, discovered Jan 19, 2023. 13,049 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 28-day schedule across 9 dated filings beginning Aug 19, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
6days

Range of discovered_at dates across filings

Filing span
28days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 572dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 19, 2023breach begins
Jan 19, 2023discovered · members disagree
Aug 19, 2024first dated filing
Sep 16, 2024most 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 and leak-site claim in this incident

  1. FEB 11Leak siteavoslocker postfirst record · attacker claim · unverifiedday 0
  2. SEP 26Leak sitedunghill postattacker claim · unverified+227d
  3. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  4. AUG 19VT AGVT AG noticeno count stated+555d
  5. AUG 19MA AGMA AG notice843 MA residents+555d
  6. AUG 19ME AGME AG noticestates nationwide total 13,049+555d
  7. AUG 19NH AGNH AG notice21 NH residents+555d
  8. AUG 19CA AGCA AG noticeno count stated+555d
  9. AUG 19IN AGIN AG noticestates nationwide total 13,049+555d
  10. AUG 19MT AGMT AG notice7 MT residents+555d
  11. SEP 16MA AGMA AG notice309 MA residents+583d
  12. SEP 16NH AGNH AG noticemost recent · 28 NH residents+583d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 19, 2023 – Jan 25, 2023
VT AG
Discovered
Jan 19, 2023IL AGJan 25, 2023VT AG + ME AG + NH AG +2filings disagree on discovery
Data types
Identity (basic) · Government ID
VT AG + ME AG + NH AG +3
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)

13,049

Sum of filed state slices

1,009· 7.7% of stated

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

US13,049
MA843
IN113
NH28
ME18
MT7

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Sep 29, 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

28 days

Cadence

~1 / 3.5d

vs. multi-state median

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