← Breach analysis by the Dual Vulnerabilities framework

Welltok MOVEit data theft (Clop, 2023)

2023 · United States · Q - Human health and social work activities · Data theft via exploited managed file transfer tool

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Data theft via exploited managed file transfer tool

Dual vulnerability type

Strategy to Execution

Evidence coverage: 2/6 stages, weight 9/60

Decisive stage: egress (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) Welltok sat in a position whose doctrinal expectations are strict: a HIPAA business associate running patient-engagement and file-transfer services on behalf of at least 165 health plans and providers, where the governance of the crown-jewel transfer path and of the personal health data concentrated on it is the core strategic obligation. (2) In practice, Clop exploited the MOVEit Transfer zero-day CVE-2023-34362 on 30 May 2023 - the day before the patch existed, which Welltok applied immediately - and exfiltrated data undetected; Welltok's own follow-up examination found no indication of compromise, and the intrusion surfaced only via an external alert on 26 July 2023, after which the firm needed a time-consuming reconstruction and review of its server to understand what data it held and to whom it belonged; the exposed set (names, SSNs, Medicare/Medicaid IDs, provider, prescription and treatment information) grew to 14,762,475 individuals, the second-largest healthcare breach ever reported to OCR at that point. (3) The classification rests on the egress stage: the expectation is doctrinal (business-associate data inventory, classification and minimisation duties; the notice itself promises review and enhancement of existing data-privacy policies and procedures) and the chain broke in execution - those duties were not operationalised, so more and more sensitive data than necessary sat on one commodity transfer server whose very contents the company could not enumerate without a post-hoc reconstruction. The entry vector is documented but not load-bearing (zero-day, no remediation window, RM18 excluded), and the detection gap (57-day dwell, missed examination) is a secondary Expertise to Execution pattern that worsened the response but did not cause the disproportion. (4) RM16 (Strategy to Execution lens): classification, retention and minimisation requirements were not implemented in Welltok's systems and processes - the firm could only establish the contents and owners of the breached server's data by reconstructing it afterwards, and sensitive identifiers for 165 clients lived on a file-transfer server (causal role: Amplifying). RM35 (Strategy to Execution lens): egress controls and data-transfer restrictions were not translated into effective operational barriers - the 30 May bulk exfiltration from its own managed-transfer server went undetected and was only established after a full reconstruction of systems (causal role: Amplifying). RM34 (Strategy to Execution lens): monitoring and alert-handling were not operated as intended - the post-disclosure examination 'using all information available' confirmed no indication of compromise, leaving a 57-day dwell until an external party alerted the company (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

informationisbeautiful row: the case description matches the stated victim Welltok (data categories match the firm's own notice). The case-file source_url carries a stray ' /' suffix and an '85-million' slug, but the article it serves is titled 'Welltok data breach exposes data of 8.5 million US patients'; the 85M figure belongs to the global Clop/MOVEit campaign overall (Emsisoft tracking via HIPAA Journal), while Welltok's own OCR-reported count grew from 8,493,379 to 14,762,475 - the row's headline figure overstates this single breach by roughly a campaign-vs-row confusion. The victim-owned MOVEit server is also described in press as operated under parent Virgin Pulse; no boundary-handoff evidence was documented, so no RM14 was coded. The South Carolina AG copy of Welltok's notification letter could not be read (the URL returns a bot-wall HTML page); Welltok's own notice page (cited) carries the same statements. Actor attribution to Clop is the standard attribution of the MOVEit campaign, reported as confirmed for this incident by HIPAA Journal; attribution is context only and the DV is assessed victim-side. No related_rows in the case file; no earlier Welltok incident established. Link check: hipaajournal.com blocks automated access (HTTP 403); the page was opened and read during research.