2023 · United States · K - Financial and insurance activities · Data theft via network intrusion (bulk exfiltration of eligibility files)
Analysed 2026-11-07 by Hermes
Open this case in the tool →Data theft via network intrusion (bulk exfiltration of eligibility files)
Strategy to Execution
Evidence coverage: 3/6 stages, weight 15/60
Decisive stage: detection (clearest evidence) · Alternative: Expertise to Execution
(1) WebTPA is a third-party administrator that runs health and insurance plan administration for insurers and self-insured employers and, in its own words, acts as a Business Associate under HIPAA/HITECH for the eligibility data of some 2.4 million plan members; the doctrinal expectation is therefore explicit and regulatory: monitor and audit the systems holding entrusted PHI and notify affected parties within statutory timelines. (2) In practice, an unauthorized actor accessed the network through a VPN connection on 6 March 2023, remained active until 12 May 2023, and exfiltrated eligibility files (names, contact details, birth/death dates, SSNs, insurance identifiers) between 18 and 23 April 2023; WebTPA detected suspicious activity only on 28 December 2023 - roughly 9.7 months after initial access and 7.5 months after the last attacker activity - learned of the exfiltration from third-party forensics rather than its own monitoring, told its clients on 25 March 2024, and notified individuals and HHS on 8 May 2024, more than a year after the theft. The entry mechanism itself (how the VPN session was obtained) is undisclosed and is not load-bearing. (3) This is a knowing-doing gap of the Strategy to Execution kind: the expectations - continuous monitoring of PHI systems, control of bulk data transfers, timely notification - were not aspirational and needed no new leadership decision; they were standing regulatory and contractual obligations that simply were not realised in operations and architecture, and no source shows leadership deferring, under-funding or knowingly accepting them. The classification rests on the detection stage, the one whose origin and break are documented by WebTPA's own primary filings (clearest evidence); the egress and response gaps point to the same type and the distribution is not borderline. (4) RM34 (Strategy to Execution lens): the monitoring and alert-handling requirements a HIPAA Business Associate must operate for data of this scale were not implemented or operated as intended - a nearly ten-month dwell time, with detection on 28 December 2023 prompted by nothing more than evidence of suspicious activity, shows time-to-detect as the decisive failure (causal role: Obscuring). RM35 (Strategy to Execution lens): egress controls and data-transfer restrictions were not translated into effective operational barriers - five days of bulk exfiltration of eligibility files covering ~2.4 million individuals went undetected and uninterruptedly at the time and were reconstructed only later by external forensic experts (causal role: Amplifying). RM39 (Strategy to Execution lens): the notification policy, roles and workflow that the statutory timelines presuppose were not operationalised to those timelines - clients were informed three months after detection and individuals and HHS 132 days after detection, over 12 months after the theft, while WebTPA's own filing states "Notification was not delayed as a result of a law enforcement investigation" (causal role: Constraining).
RM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapRM39 — Breach notification / disclosure failureRow description matches the incident and the stated victim (customers of The Hartford, Transamerica and Gerber Life confirmed affected; no data-quality bug). The dataset source_url slug says 24-million but the opened BleepingComputer article gives 2.4 million (HHS portal: 2,429,175; HIPAA Journal reports a later HHS update to 2,518,533). WebTPA's own notice page (webtpa.com/notice) could not be opened at analysis time, so the victim's disclosure is cited through the notification letter its counsel filed with the Maryland Attorney General and through press quoting the notice. Actor is not publicly attributed; no ransomware group or claim of responsibility appeared in opened sources. The notification timeline is contested in the consolidated class action Harrell v. WebTPA (N.D. Tex. 3:24-cv-01158-L); defendants deny wrongdoing and agreed a $13.75M settlement (reported Sept 2025), and no regulator finding of failings was located - RM39 is coded on the dates in WebTPA's own regulatory filings, not on a legal finding. The egress-stage reading (egress visibility should have existed) rests partly on inference from WebTPA's Business Associate obligations; no opened source describes its DLP posture. Ownership per SecurityWeek: wholly owned subsidiary of GuideWell Mutual Holding Corporation; Anthem BCBS and Elevance Health were co-defendants in the consolidated action. Research used only public regulator filings, victim notifications and press reporting; no leak-site or attacker material was consulted. Link check: oag.maryland.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: hipaajournal.com blocks automated access (HTTP 403); the page was opened and read during research.