DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilincritical sensitivity
Merged incident · 7 filings

Daniels Law Group LLC — June 2025 breach

Clustered 7 filings across 6 jurisdictions · filing window Jul 9, 2025 → Aug 12, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

5,199

First → last filing

Jul 9, 2025 → Aug 12, 2025

Merge confidence

100%

incident inc_255d21c0c7e341e8 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 2 unverified claims. Intrusion Jun 26, 2025–Jul 1, 2025, discovered Jul 1, 2025 — the first regulatory filing landed 41 days later. 5,199 individuals reported across the linked filings. Data reported: Government ID, Minor, Health (basic), and 3 more. Notifications rolled out on a 34-day schedule across 5 filings beginning Jul 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
41days

Discovered → first regulatory filing

Discovery variance
8days

Range of discovered_at dates across filings

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

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 34dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Jun 26, 2025breach begins
Jul 1, 2025discovered · members disagree
notification delay · 41 days
Aug 11, 2025first filing
Aug 12, 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. JUL 9Leak siteqilin postfirst filing · attacker claim · unverifiedday 0
  2. JUL 21Leak siteqilin postattacker claim · unverified+12d
  3. AUG 11IN AGIN AG noticestates nationwide total 5,199+33d
  4. AUG 12MA AGMA AG notice3 MA residents+34d
  5. AUG 12MT AGMT AG notice6 MT residents+34d
  6. AUG 12NH AGNH AG notice1 NH residents+34d
  7. AUG 12ME AGME AG noticemost recent · states nationwide total 5,199+34d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 26, 2025
IN AG
Discovered
Jul 1, 2025MT AGJul 9, 2025NH AG + ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PII
MA AG + NH AG + MT AG +1
Attack vector
Unauthorized Access
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)

5,199

Sum of filed state slices

14· 0.3% of stated

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

US5,199
MT6
IN3
MA3
NH1
ME1

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 filing5 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 22, 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

34 days

Cadence

~1 / 5.7d

vs. multi-state median

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