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

Project Hospitality — July 2024 breach

Clustered 7 filings across 7 jurisdictions · filing window Sep 2, 2024 → May 12, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

89,476

First → last filing

Sep 2, 2024 → May 12, 2025

Merge confidence

100%

incident inc_15625bc680ed4975 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 2, 2024, discovered Jul 8, 2024 — the first regulatory filing landed 58 days later (flagged late). 89,476 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 3 more. Notifications rolled out on a 251-day schedule across 6 filings beginning Sep 2, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
58days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
1days 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
251days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap✗ Leak >180dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Jul 2, 2024breach begins
Jul 8, 2024discovered
notification delay · 58 days
Sep 4, 2024first filing
May 12, 2025most 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. SEP 2Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. SEP 4HHS OCRHHS OCR noticestates nationwide total 42,432+1d
  3. NOV 4MT AGMT AG notice1 MT residents+62d
  4. MAY 7VT AGVT AG noticeno count stated+246d
  5. MAY 7MA AGMA AG notice9 MA residents+246d
  6. MAY 7IN AGIN AG noticestates nationwide total 89,476+246d
  7. MAY 12NH AGNH AG noticemost recent · 1 NH residents+251d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 2, 2024
IN AG
Discovered
Jul 8, 2024· 6d undetected
MT AG + VT AG + NH AG
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + MT AG + MA AG +2
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)

89,476

Sum of filed state slices

15· 0.0% of stated

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

US89,476
MA9
IN4
MT1
NH1

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

251 days

Cadence

~1 / 41.8d

vs. multi-state median

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