Petya (malware)

Petya was discovered in March 2016;[6] Check Point noted that while it had achieved fewer infections than other ransomware active in early 2016, such as CryptoWall, it contained notable differences in operation that caused it to be "immediately flagged as the next step in ransomware evolution".[1] Another variant of Petya discovered in May 2016 contained a secondary payload used if the malware cannot achieve administrator-level access.[6]

The name "Petya" is a reference to the 1995 James Bond film GoldenEye, wherein Petya is one of the two Soviet weapon satellites which carry a "Goldeneye"—an atomic bomb detonated in low Earth orbit to produce an electromagnetic pulse. A Twitter account that Heise suggested may have belonged to the author of the malware, named "Janus Cybercrime Solutions" after Alec Trevelyan's crime group in GoldenEye, had an avatar with an image of GoldenEye character Boris Grishenko, a Russian hacker and antagonist in the film played by Scottish actor Alan Cumming.[7]

On 30 August 2018, a regional court in Nikopol in the Dnipropetrovsk Oblast of Ukraine convicted an unnamed Ukrainian citizen to one year in prison after pleading guilty to having spread a version of Petya online.[8][9][10]

NotPetya's ransom note displayed on a compromised system

On 27 June 2017, a major global cyberattack began (Ukrainian companies were among the first to state they were being attacked[11]), utilizing a new variant of Petya. On that day, Kaspersky Lab reported infections in France, Germany, Italy, Poland, the United Kingdom, and the United States, but that the majority of infections targeted Russia and Ukraine, where more than 80 companies were initially attacked, including the National Bank of Ukraine.[11][12] ESET estimated on 28 June 2017 that 80% of all infections were in Ukraine, with Germany second hardest hit with about 9%.[13] Russian president Vladimir Putin's press secretary, Dmitry Peskov, stated that the attack had caused no serious damage in Russia.[13] Experts believed this was a politically-motivated attack against Ukraine, since it occurred on the eve of the Ukrainian holiday Constitution Day.[14][15]

Kaspersky dubbed this variant "NotPetya", as it has major differences in its operations in comparison to earlier variants.[11] McAfee engineer Christiaan Beek stated that this variant was designed to spread quickly, and that it had been targeting "complete energy companies, the power grid, bus stations, gas stations, the airport, and banks".[11][16]

It was believed that the software update mechanism of M.E.Doc—a Ukrainian tax preparation program that, according to F-Secure analyst Mikko Hyppönen, "appears to be de facto" among companies doing business in the country—had been compromised to spread the malware.[13][17][18] Analysis by ESET found that a backdoor had been present in the update system for at least six weeks prior to the attack, describing it as a "thoroughly well-planned and well-executed operation".[19] The developers of M.E.Doc denied that they were entirely responsible for the cyberattack, stating that they too were victims.[17][20][21][22]

On 4 July 2017, Ukraine's cybercrime unit seized the company's servers after detecting "new activity" that it believed would result in "uncontrolled proliferation" of malware. Ukraine police advised M.E.Doc users to stop using the software, as it presumed that the backdoor was still present.[19][23] Analysis of the seized servers showed that software updates had not been applied since 2013, there was evidence of Russian presence, and an employee's account on the servers had been compromised; the head of the units warned that M.E.Doc could be found criminally responsible for enabling the attack because of its negligence in maintaining the security of their servers.[19][22][24]

Petya's payload infects the computer's master boot record (MBR), overwrites the Windows bootloader, and triggers a restart. Upon startup, the payload encrypts the Master File Table of the NTFS file system, and then displays the ransom message demanding a payment made in Bitcoin.[6][25][26] Meanwhile, the computer's screen displays text purportedly output by chkdsk, Windows' file system scanner, suggesting that the hard drive's sectors are being repaired.[1]

The original payload required the user to grant it administrative privileges; one variant of Petya was bundled with a second payload, Mischa, which activated if Petya failed to install. Mischa is a more conventional ransomware payload that encrypts user documents, as well as executable files, and does not require administrative privileges to execute.[6] The earlier versions of Petya disguised their payload as a PDF file, attached to an e-mail.[6] United States Computer Emergency Response Team (US-CERT) and National Cybersecurity and Communications Integration Center (NCCIC) released Malware Initial Findings Report (MIFR) about Petya on 30 June 2017.[27]

