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

medQ, Inc. — December 2023 breach

Clustered 8 filings across 7 jurisdictions · filing window Feb 23, 2024 → May 29, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

55,917

First → last filing

Feb 23, 2024 → May 29, 2024

Merge confidence

100%

incident inc_4e619398fde0423e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Dec 20, 2023–Dec 26, 2023, discovered Dec 26, 2023 — the first regulatory filing landed 59 days later (flagged late). 55,917 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 2 more. Notifications rolled out on a 96-day schedule across 8 filings beginning Feb 23, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
96days

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 clocksCalifornia✗ CA 60-day late · 146dMaine⏱ ME AG >30d · 59dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 20, 2023breach begins
Dec 26, 2023discovered
notification delay · 59 days
Feb 23, 2024first filing
May 29, 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. FEB 23MT AGMT AG noticefirst filing · 4 MT residentsday 0
  2. FEB 23CA AGCA AG noticeno count statedday 0
  3. FEB 23ME AGME AG noticestates nationwide total 54,353day 0
  4. FEB 23HHS OCRHHS OCR noticestates nationwide total 55,917day 0
  5. FEB 23MA AGMA AG notice2 MA residentsday 0
  6. FEB 23IN AGIN AG noticestates nationwide total 54,353day 0
  7. MAR 13NH AGNH AG notice2 NH residents+19d
  8. MAY 29CA AGCA AG noticemost recent · no count stated+96d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 20, 2023 – Dec 26, 2023
MT AG
Discovered
Dec 26, 2023· 6d undetected
MT AG + CA AG + ME AG +1
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MT AG + CA AG + HHS OCR +2
Attack vector
Ransomware
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)

55,917

Sum of filed state slices

22· 0.0% of stated

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

US55,917
IN12
MT4
ME2
MA2
NH2

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

96 days

Cadence

~1 / 13.7d

vs. multi-state median

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