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

Mehri & Skalet, PLLC — December 2024 breach

Clustered 15 filings across 11 jurisdictions · filing window Oct 1, 2025 → Nov 21, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

11

Affected · reported

36,011

First → last filing

Oct 1, 2025 → Nov 21, 2025

Merge confidence

100%

incident inc_b6ef8ee7e6634cb7 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. Intrusion Dec 17, 2024, discovered May 20, 2025 — the first regulatory filing landed 134 days later (flagged late). 36,011 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 4 more. Notifications rolled out on a 51-day schedule across 15 filings beginning Oct 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
134days

Discovered → first regulatory filing

Discovery variance
128days

Range of discovered_at dates across filings

Filing span
51days

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 clocksMaine✗ ME AG >90d · 157dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 183dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 17, 2024breach begins
May 20, 2025discovered · members disagree
notification delay · 134 days
Oct 1, 2025first filing
Nov 21, 2025most 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. OCT 1IL AGIL AG noticefirst filing · no count statedday 0
  2. OCT 24MA AGMA AG notice248 MA residents+23d
  3. OCT 24NE AGNE AG notice12 NE residents+23d
  4. OCT 24IN AGIN AG notice446 IN residents+23d
  5. OCT 24ME AGME AG notice9 ME residents+23d
  6. OCT 24VT AGVT AG noticeno count stated+23d
  7. OCT 24NH AGNH AG notice35 NH residents+23d
  8. OCT 27TX AGTX AG noticestates nationwide total 10,328+26d
  9. NOV 19WA AGWA AG notice518 WA residents+49d
  10. NOV 19ME AGME AG notice107 ME residents+49d
  11. NOV 19NH AGNH AG notice125 NH residents+49d
  12. NOV 19CA AGCA AG noticeno count stated+49d
  13. NOV 19VT AGVT AG noticeno count stated+49d
  14. NOV 19MT AGMT AG notice69 MT residents+49d
  15. NOV 21TX AGTX AG noticemost recent · states nationwide total 36,011+51d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 17, 2024
NE AG
Discovered
May 20, 2025NE AG + ME AG + VT AG +4Sep 25, 2025IL AG + TX AGfilings disagree on discovery
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + MA AG + NE AG +7
Attack vector
Phishing
NE 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)

36,011

Sum of filed state slices

4,735· 13.1% of stated

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

US36,011
TX3,210
WA518
IN446
MA248
NH125
ME107
MT69
NE12

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

51 days

Cadence

~1 / 3.6d

vs. multi-state median

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