DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed19 filings · 13 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedshinyhunterscritical sensitivity
Merged incident · 19 filings

DentaQuest, LLC — May 2026 breach

Clustered 19 filings across 14 jurisdictions · filing window May 28, 2026 → Aug 12, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

19 filings

States

13

Affected · reported

27,400,000

First → last filing

May 28, 2026 → Aug 12, 2026

Merge confidence

100%

incident inc_3d68003633fd4798 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 17 regulatory filings and 2 unverified claims. Intrusion May 17, 2026–May 20, 2026, discovered May 20, 2026 — the first regulatory filing landed 42 days later (flagged late). 27,400,000 individuals reported across the linked filings. Data reported: Government ID, Minor, Health (basic), and 3 more. Notifications rolled out on a 76-day schedule across 17 filings beginning May 28, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
42days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
34days 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
76days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >30dMassachusetts⏱ MA AG >30dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

May 17, 2026breach begins
May 20, 2026discovered
notification delay · 42 days
Jul 1, 2026first filing
Aug 12, 2026most 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 28Leak siteshinyhunters postfirst filing · attacker claim · unverifiedday 0
  2. MAY 30Leak siteshinyhunters postattacker claim · unverified+2d
  3. JUL 1IL AGIL AG noticeno count stated+34d
  4. JUL 16IA AGIA AG noticestates nationwide total 15,000,000+49d
  5. JUL 16MA AGMA AG notice522,000 MA residents+49d
  6. JUL 16HHS OCRHHS OCR noticestates nationwide total 15,000,000+49d
  7. JUL 16RI AGRI AG noticestates nationwide total 15,000,000+49d
  8. JUL 16WA AGWA AG noticestates nationwide total 15,000,000+49d
  9. JUL 16CA AGCA AG noticeno count stated+49d
  10. JUL 16OR AGOR AG noticestates nationwide total 15,000,000+49d
  11. JUL 16SC AGSC AG notice265,900 SC residents+49d
  12. JUL 17DE AGDE AG noticeno count stated+50d
  13. JUL 17TX AGTX AG noticestates nationwide total 15,000,000+50d
  14. JUL 17NE AGNE AG noticeno count stated+50d
  15. JUL 29NH AGNH AG noticestates nationwide total 189,492+62d
  16. JUL 30ID AGID AG notice26 ID residents+63d
  17. JUL 30MA AGMA AG notice51 MA residents+63d
  18. AUG 3ID AGID AG noticestates nationwide total 27,400,000+67d
  19. AUG 12ID AGID AG noticemost recent · 26 ID residents+76d
  20. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 17, 2026 – May 19, 2026
IA AG
Discovered
May 20, 2026· 3d undetected
IL AG + IA AG + MA AG +10
Data types
Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
IL AG + IA AG + MA AG +10
Attack vector
Phishing
IA 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)

27,400,000

Sum of filed state slices

4,860,005· 17.7% of stated

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

US27,400,000
TX3,973,000
MA522,000
SC265,900
WA91,700
IA3,200
ID3,200
RI1,000
NH5

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

76 days

Cadence

~1 / 4.2d

vs. multi-state median

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