2023 · United States · Q - Human health and social work activities · Ransomware attack with undetected data exfiltration
Analysed 2026-11-06 by Hermes
Open this case in the tool →Ransomware attack with undetected data exfiltration
Strategy to Leadership
Evidence coverage: 2/6 stages, weight 16/60
Decisive stage: response (clearest evidence) · Alternative: Expertise to Execution
(1) Richmond University Medical Center is a 470-bed acute-care hospital holding medical, financial and identity records for hundreds of thousands of patients; its binding doctrinal expectation as a HIPAA covered entity was to detect and scope any loss of protected health information and to notify affected individuals without unreasonable delay, in no case later than 60 days after discovery. (2) In practice the operational incident handling was competent: the hospital detected the intrusion itself on 6 May 2023, contained it, kept full services running apart from overnight trauma and stroke diversions, and restored systems within weeks; the electronic health record system was not hit. But files were copied out of the network undetected around 6 May 2023, the hospital could not determine from its own systems what had left and had to locate a copy of each file and manually review them, and individuals received notification letters only in December 2024, roughly 19.5 months after discovery, when 674,033 affected people were reported. The entry vector was never disclosed and is not load-bearing. (3) This is a knowing-doing gap inside the doctrinal column: the expectation (prompt, complete notification; forensic ability to scope a breach) was legally and strategically in place, yet the decision level let the scoping exercise run for nineteen months with individual notification held until it concluded, and the public account stayed at may have been accessed while data had in fact been acquired; the chain did not break in executing a resourced notification process but in deciding its timing - Strategy to Leadership, resting on the response/disclosure stage, the best-documented stage (primary sources: the hospital's own May 2023 notice and December 2024 notification letters, AG filings). A secondary Expertise to Execution pattern sits in the egress stage (undetected exfiltration, manual rescoping), but it rests on inference. (4) RM39 (Strategy to Leadership lens): leadership disclosure behaviour diverged from the legal expectation - individual notification came in December 2024, about 19.5 months after the 6 May 2023 discovery, with no law-enforcement delay documented in any notice and the forensic question about the EHR resolved within weeks (causal role: Constraining). RM33 (Strategy to Leadership lens): forensic readiness did not reach the level the incident demanded - the hospital could not determine from logs and systems what data was taken and needed a copy-by-copy manual review of files that took nineteen months to conclude the scope (causal role: Obscuring). RM35 (Strategy to Leadership lens): exfiltration and data-loss risk had not been converted into an operational control - files containing personal data of 674,033 people left the network around 6 May 2023 without being detected or interrupted, and the hospital learned what had left only by reconstructing file copies afterwards (causal role: Amplifying).
RM39 — Breach notification / disclosure failureRM33 — Logging / forensic-readiness gapRM35 — Egress / exfiltration monitoring gapDataset caveat: the EuRepoC row codes intelligence_impact as no data breach/exfiltration and economic_impact as none; that reflects the May-June 2023 reporting window. The hospital's own December 2024 notification confirms files were acquired and 674,033 individuals were affected; the classification uses the researched record. Link check: the direct rumcsi.org URL of the December 2024 notification PDF returns an HTML error page to programmatic retrieval, so the Wayback snapshot of that exact file, opened and read during this task, is cited instead. Link check: silive.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: mass.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. A law-firm case page read during research dated the notification-letter mailing 19 December 2024; its URL now returns 404 to the link checker and was dropped from the citations - SecurityWeek independently reports state attorneys general were informed mid-December 2024 and the notification letters themselves are dated December 2024. Containment and prompt-detection readings rest on the victim's own statements (self-reported, no independent forensic report published). No ransomware group ever claimed responsibility and the entry vector was never disclosed. Dates: EuRepoC start 05.05.2023 matches the reported onset of outages; 6 May 2023 is the victim's stated discovery date of the unauthorized access. Unattended run: no action requiring consent arose.