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

Houser, LLP — May 2023 breach

Clustered 23 filings across 13 jurisdictions · filing window Feb 1, 2024 → Apr 12, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

23 filings

States

13

Affected · reported

370,001

First → last filing

Feb 1, 2024 → Apr 12, 2024

Merge confidence

100%

incident inc_e647c062f94c42dc · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 23 regulatory filings. Intrusion May 7, 2023–May 9, 2023, discovered May 7, 2023 — the first regulatory filing landed 270 days later (flagged late). 370,001 individuals reported across the linked filings. Data reported: Biometric, Government ID, Identity (basic), and 6 more. Notifications rolled out on a 71-day schedule across 23 filings beginning Feb 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
270days

Discovered → first regulatory filing

Discovery variance
256days

Range of discovered_at dates across filings

Filing span
71days

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 clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 295dVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 41dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueHawaii✓ HI CRA notice dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

biometricfinancial_credentialsidentity_government

Incident timeline

May 7, 2023breach begins
May 7, 2023discovered · members disagree
notification delay · 270 days
Feb 1, 2024first filing
Apr 12, 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 1IL AGIL AG noticefirst filing · no count statedday 0
  2. FEB 28ME AGME AG noticestates nationwide total 326,386+27d
  3. FEB 28MT AGMT AG notice588 MT residents+27d
  4. FEB 28WA AGWA AG notice7,791 WA residents+27d
  5. FEB 28CA AGCA AG noticeno count stated+27d
  6. FEB 28OR AGOR AG noticestates nationwide total 326,386+27d
  7. FEB 28MA AGMA AG notice10,630 MA residents+27d
  8. FEB 28NH AGNH AG notice2,217 NH residents+27d
  9. FEB 28VT AGVT AG noticeno count stated+27d
  10. FEB 28HI AGHI AG notice1,620 HI residents+27d
  11. FEB 28DE AGDE AG noticeno count stated+27d
  12. FEB 28IN AGIN AG noticestates nationwide total 326,386+27d
  13. FEB 29SC AGSC AG notice5,255 SC residents+28d
  14. MAR 26ME AGME AG noticestates nationwide total 364,312+54d
  15. MAR 26DE AGDE AG noticeno count stated+54d
  16. MAR 26NH AGNH AG notice2,217 NH residents+54d
  17. MAR 26CA AGCA AG noticeno count stated+54d
  18. MAR 27VT AGVT AG noticeno count stated+55d
  19. APR 12NH AGNH AG notice2,217 NH residents+71d
  20. APR 12CA AGCA AG noticeno count stated+71d
  21. APR 12DE AGDE AG noticeno count stated+71d
  22. APR 12VT AGVT AG noticeno count stated+71d
  23. APR 12ME AGME AG noticemost recent · states nationwide total 370,001+71d
  24. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 7, 2023
ME AG
Discovered
May 7, 2023IL AGMay 9, 2023MT AG + WA AG + CA AG +5Jan 18, 2024ME AG + OR AGfilings disagree on discovery
Data types
Biometric · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
ME AG + MT AG + WA AG +7
Attack vector
Unauthorized Access
ME 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)

370,001

Sum of filed state slices

37,151· 10.0% of stated

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

US370,001
MA10,630
WA7,791
IN7,308
SC5,255
NH2,217
ME1,742
HI1,620
MT588

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

71 days

Cadence

~1 / 3.2d

vs. multi-state median

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