← Breach analysis by the Dual Vulnerabilities framework

HealthEC platform data theft (unattributed, 2023)

2023 · United States · Q - Human health and social work activities · Data theft via compromised population health management platform (supply-chain breach affecting client healthcare organisations)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via compromised population health management platform (supply-chain breach affecting client healthcare organisations)

Dual vulnerability type

Strategy to Execution

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

Decisive stage: egress (clearest evidence) · Alternative: Strategy to Leadership

Why this classification

(1) HealthEC LLC is a population health management vendor that aggregates personal, clinical and claims data for some 18 provider organisations (Corewell Health, HonorHealth, TennCare and the community health centres named in the row); as a HIPAA business associate the expectation on it was doctrinal and explicit: safeguard the protected health information in its care and notify covered clients of a breach without unreasonable delay and within 60 days of discovery. (2) In practice an unknown actor accessed certain systems from 14 to 23 July 2023 and copied files across that entire window without being interrupted; HealthEC became aware in July 2023, completed its file review only on 24 October, notified clients from 26 October, mailed individual letters from 22 December 2023 (for some clients not until 7 February 2024), and its public notice did not state the total impact - the 4,452,782 figure surfaced via the HHS breach portal in January 2024. The entry vector was never disclosed and is not load-bearing. (3) This is a knowing-doing gap of the Strategy to Execution kind: the duties existed as formal strategic artefacts (HIPAA obligations, business-associate contracts, a compliance-selling data platform), but the chain broke in operational realisation - nothing stopped a ten-day bulk exfiltration from the platform, and the notification workflow took three-plus months to reach clients and five to reach individuals. No source shows leadership knowing and deferring these duties, so the diagonal runs strategy to execution rather than within the doctrinal column. The classification rests on the egress stage (load-bearing); the response stage points to the same type. (4) RM35 (Strategy to Execution lens): egress controls and data-transfer restrictions were not translated into an effective operational barrier - files were copied off a platform holding data for a membership of around eight million over ten days without detection or interruption, amplifying the impact to 4.45 million patients (causal role: Amplifying). RM39 (Strategy to Execution lens): notification policies and workflows were not operationalised - awareness in July 2023, client notification on 26 October (past the 60-day outer limit as measured from the July awareness documented in the client's letter to the Maryland AG), individual letters five months after discovery, and a public notice silent on the total scale (causal role: Constraining). RM13 (Strategy to Execution lens): the client providers' supplier contracts and due diligence did not translate into monitored vendor operation - the centres learned of the incident only when HealthEC told them around 26 October, had no visibility into its scope, and for Corewell Health this was the second supply-chain breach of 2023 (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

The Victim column lists 14 client healthcare organisations plus HealthEC LLC; the organisation actually breached was HealthEC LLC (health-data platform vendor, New Jersey; since rebranded Elligint Health) - the others are downstream clients affected through the shared platform, so the lifecycle analysis is HealthEC's. The case file's Maine AG notification URL returns 404; the same notification text was read as filed with the California AG, and the 4,452,782 total comes from HHS portal reporting cited by BleepingComputer and SC Magazine. healthec.com/cyber-incident/ now redirects to a marketing page (incident page removed), so the notice is cited in its state-agency copies. Whether the 26 October client notification exceeded HIPAA's 60-day outer limit depends on treating 'discovery' as the July 2023 awareness (the client's Maryland AG letter) rather than the 24 October completion of the file review; the consolidated class action (D.N.J. 2:24-cv-00026) alleges the breach was discovered in July and notification was unreasonably delayed five months - an allegation, not a finding; no OCR enforcement against HealthEC was found. Class-action allegations of missing encryption and cost-driven underinvestment were treated as allegations and not coded. Actor unattributed; entry vector never disclosed. Link check: oag.maryland.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: hhs.gov blocks automated access (HTTP 403); the page was opened and read during research.