DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed13 records · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinc_ransomhigh sensitivity
Merged incident · 13 records

UNITE HERE! — October 2023 breach

Clustered 13 records across 11 jurisdictions: 11 filings and 2 leak-site claims · filed Feb 23, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 records

States

11

Affected · reported

791,273

First → last dated filing

Feb 23, 2024

Merge confidence

100%

incident inc_7ef81b59f6f14f52 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings and 2 unverified claims. Intrusion Oct 20, 2023, discovered Oct 20, 2023. 791,273 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
0days

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 clocksOregon✗ OR AG >45dWashington✗ WA AG >90dLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 126dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 20, 2023breach begins
Oct 20, 2023discovered
Feb 23, 2024first dated filing
—watching for filings

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

  1. DEC 20Leak siteinc_ransom postfirst record · attacker claim · unverifiedday 0
  2. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  3. FEB 23NH AGNH AG notice212 NH residents+64d
  4. FEB 23MT AGMT AG notice3,881 MT residents+64d
  5. FEB 23OR AGOR AG noticestates nationwide total 791,273+64d
  6. FEB 23VT AGVT AG noticeno count stated+64d
  7. FEB 23MA AGMA AG notice32,964 MA residents+64d
  8. FEB 23CA AGCA AG noticeno count stated+64d
  9. FEB 23IN AGIN AG noticestates nationwide total 791,273+64d
  10. FEB 23HHS OCRHHS OCR noticestates nationwide total 95,797+64d
  11. FEB 23WA AGWA AG notice76,574 WA residents+64d
  12. FEB 23ME AGME AG noticestates nationwide total 791,273+64d
  13. APR 22Leak siteinc_ransom postmost recent · attacker claim · unverified+123d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 20, 2023
NH AG
Discovered
Oct 20, 2023
IL AG + MT AG + OR AG +2
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + MT AG + VT AG +5
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)

791,273

Sum of filed state slices

119,415· 15.1% of stated

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

US791,273
WA76,574
MA32,964
IN5,681
MT3,881
NH212
ME103

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

0 days

Cadence

~1 / 0d

vs. multi-state median

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