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

The Cannon Corporation — January 2023 breach

Clustered 11 filings across 9 jurisdictions · filing window Sep 26, 2023 → Sep 16, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

13,049

First → last filing

Sep 26, 2023 → Sep 16, 2024

Merge confidence

100%

incident inc_4a455fa5ac164872 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 19, 2023–Jan 25, 2023, discovered Jan 19, 2023 — the first regulatory filing landed 560 days later (flagged late). 13,049 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 356-day schedule across 10 filings beginning Sep 26, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
560days

Discovered → first regulatory filing

Discovery variance
6days

Range of discovered_at dates across filings

Leak precedence
310days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
356days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 572dCalifornia✗ 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
notification delay · 560 days
Aug 1, 2024first filing
Sep 16, 2024most 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 26Leak sitedunghill postfirst filing · attacker claim · unverifiedday 0
  2. AUG 1IL AGIL AG noticeno count stated+310d
  3. AUG 19VT AGVT AG noticeno count stated+328d
  4. AUG 19MA AGMA AG notice843 MA residents+328d
  5. AUG 19ME AGME AG noticestates nationwide total 13,049+328d
  6. AUG 19NH AGNH AG notice21 NH residents+328d
  7. AUG 19IN AGIN AG noticestates nationwide total 13,049+328d
  8. AUG 19MT AGMT AG notice7 MT residents+328d
  9. AUG 19CA AGCA AG noticeno count stated+328d
  10. SEP 16MA AGMA AG notice309 MA residents+356d
  11. SEP 16NH AGNH AG noticemost recent · 28 NH residents+356d
  12. 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 claim1 member

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

356 days

Cadence

~1 / 35.6d

vs. multi-state median

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