Ransomware Hits a Logistics Firm: The Decision to Pay, Wait, or Rebuild
Archi4 min read
Contents
The 72-Hour Window#
At 2:14 a.m. on a Tuesday, the dispatch system at a mid-sized freight broker stopped accepting new loads. By 6 a.m., the company's operations team had confirmed what the night shift suspected: ransomware had encrypted the scheduling database, the driver communication platform, and the billing archive. A note on the screen demanded payment in cryptocurrency within 72 hours.
The company, which asked not to be named while the incident is under investigation, moves roughly 1,200 loads a day across the central United States. Every hour the dispatch system stayed dark, trailers sat idle and drivers called in for instructions that nobody could give.
What followed was not a single decision but a sequence of them, each shaped by incomplete information and a clock that would not stop.
The first call: isolate and assess#
The IT director made the call to pull the plug on the corporate network within the first hour. That move stopped the spread to two regional offices but also cut off the company's email, its phone system, and the shared drive where contracts lived. Operations shifted to personal phones and a whiteboard.
By midday, the security team had a rough map. The attackers had entered through a compromised remote-access account belonging to a former contractor whose credentials had never been revoked. The encryption had reached the backup server because the backup server was on the same network and used the same domain credentials.
That detail changed the shape of the decision. The company had backups. It did not have clean backups.
Pay, restore, or rebuild#
The executive team met at 7 p.m. in a conference room with a projector that still worked because it was not connected to anything. Three options sat on the table.
Paying, the attackers implied through a chat portal, would bring a decryption key within hours. The price was quoted in the low six figures. Restoring from backup would take an estimated four to six days, and the most recent verified backup was 11 days old. Rebuilding from scratch meant new hardware, new identity systems, and a manual reconstruction of customer records that existed only in encrypted form.
No option was clean. Each carried a cost that was partly financial and partly operational.
What the lawyers said#
The company's outside counsel raised a point that reframed the conversation. Under the insurer's policy, paying a ransom required notifying the carrier and, depending on the amount, potential disclosure to federal authorities. The insurer had its own incident response firm, and that firm had seen this particular ransomware family before. In several prior cases, the decryption tool provided after payment worked partially. Files were corrupted. Databases came back with missing indexes.
The response firm's assessment was blunt: payment would likely restore some files and not others. The company would still need to rebuild. Paying would buy time, not a solution.
The decision#
The CEO made the call just after midnight. The company would not pay. It would rebuild from the 11-day-old backup, reconcile the gap by contacting customers directly, and use the incident as the trigger to replace the flat network with segmented infrastructure.
The reasoning was not moral. It was arithmetic. A partial decryption plus a rebuild cost more than a rebuild alone, and the 72-hour deadline was a pressure tactic, not a technical constraint.
The week that followed#
Restoring the backup took 38 hours. Reconciling the 11-day gap took six people working in shifts for four days. The company lost an estimated 340 loads to competitors and paid overtime that erased the quarter's margin.
Two things went right. The company had a printed customer contact list in a filing cabinet, a relic of an older era that turned out to be the most reliable asset in the building. And the drivers, who had no access to the dispatch platform, kept moving freight by phone and text.
What the logs showed afterward#
The post-incident review found three failures that mattered more than the ransomware itself. The contractor account had been active for 14 months after the contract ended. The backup system shared credentials with the production domain. And the company had no tested procedure for operating without its primary systems.
None of those failures required sophisticated attackers to exploit. They required only patience.
The company now runs quarterly restore tests and has moved backups to a separate identity system. The former contractor account was disabled the morning after the incident, along with 60 others that nobody could justify.
The decision that keeps recurring#
For the security team, the hardest part was not the initial call. It was the second decision, made three weeks later, to tell customers the full scope of what had been exposed. That disclosure cost the company two accounts. It also produced a referral from a shipper who had been through the same thing and valued the honesty.
The company is still operating. Its dispatch system is new. The whiteboard from that Tuesday is still in the conference room, and nobody has erased it.
More articles