DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed16 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhivemoderate sensitivity
Merged incident · 16 filings

ALVARIA, INC. — March 2023 breach

Clustered 16 filings across 4 jurisdictions · filing window Jan 1, 2023 → May 26, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

16 filings

States

4

Affected · reported

4,456

First → last filing

Jan 1, 2023 → May 26, 2023

Merge confidence

100%

incident inc_88fb90b416304c6e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 16 regulatory filings. The filings describe malware. Intrusion Mar 9, 2023–Mar 10, 2023, discovered Mar 9, 2023. 4,456 individuals reported across the linked filings. Data reported: Identity (basic), PII, PHI, and 2 more. Notifications rolled out on a 145-day schedule across 16 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
145days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Incident timeline

Mar 9, 2023breach begins
Mar 9, 2023discovered
Jan 1, 2023first filing
May 26, 2023most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. APR 26CA AGCA AG noticeno count stated+115d
  3. MAY 26HHS OCRHHS OCR noticestates nationwide total 1,518+145d
  4. MAY 26HHS OCRHHS OCR noticestates nationwide total 916+145d
  5. MAY 26HHS OCRHHS OCR noticestates nationwide total 4,456+145d
  6. MAY 26HHS OCRHHS OCR noticestates nationwide total 537+145d
  7. MAY 26HHS OCRHHS OCR noticestates nationwide total 1,097+145d
  8. MAY 26HHS OCRHHS OCR noticestates nationwide total 507+145d
  9. MAY 26HHS OCRHHS OCR noticestates nationwide total 803+145d
  10. MAY 26HHS OCRHHS OCR noticestates nationwide total 1,147+145d
  11. MAY 26HHS OCRHHS OCR noticestates nationwide total 1,191+145d
  12. MAY 26NH AGNH AG notice1 NH residents+145d
  13. MAY 26HHS OCRHHS OCR noticestates nationwide total 983+145d
  14. MAY 26HHS OCRHHS OCR noticestates nationwide total 524+145d
  15. MAY 26HHS OCRHHS OCR noticestates nationwide total 1,389+145d
  16. MAY 26HHS OCRHHS OCR noticemost recent · states nationwide total 796+145d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 9, 2023 – Mar 10, 2023
CA AG
Discovered
Mar 9, 2023
IL AG + CA AG + NH AG
Data types
Employment · Health (basic) · Identity (basic) · PHI · PII
CA AG + HHS OCR + NH AG
Attack vector
Ransomware
CA 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)

4,456

Sum of filed state slices

1· 0.0% of stated

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

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

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

145 days

Cadence

~1 / 9.7d

vs. multi-state median

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