It's a story about the biggest shipping company in the world and the day a single line of code brought it , and a measurable slice of global economy , to a dead stop . It begins not on a container ship , but in an office in Ukraine with an accounting software update that was actually a declaration of war . All righty , then . Ladies and gentlemen , welcome back to another episode of Privacy , please . I'm your host , cameron Ivey , and today's episode is a brand new series called Digital Fallout , where I'll go behind the headlines to tell the real stories of our digital world . Before we jump into today's story , a quick but important note for our listeners . The events I'll be discussing today are based on real-world incidents , and our narrative is built upon extensive public reporting for reputable news outlets , official company statements and security researchers . We've synthesized this information to create a compelling story , but it is not a direct firsthand account . A compelling story , but it is not a direct firsthand account and , as always , while we discuss legal and security topics , I am not a lawyer or a security professional providing advice . The content of this podcast is for informational and educational purposes only . Now , with that being said , let's get into this week's story .
Speaker 1In June of
2017 , an IT worker at the Maersk headquarters in Denmark noticed a few computers acting strangely . Then a few more , within minutes , screens across the office went black , replaced with a red and black ransom note demanding Bitcoin . But then the phone started ringing . It wasn't just them , it was their office in Rotterdam , in New Jersey , in Mumbai . One by one , across 130 countries , the digital eyes and ears of the world's largest shipping company were going blind . The digital heartbeat that scheduled and tracked 76,000 sailors and nearly 4 million shipping containers
. Flatlined Ships worth billions carrying untold cargo , were suddenly adrift in a digital ocean with no way to dock . This wasn't a typical ransomware attack . You see .
Speaker 1The forensics team quickly realized the payment system on the ransom note was fake . The malware wasn't designed to hold data hostage . It was designed to wipe it from existence . This was a weapon , not a crime . They traced its origin to a hijacked update from a popular Ukrainian tax software called MEDOC . The worm , later dubbed NotPetya , had been unleashed , likely by Russian state hackers , as an act of cyberwar against Ukraine , and Marysk had become catastrophic collateral damage . Catastrophic collateral damage . The race was on .
Speaker 1The global IT team at Maersk was in a frantic search for what they called a digital Adam and Eve a single uninfected computer that could be used to rebuild their entire global network from scratch . They had backups , but the system that managed and authenticated the backups was also destroyed . It was a fortress without a blueprint . Every server they checked was corrupted . For days
the multi-billion dollar company was run on WhatsApp , post-it notes and personal cell phones . It looked like their entire digital kingdom , built over decades , had been completely and permanently erased in just seven minutes . And then , a miracle , a call came in from an office in Accra , ghana . A routine power outage had knocked their local server offline . Just before the attack hit , it was disconnected from the network at the same moment . The digital plague was spreading . That server , kept safe by a random blackout , was the only machine left in the world that contained a copy of their global user directory . It was flown like a precious artifact to the UK single server .
Speaker 1A heroic team of engineers worked non-stop for 10 days to rebuild Maersk's entire 4,000 server , 45,000 PC network . The fallout was immense A $300 million financial loss for Maersk and a terrifying lesson for the world . It proved that a geopolitical conflict in one corner of the world could instantly paralyze a Danish shipping company and disrupt global supply chains . The Napetia attack . It wasn't just a data breach . It was the moment the world saw how fragile
our interconnected society truly is . It was the day the code became a weapon . It's a powerful reminder of how interconnected and vulnerable our world truly is .
Speaker 1And that brings us to the end of our episode . A final thank you to the incredible journalists and researchers whose work made this story possible . Our account today was built on reporting from sources like Wired Magazine , the New York Times and the hard and countless work of security professionals who analyze these events , so we can all learn from them . For a list of our primary resources for today's story , please check our show notes . Thanks for joining us on today's journey . Until next time , stay curious , stay safe . You've been listening to Privacy , please . And thank you so much for tuning in . I hope you enjoyed this story . I hope you enjoyed this format . I would love to hear from you because , if you like it , I'll keep doing it . I really enjoy telling stories and , yeah , so I'll see you guys next week . Thanks for tuning in .