September 13, 2018
-
Kailyn Johnson
,

Evaluating the Threatscape One Year After NotPetya Ransomware Attack

<h4><em>The NotPetya cyber-attack occurred a little over a month after WannaCry, targeting Ukrainian </em><em>organisations</em><em>. </em></h4><p>The attack was initiated utilising a corrupted update for an accounting and tax software that was almost exclusively used throughout every organisation, private and public, in the country. The malware employed the same SMB exploit that WannaCry leveraged to propagate inside networks, which was effective as many organisations still had yet to apply the patch that was released in early 2017.  Even organisations that had applied the patch to this Microsoft vulnerability were susceptible to infection from the NotPetya malware because it also employed a credential harvesting tool called “Mimikatz” which automates the collection of credentials on Windows systems. This allowed the malware to spread within networks even if the “Eternal Blue” SMB exploit was fixed. Because of the dual propagation technique, the malware could infect organisations external to Ukraine that had an office or branch in the country.</p><h4><em>This cyber attack was one of the most financially costly attacks in recent history, causing over $10 billion USD in lost revenue internationally. </em></h4><p>The malware encrypted every machine on an infected network, and although the malware was disguised as ransomware since it encrypted 65 specific types of files on a machine, it ultimately was designed to act as a wiper and prevented users from being able to retrieve their files back even if they paid the ransom. Security researchers later deemed that the malware’s wiping functionality was the actual intention of the threat actors. Over 70% of victims originated within Ukraine and the attack occurred on the eve of their Independence Day following the fall of the Soviet Union. This prompted many researchers to believe that Russian state-sponsored threat actors were most likely the perpetrators behind these attacks because of the use of the Ukrainian accounting software as the initial attack vector, the specific targeting of Ukraine, and the fact it preceded their independence day.<br/> <br/> The report included in this blog, will also discuss the consequences of the NotPetya attack for organisations, which were quite severe for many commercial and governmental entities. This attack highlighted repercussions that can have rebounding impacts on secondary and tertiary victims that were not the primary target due to failures from third-party vendors and general organisational policies. Some of the key lessons discussed in this white paper include: swiftly applying security patches, especially when a recent incident exploited those easily-fixed vulnerabilities, the necessity for third-party vendors to protect the signature and certificate of legitimacy of their code and software products that organisations use, improved awareness of current cyber threat trends and pre-existing mitigations, and following the 3-2-1 rule when storing and backing up data.</p><p>The goal of this report is to call attention to the pre-existing security weaknesses businesses and organisations have to help inform the development of new policies and procedures to mitigate these for improved resilience towards cyber threats. Threats are constantly evolving and adapting quicker than organisations are able to mitigate them, meaning it is crucial to continually develop proactive policies as well as ensure pre-existing vulnerabilities are abated.</p><p><a href="https://www.anomali.com/resources/whitepapers/notpetya-one-year-later?cid=7011Y0000011IFL" target="_blank"><strong>Download the Report</strong></a></p>

Get the Latest Anomali Updates and Cybersecurity News – Straight To Your Inbox

Become a subscriber to the Anomali Newsletter
Receive a monthly summary of our latest threat intelligence content, research, news, events, and more.