Skip to content
Post Mortem

Biggest cases ยท May 7, 2021

Colonial Pipeline: one password and a week of fuel shortages

Ransomware hit the billing side of a pipeline company. As a precaution it shut the whole pipeline, and fuel shortages followed along the US East Coast.

CRITICALransomwareenergymfainfrastructure

Details may change as reporting changes. Information comes from the linked sources, and we do not guarantee it is complete or current.

Why it is on the listThe most disruptive ransomware attack on critical infrastructure in the US, and a turning point in how governments treat ransomware.

In plain English

The criminals did not touch the machines that push fuel through the pipes. They locked the company's business computers, the ones used for billing and tracking. Colonial could not be sure it could bill for fuel or track it safely, so it shut the pipeline itself.

That one decision, made as a precaution, caused queues and shortages at petrol stations along the East Coast for days.

The way in was a single old remote-access (VPN) account. It had no second login step, and its password was later found in a batch of leaked passwords.

Words used here

VPN
A private tunnel that lets staff reach company systems from outside the office.
MFA
A second proof you are you, such as a code on your phone. Stops a stolen password working on its own.
Precautionary shutdown
Turning off something that still works because you cannot be sure it is safe.

What happened

The DarkSide ransomware group locked Colonial's IT systems on May 7, 2021. The company, whose pipeline is more than 5,500 miles long and supplies nearly half of the East Coast's fuel, halted operations.

A Mandiant executive told Congress the attackers got in through an exposed password for a VPN account. The company's operational technology, the systems that actually move fuel, was not directly compromised.

Colonial paid a ransom of about 75 bitcoin, roughly $4.4 million. The Justice Department later announced it had seized about $2.3 million of it.

How it unfolded

  1. May 7, 2021

    Ransomware found on business systems. Pipeline shut down.

  2. May 9 to 12

    Emergency declarations and queues at stations. Colonial restarts around May 12.

  3. June 2021

    The Justice Department announces it recovered part of the ransom.

Who was affected

Colonial, and millions of drivers and businesses along the US East Coast who had trouble getting fuel for several days.

What the response was

  • Colonial shut down the pipeline, called the FBI and paid the ransom to obtain a decryption tool.
  • US agencies launched a joint ransomware effort and the stopransomware.gov site.

What went wrong

  • A legacy VPN account without a second login step was still active.
  • The IT and operations sides were so linked that a billing problem meant shutting the pipeline.

What worked

  • Calling the FBI immediately led to the later recovery of part of the ransom.
  • Operational systems were not hit, which sped up the restart.

What organisations should do differently

  • Turn on MFA for every remote-access account, and delete accounts nobody uses.
  • Keep billing and business systems separate enough that you can run operations without them.
  • Decide ahead of time who can order a shutdown and what you will tell the public.

What you can do today

  • Turn on MFA on email, remote access and admin accounts.
  • Delete old accounts of people and tools that left.
  • Check for your own passwords in leaked lists at a service like Have I Been Pwned.

The lesson that still holds

One unprotected login can cost a week of business. Second factor on everything that reaches in from outside, and remove what you no longer use.

Sources

Finished this one?

Add it to What I learned and earn 40 Trust. You can open your list from the badge at the bottom of the page.