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

LABELLA ASSOCIATES, D.P.C. — March 2025 breach

Clustered 7 filings across 7 jurisdictions · filing window Apr 28, 2025 → Nov 12, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

6,712

First → last filing

Apr 28, 2025 → Nov 12, 2025

Merge confidence

100%

incident inc_ec18d09f24744fd5 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 24, 2025, discovered Mar 24, 2025 — the first regulatory filing landed 202 days later (flagged late). 6,712 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 197-day schedule across 6 filings beginning Apr 28, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
202days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
166days 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
197days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 233dLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 24, 2025breach begins
Mar 24, 2025discovered
notification delay · 202 days
Oct 12, 2025first filing
Nov 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. APR 28Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. OCT 12VT AGVT AG noticeno count stated+166d
  3. NOV 12ME AGME AG noticestates nationwide total 6,712+197d
  4. NOV 12NH AGNH AG notice11 NH residents+197d
  5. NOV 12IN AGIN AG noticestates nationwide total 6,712+197d
  6. NOV 12MT AGMT AG notice2 MT residents+197d
  7. NOV 12MA AGMA AG noticemost recent · 30 MA residents+197d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 24, 2025
ME AG
Discovered
Mar 24, 2025
VT AG + ME AG + NH AG +1
Data types
Financial account · Identity (basic) · Government ID
VT AG + ME AG + NH AG +2
Attack vector
Unauthorized Access
VT 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)

6,712

Sum of filed state slices

230· 3.4% of stated

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

US6,712
ME179
MA30
NH11
IN8
MT2

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 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

197 days

Cadence

~1 / 32.8d

vs. multi-state median

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