DisclosureLens
Leak SiteHHS OCRState AGConfirmed17 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblack_bastahigh sensitivity
Merged incident · 17 filings

UNITED SEATING AND MOBILITY, L.L.C. — February 2024 breach

Clustered 17 filings across 13 jurisdictions · filing window Feb 29, 2024 Jul 18, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

17 filings

States

12

Affected · reported

698,577

First → last filing

Feb 29, 2024 Jul 18, 2024

Merge confidence

100%

incident inc_7e380a5425964691 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings and 2 unverified claims. Intrusion Feb 29, 2024–Mar 2, 2024, discovered Mar 2, 2024 — the first regulatory filing landed 44 days later (flagged late). 698,577 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Employment, and 4 more. Notifications rolled out on a 140-day schedule across 15 filings beginning Feb 29, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
44days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Leak precedence
46days 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
140days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >90d · 135dLeak gap Leak >30dVermont VT AG >14 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 29, 2024breach begins
Mar 2, 2024discovered · members disagree
notification delay · 44 days
Apr 15, 2024first filing
Jul 18, 2024most 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. FEB 29Leak siteblack_basta postfirst filing · attacker claim · unverifiedday 0
  2. MAR 2Leak siteblack_basta postattacker claim · unverified+2d
  3. APR 15NH AGNH AG notice8 NH residents+46d
  4. APR 15MT AGMT AG notice720 MT residents+46d
  5. APR 15ME AGME AG noticestates nationwide total 4,190+46d
  6. APR 15VT AGVT AG noticeno count stated+46d
  7. APR 15IN AGIN AG noticestates nationwide total 698,577+46d
  8. APR 15MA AGMA AG notice9,289 MA residents+46d
  9. MAY 1CA AGCA AG noticeno count stated+62d
  10. MAY 1SC AGSC AG notice10,627 SC residents+62d
  11. MAY 1HHS OCRHHS OCR noticestates nationwide total 602,265+62d
  12. MAY 1IL AGIL AG noticeno count stated+62d
  13. MAY 1WA AGWA AG notice35,143 WA residents+62d
  14. JUL 17ME AGME AG noticestates nationwide total 698,577+139d
  15. JUL 17CA AGCA AG noticeno count stated+139d
  16. JUL 17OR AGOR AG noticestates nationwide total 698,577+139d
  17. JUL 18NH AGNH AG noticemost recent · 18 NH residents+140d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 29, 2024Mar 2, 2024
MT AG
Discovered
Mar 2, 2024NH AG + MT AG + VT AG +4Mar 4, 2024ME AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + MT AG + ME AG +6
Attack vector
Ransomware
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)

698,577

Sum of filed state slices

55,993· 8.0% of stated

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

US698,577
WA35,143
SC10,627
MA9,289
MT720
IN182
NH18
ME14

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

140 days

Cadence

~1 / 8.8d

vs. multi-state median

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