← Breach analysis by the Dual Vulnerabilities framework

Acadian Ambulance Ransomware & Data Theft (Daixin Team, 2024)

2024 · United States · Q - Human health and social work activities · Ransomware attack with data theft and disruption

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with data theft and disruption

Dual vulnerability type

Strategy to Execution

Evidence coverage: 3/6 stages, weight 12/60

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

Why this classification

(1) Acadian Ambulance Services, one of the largest private EMS providers in the US, is a HIPAA-covered entity holding patient intake data - names, addresses, dates of birth, Social Security numbers and medical information - so the expectation to protect that crown-jewel data through controls and monitoring sits at the doctrinal (regulatory/strategic) level. (2) In practice a threat actor held access to the network from June 19 to June 21, 2024 and files and folders were taken without authorization, with no reporting of anything detecting or interrupting the transfers; the victim's own IT did detect suspicious activity on or around June 21 (detection aligned), lockdown and backups preserved patient care and dispatch and restored systems within days (recovery aligned), and the entry vector was never disclosed (not load-bearing). What the investigation then showed is that the safeguard expectation existed on paper while the operational architecture did not deliver it: two months of file review were needed to scope what had left, the notice still stated only that data 'were or may have been taken', and HHS counted 2,896,985 affected individuals. The Daixin Team's unverified claim of encrypting 1,000-2,000 of ~2,000 servers points to a flat, unsegmented virtual estate (containment, contribution only - attacker claim). On disclosure, the public acknowledgment of the theft was forced by the group's leak-site listing of July 23, and Acadian's statements never acknowledged the $7 million ransom demand (response, contributing; deadlines reported as met). (3) This is a Strategy to Execution gap: the doctrinal duty to protect patient data did not translate into operational reality - no effective egress control stopped or noticed bulk exfiltration over the three-day window. No source documents leadership deciding and resourcing egress controls that then failed, nor leadership deferring or accepting the gap, so the break is classified as execution on inference, and the classification rests on the egress stage, the only load-bearing stage documented; the runner-up Strategy to Leadership reading of the response stage cannot win because that gap contributes rather than bears the impact. (4) RM35 (Strategy to Execution lens): egress controls, DLP or data-transfer restrictions were not translated into effective operational barriers - sensitive patient files left the network undetected and uninterruptedly during June 19-21, and their content could only be established afterwards by reviewing the stolen files (causal role: Amplifying). RM30 (Strategy to Execution lens): segmentation and isolation requirements were not realized in the architecture to the extent that, per the group's unverified claim, ransomware reached roughly half of the ~2,000-server estate from one intrusion, sparing only the deliberately untouched life-support systems (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Data quality: eurepoc_extra.intelligence_impact ('No data breach/exfiltration or data corruption...') contradicts the row's own description and the victim's HHS OCR filing of 2,896,985 affected individuals; the theft is treated as established from the victim's own notice. Attribution: EuRepoC records the row as Not attributed; Daixin Team's claim is consistent with sector reporting and the Oct 2022 CISA/FBI/HHS joint advisory, but the victim never confirmed the group, the entry vector or ransomware details. Attacker claims: the 10/11 million records, the $7 million demand, the ~$173,000 counter-offer, the June 22 start of negotiations and the encryption of 1,000-2,000 servers are Daixin Team claims relayed by DataBreaches.net; Acadian publicly disputed the affected count and employee SSNs. Daixin claimed in September 2024 (ISMG) that it had published data on its leak site; the leak site was not accessed (research boundaries). The consolidated class actions (Hulse v. Acadian, W.D. La.) allege negligence in protecting data; these are allegations and were not used as evidence. The response/disclosure condition (leak-triggered disclosure, statements omitting the ransom demand) is described in the rationale but not coded RM39: notification was reported as within statutory deadlines, so the marker's exclusion condition is not cleared. Unattended run: no source required an action needing consent; none was taken. Link check: theadvocate.com blocks automated access (HTTP 429); the page was opened and read during research. Link check: databreaches.net 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.