2021 · United States · H - Transport and storage · Ransomware attack with data theft and operational shutdown
Analysed 2026-11-07 by Hermes
Open this case in the tool →Ransomware attack with data theft and operational shutdown
Expertise to Execution
Evidence coverage: 3/6 stages, weight 25/60
Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution
(1) Colonial Pipeline is the largest US refined-products pipeline and a designated critical-infrastructure operator; protecting remote access was an explicit, operationalised expectation at the company - Blount told the Senate that in normal operation it used RSA tokens for remote access, and the CISA/FBI advisory of 11 May 2021 names MFA on remote access as a basic expectation for just this threat. (2) In practice a DarkSide affiliate logged in on 29 April 2021 with an employee username and password over a legacy VPN profile that was not intended to be in use, was never required to present a one-time passcode, and whose password surfaced in a dark-web leak batch; the intrusion sat undetected for eight days until a ransom note appeared on 7 May, roughly 100 GB had left the share drive unnoticed, and only the IT network was contained by the company's own prompt IT/OT separation and 15-minute shutdown. (3) This is a knowing-doing gap inside the material column, not weak security in general: every load-bearing remedy - MFA on remote access, retiring an unused VPN profile and account, detecting an interactive intruder and bulk egress - was technically known and, for MFA, already deployed elsewhere at the company; the primary sources (the CEO's own testimony and Mandiant's forensic testimony) document no leadership decision that deferred, under-funded or accepted the gap, so the chain broke where the known control was not realised in the operational architecture. The classification rests on the entry stage (clearest evidence: both origin and break documented by primary sources); the same material-to-execution pattern recurs at detection and egress, while containment, recovery and response are documented as aligned; the entry vector itself is not what makes the type - the documented non-execution of an existing remedy is. RM22 (Expertise to Execution lens): identity controls failed exactly where experts knew how to implement them - a single-factor legacy VPN profile and a disused account with a leaked, never-detected password stayed live, because the credential-lifecycle and MFA controls were not applied to that legacy path (causal role: Enabling). RM15 (Expertise to Execution lens): a forgotten exposure path - a legacy VPN profile not intended to be in use yet still reachable - plus days without a view into the corrupted environment shows technical teams lacked an accurate picture of accounts and exposure when they had to scope and respond (causal role: Enabling). RM34 (Expertise to Execution lens): an eight-day dwell ending in discovery via the attacker's own ransom note shows available monitoring was not configured or tuned to surface the intrusion in time (causal role: Obscuring). RM35 (Expertise to Execution lens): roughly 100 GB staged and exfiltrated from the share drive in hours without interruption, learned of only from the ransom note, shows egress monitoring was not realised for a crown-jewel critical-infrastructure network (causal role: Amplifying).
RM22 — Authentication / credential exposureRM15 — Asset / exposure visibility gapRM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapBoth source_url leads in the case file are dead as cited (CNN article 404; CISA 2021-05-11 alert page moved after the CISA redesign): the CNN lead was replaced by the Bloomberg article it sourced (opened via the opened Wayback snapshot) plus its Al Jazeera copy, and the CISA lead by the current CISA/FBI advisory PDF AA21-131A opened from cisa.gov. The DOJ ransom-seizure release is cited from the archived justice.gov URL (opened via an opened Wayback snapshot). Case-file description matches the stated victim (compromised password + DarkSide best-practices sources); no data-quality mismatch. Related row 1347 (EuRepoC, Colonial Pipeline Hack): its case file row-1347.json is not present in cases-run500 and no result-1347.json exists in the output directory, so it could not be read or aligned; it appears to describe the same incident. Origin of the credential is not fully resolved: Mandiant found no phishing of the employee and said investigators may never know for certain how the password was obtained; the dark-web leak batch is the reported suspicion, per the Bloomberg interview. The exact ransom (~75 BTC, about $4.4m, paid 8 May 2021) and the DOJ seizure of 63.7 BTC are per the DOJ release. Unattended run: nothing encountered required consent; no leak sites or stolen data were accessed.