All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed10 records · 7 statesUnverified claimConfirmedEnforcedransomhousehigh sensitivity

Merged incident · 10 records

Albany ENT & Allergy Services, PC. — March 2023 breach

Clustered 10 records across 7 jurisdictions: 8 filings and 2 leak-site claims · filing window May 25, 2023 → May 31, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

Affected · reported

224,486

First → last dated filing

May 25, 2023 → May 31, 2023

Merge confidence

100%

incident inc_7cbc4cba12204df1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 2 unverified claims. Intrusion Mar 23, 2023–Apr 4, 2023, discovered Mar 27, 2023. 224,486 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 2 more. Notifications rolled out on a 6-day schedule across 7 dated filings beginning May 25, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Discovery variance

36days

Range of discovered_at dates across filings

Filing span

6days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dMaine✓ ME AG ≤30d · 23dHIPAA✓ HHS report on timeMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 23, 2023breach begins

Mar 27, 2023discovered · members disagree

May 25, 2023first dated filing

May 31, 2023most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

JAN 1IL AGIL AG noticefiling day not on record · no count stated—
APR 28Leak siteransomhouse postfirst record · attacker claim · unverifiedoperator-confirmedday 0
MAY 11Leak sitebianlian postattacker claim · unverifiedoperator-confirmed+13d
MAY 25ME AGME AG noticestates nationwide total 224,486auto-linked+27d
MAY 25HHS OCRHHS OCR noticestates nationwide total 224,486auto-linked+27d
MAY 25IN AGIN AG noticestates nationwide total 224,486auto-linked+27d
MAY 25MA AGMA AG notice450 MA residentsauto-linked+27d
MAY 25ME AGME AG noticestates nationwide total 224,486auto-linked+27d
MAY 25MT AGMT AG notice10 MT residentsauto-linked+27d
MAY 31NH AGNH AG noticemost recent · 76 NH residentsauto-linked+33d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 23, 2023
Discovered: Mar 27, 2023IL AG + MT AG + NH AGMay 2, 2023ME AG + HHS OCRfilings disagree on discovery
Data types: Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Unauthorized Access

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)

224,486

Sum of filed state slices

622· 0.3% of stated

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

US224,486

MA450

NH76

ME61

IN25

MT10

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

6 days

Cadence

~1 / 1d

vs. multi-state median

1.0× faster

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.