Maersk Frankfurt heads for open water as container fire subsides
Maersk Frankfurt, the newbuild box ship that suffered a possible electrical fault and subsequent container ...
TFII: SOLID AS USUALMAERSK: WEAKENINGF: FALLING OFF A CLIFFAAPL: 'BOTTLENECK IN MAINLAND CHINA'AAPL: CHINA TRENDSDHL: GROWTH CAPEXR: ANOTHER SOLID DELIVERYMFT: HERE COMES THE FALLDSV: LOOK AT SCHENKER PERFORMANCEUPS: A WAVE OF DOWNGRADES DSV: BARGAIN BINKNX: EARNINGS OUTODFL: RISING AND FALLING AND THEN RISING
TFII: SOLID AS USUALMAERSK: WEAKENINGF: FALLING OFF A CLIFFAAPL: 'BOTTLENECK IN MAINLAND CHINA'AAPL: CHINA TRENDSDHL: GROWTH CAPEXR: ANOTHER SOLID DELIVERYMFT: HERE COMES THE FALLDSV: LOOK AT SCHENKER PERFORMANCEUPS: A WAVE OF DOWNGRADES DSV: BARGAIN BINKNX: EARNINGS OUTODFL: RISING AND FALLING AND THEN RISING
Reading like an airport thriller, this Wired story of the infamous NotPetya cyber attack recounts the panic spreading through Maersk’s HQ in Copenhagen that summer morning when its IT system became infected. “Maersk employees were running down hallways, yelling to their colleagues to turn off computers or disconnect them from Maersk’s network before the malicious software could infect them, as it dawned on them that every minute could mean dozens or hundreds more corrupted PCs. Tech workers ran into conference rooms and unplugged machines in the middle of meetings. Soon staffers were hurdling over locked key-card gates…” This is in-depth account of the hows and whys of NotPetya is the most definitive yet, and also confirms the increasingly common view that Maersk was not the object of the cyber attack, just collateral damage.
Comment on this article