The "NotPetya" variant used in the 2017 attack uses EternalBlue, an exploit that takes advantage of a vulnerability in Windows' Server Message Block (SMB) protocol. EternalBlue is generally believed to have been developed by the U.S. National Security Agency (NSA);[26] it was leaked in April 2017 and was also used by WannaCry.[26][28] The malware harvests passwords (using tweaked build of open-source Mimikatz[29]) and uses other techniques to spread to other computers on the same network, and uses those passwords in conjunction with PSExec to run code on other local computers.[30][31][32] Additionally, although it still purports to be ransomware, the encryption routine was modified so that the malware could not technically revert its changes.[33] This characteristic, along with other unusual signs in comparison to WannaCry (including the relatively low unlock fee of US$300, and using a single, fixed Bitcoin wallet to collect ransom payments rather than generating a unique ID for each specific infection for tracking purposes),[34] prompted researchers to speculate that this attack was not intended to be a profit-generating venture, but to damage devices quickly, and ride off the media attention WannaCry received by claiming to be ransomware.[35][36]

It was found that it may be possible to stop the encryption process if an infected computer is immediately shut down when the fictitious chkdsk screen appears,[37] and a security analyst proposed that creating read-only files named perf.c and/or perfc.dat in the Windows installation directory could prevent the payload of the current strain from executing.[38][39][40][41] The email address listed on the ransom screen was suspended by its provider, Posteo, for being a violation of its terms of use. As a result, infected users could not actually send the required payment confirmation to the perpetrator.[34][42]Additionally, if the computer's filesystem was FAT based, the MFT encryption sequence was skipped, and only the ransomware's message was displayed, allowing data to be recovered trivially.[43]

Microsoft had already released patches for supported versions of Windows in March 2017 to address the EternalBlue vulnerability. This was followed by patches for unsupported versions of Windows (such as Windows XP) in May 2017, in the direct wake of WannaCry.[44][45] Wired believed that "based on the extent of damage Petya has caused so far, though, it appears that many companies have put off patching, despite the clear and potentially devastating threat of a similar ransomware spread."[46] Some enterprises may consider it too disruptive to install updates on certain systems, either due to possible downtime or compatibility concerns, which can be problematic in some environments.[44]

In a report published by Wired, a White House assessment pegged the total damages brought about by NotPetya to more than $10 billion. This was confirmed by former Homeland Security adviser Tom Bossert, who at the time of the attack was the most senior cybersecurity focused official in the US government.[47]

During the attack initiated on 27 June 2017, the radiation monitoring system at Ukraine's Chernobyl Nuclear Power Plant went offline.[48] Several Ukrainian ministries, banks and metro systems were also affected.[49] It is said to have been the most destructive cyberattack ever.[50]

Among those affected elsewhere included British advertising company WPP,[49] Maersk Line,[51] American pharmaceutical company Merck & Co., Russian oil company Rosneft (its oil production was unaffected[52]), multinational law firm DLA Piper,[49] French construction company Saint-Gobain and its retail and subsidiary outlets in Estonia,[53] British consumer goods company Reckitt Benckiser,[54] German personal care company Beiersdorf, German logistics company DHL,[55] United States food company Mondelez International, and American hospital operator Heritage Valley Health System.[11][56] The Cadbury's Chocolate Factory in Hobart, Tasmania, is the first company in Australia to be affected by Petya.[57] On 28 June 2017, JNPT, India's largest container port, had reportedly been affected, with all operations coming to a standstill.[58] Princeton Community Hospital in rural West Virginia will scrap and replace its entire computer network on its path to recovery.[59]

The business interruption to Maersk, the world's largest container ship and supply vessel operator, was estimated between $200m and $300m in lost revenues.[60]

The business impact on FedEx is estimated to be $400m in 2018, according to the company's 2019 annual report.[61]

Jens Stoltenberg, NATO Secretary-General, pressed the alliance to strengthen its cyber defenses, saying that a cyberattack could trigger the Article 5 principle of collective defense.[62][63]

Mondelez International's insurance carrier, Zurich American Insurance Company, has refused to pay out a claim for cleaning up damage from a Notpetya infection, on the grounds that Notpetya is an "act of war" that is not covered by the policy. Mondelez is suing Zurich American for $100 million.[64]

Europol said it was aware of and urgently responding to reports of a cyber attack in member states of the European Union.[12] The United States Department of Homeland Security was involved and coordinating with its international and local partners.[51] In a letter to the NSA,[65] Democratic Congressman Ted Lieu asked the agency to collaborate more actively with technology companies to notify them of software vulnerabilities and help them prevent future attacks based on malware created by the NSA.[32][66] On 15 February 2018, the Trump administration blamed Russia for the attack and warned that there would be "international consequences".[67] The United Kingdom and the Australian government also issued similar statements.[68]

In October 2020 the DOJ named further GRU officers in an indictment.[69] At the same time, the UK government blamed GRU's Sandworm also for attacks on the 2020 Summer Games.[70]

• CIH (1998)
• Stuxnet (2010)
• WannaCry (2017)

•  Law portal
•  Internet portal