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

Doxim — December 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window May 31, 2024 → Dec 16, 2024. View entity profile → Other incidents for this victim →

✓ data types, discovery date agreeMerge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

31,848

First → last filing

May 31, 2024 → Dec 16, 2024

Merge confidence

100%

incident inc_3cf421a163724eae · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Dec 25, 2023–Dec 30, 2023, discovered Dec 30, 2023 — the first regulatory filing landed 153 days later (flagged late). 31,848 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 199-day schedule across 8 filings beginning May 31, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
153days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
199days

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 bdayLeak gap✗ Leak >180dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 25, 2023breach begins
Dec 30, 2023discovered
notification delay · 153 days
May 31, 2024first filing
Dec 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. MAY 31VT AGVT AG noticefirst filing · no count statedday 0
  2. MAY 31IN AGIN AG notice30,433 IN residentsday 0
  3. MAY 31DE AGDE AG noticeno count statedday 0
  4. JUN 13MT AGMT AG notice170 MT residents+13d
  5. JUN 14CA AGCA AG noticeno count stated+14d
  6. DEC 11WA AGWA AG notice943 WA residents+194d
  7. DEC 16OR AGOR AG noticeno count stated+199d
  8. DEC 16NH AGNH AG noticemost recent · 302 NH residents+199d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 25, 2023
IN AG
Discovered
Dec 30, 2023· 5d undetected
VT AG + DE AG + MT AG +4
Data types
Financial account · Identity (basic) · Government ID
VT AG + DE AG + MT 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.

Affected residents by state

per-state reported counts

IN30,433
WA943
NH302
MT170

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing8 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 Aug 9, 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

199 days

Cadence

~1 / 28.4d

vs. multi-state median

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