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

Avamere Health Services, LLC — January 2022 breach

Clustered 9 filings across 6 jurisdictions · filing window Jun 17, 2022 → Dec 26, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

5

Affected · reported

229,460

First → last filing

Jun 17, 2022 → Dec 26, 2022

Merge confidence

100%

incident inc_78de96bfabfa4abf · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 19, 2022–Mar 17, 2022, discovered Mar 17, 2022 — the first regulatory filing landed 92 days later (flagged late). 229,460 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 192-day schedule across 8 filings beginning Jun 17, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
92days

Discovered → first regulatory filing

Discovery variance
92days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 192d

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
192days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dMaine⏱ ME AG >30d · 49dOregon✓ OR AG ≤45dHIPAA✓ HHS report on timeFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 19, 2022breach begins
Mar 17, 2022discovered · members disagree
notification delay · 92 days
Jun 17, 2022first filing
Dec 2, 2022most 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. JUN 17MT AGMT AG noticefirst filing · 278 MT residentsday 0
  2. JUN 24NH AGNH AG notice9 NH residents+7d
  3. JUN 27WA AGWA AG notice65,076 WA residents+10d
  4. JUN 30OR AGOR AG noticestates nationwide total 25,672+13d
  5. JUL 6ME AGME AG noticestates nationwide total 45,381+19d
  6. JUL 13HHS OCRHHS OCR noticestates nationwide total 229,460+26d
  7. JUL 16NH AGNH AG notice15 NH residents+29d
  8. DEC 2NH AGNH AG notice27 NH residents+168d
  9. DEC 26Leak siteavoslocker postmost recent · attacker claim · unverified+192d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 19, 2022 – Mar 17, 2022
NH AG
Discovered
Mar 17, 2022WA AGMay 18, 2022NH AG + OR AG + ME AG +1Jun 17, 2022NH AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + NH AG + WA AG +2
Attack vector
Unauthorized Access
NH 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)

229,460

Sum of filed state slices

65,391· 28.5% of stated

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

US229,460
WA65,076
MT278
NH27
ME10

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 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 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

192 days

Cadence

~1 / 24d

vs. multi-state median

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