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

Alpine Ear Nose & Throat — November 2024 breach

Clustered 7 filings across 6 jurisdictions · filing window Nov 19, 2024 → Jan 30, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

65,648

First → last filing

Nov 19, 2024 → Jan 30, 2026

Merge confidence

100%

incident inc_bc9a9f6def5740cd · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Nov 19, 2024, discovered Nov 19, 2024 — the first regulatory filing landed 59 days later (flagged late). 65,648 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 4 more. Notifications rolled out on a 437-day schedule across 5 filings beginning Nov 19, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
59days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
59days 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
437days

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 >180dMaine✗ ME AG >90d · 437dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Nov 19, 2024breach begins
Nov 19, 2024discovered
notification delay · 59 days
Jan 17, 2025first filing
Jan 30, 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. NOV 19Leak sitebianlian postfirst filing · attacker claim · unverifiedday 0
  2. DEC 1Leak sitebianlian postattacker claim · unverified+12d
  3. JAN 17HHS OCRHHS OCR noticestates nationwide total 65,648+59d
  4. JAN 30MA AGMA AG notice7 MA residents+437d
  5. JAN 30NH AGNH AG noticestates nationwide total 65,648+437d
  6. JAN 30ME AGME AG noticestates nationwide total 65,648+437d
  7. JAN 30IN AGIN AG noticemost recent · states nationwide total 65,648+437d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 19, 2024
ME AG
Discovered
Nov 19, 2024
NH AG + ME AG
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI
HHS OCR + MA AG + NH AG +1
Attack vector
Unauthorized Access
HHS OCR

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)

65,648

Sum of filed state slices

43· 0.1% of stated

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

US65,648
IN18
ME10
NH8
MA7

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 13, 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

437 days

Cadence

~1 / 72.8d

vs. multi-state median

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