2023 · United States · Q - Human health and social work activities · Data theft and extortion of patients (no encryption)
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft and extortion of patients (no encryption)
Expertise to Execution
Evidence coverage: 1/6 stages, weight 10/60
Decisive stage: egress (clearest evidence) · Alternative: Strategy to Execution
(1) INTEGRIS Health is Oklahoma's largest not-for-profit health network, a HIPAA-covered entity holding identity data on millions of patients; the expectation at the victim was that bulk acquisition of patient files would be detected and interrupted and that its data holdings across the hospitals it manages were inventoried and classified well enough to know what an intruder had taken - the victim's own FAQ shows monitoring tooling that produced alerts existed. (2) In practice, files were 'accessed or acquired by an unauthorized party on November 28, 2023' without the organisation noticing the theft at all: INTEGRIS confirmed the data was stolen only when patients received the attacker's extortion emails on December 24, 2023, the data was on sale on a Tor site, and a manual forensic review lasting two months was needed to determine the data types and 'which healthcare entities were involved', with the involvement of its Community Hospital patients discovered only on January 29, 2024. (3) That is a knowing-doing gap inside the material column: the remedies - egress monitoring over bulk file operations and a working inventory and classification of patient data across managed entities - sit with technical operations specialists, the victim's own disclosure shows its alerting capability did not cover the mass file acquisition and its data holdings were not mapped enough to scope the breach, and the chain broke in execution (controls existed in part but were not realised for exfiltration), not at a leadership decision, which no source documents. The entry vector is undisclosed in every source and is not load-bearing; the intrusion itself was found via the victim's own alerts, recovery was not in play (no encryption, no interruption), and disclosure followed the victim's notification obligations, so the classification rests on the egress stage. (4) RM35 (Expertise to Execution lens): the victim's specialists had monitoring tooling in place, yet the acquisition of data on 2,385,646 people left the network undetected and uninterruptedly - egress visibility was never tuned to cover bulk patient-file operations, so the theft surfaced only through the attacker's extortion emails (causal role: Amplifying). RM16 (Expertise to Execution lens): specialists could not identify the breached data from existing inventories - INTEGRIS could not say which data types or which of the healthcare entities it manages were involved without a two-month manual review, showing data ownership, lineage and inventories were inadequate (causal role: Amplifying).
RM35 — Egress / exfiltration monitoring gapRM16 — Data governance / minimisation gapEuRepoC row; victim as written matches the description (no mismatch). Actor unattributed in contemporaneous reporting; the Hunters International attribution rests on the gang's later victim claims reported by BleepingComputer, not on a forensic confirmation. Scale figures differ by source: the extortion emails claimed data of over 2 million patients, the HHS OCR portal figure is 2,385,646, and the Tor extortion site listed about 4,674,000 records (duplicates unknown, attacker claim). The victim's live notice pages (integrisok.com/integrishealth.org cyber-event) block automated access (HTTP 403); the notice text was instead read from the victim's PRNewswire release and the victim's FAQ PDF hosted on its Community Hospital site. The dataset source_url list mixes in unrelated articles: the therecord.media link covers Capital Health (New Jersey), not INTEGRIS (it was opened and mentions INTEGRIS only in passing), and one BleepingComputer link covers a Hunters International malware campaign against IT workers; neither is cited as load-bearing. Detection date is not disclosed; notification timing (site notice Dec 24, 2023; mass notice Feb 6, 2024) showed no established unreasonableness since the discovery date is undisclosed, so no disclosure marker was coded, and the extortion decision was made without any documented governance record, so no extortion-governance marker was coded either.