Attacks/Breaches

6/29/2017
07:23 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
100%
0%

Decrypting the Motivations Behind NotPetya/ExPetr/GoldenEye

Experts discuss the methods and targets involved in this week's massive malware outbreak to figure out what motivated attackers.

This week's massive ransomware outbreak has left security experts grappling to understand the "who" and "why" behind the attack, which mostly affected organizations in Ukraine and also reached businesses in an estimated 60 countries.

The malware at work is going by several names. Many researchers, noting similarities with the Petya malware, have simply declared this malware Petya. Others call it NotPetya. Some call it GoldenEye, which is a variant of Petya. Kaspersky Lab found similarities with a Petya modification called PetrWrap, and has dubbed it ExPetr.

Experts are piecing together the many updates and findings about this malware to figure out what happened.

"It's really, really hard right now to identify motivation," says Adam Kujawa, head of malware intelligence at Malwarebytes. "A lot of the security industry is struggling to figure out what's going on and why it's happening."

However, a few findings could help determine the motivation behind this attack:

Ukraine was a target

All of its many nicknames refer to the same malware, which has been largely wreaking havoc through MeDoc, an accounting software primarily used in Ukraine. Analysis indicates MeDoc's update server was compromised and as a result, any machine running the software would be hit with malware during an automatic update. From there, it rapidly spreads to other machines.

MeDoc is required software in Ukraine, an interesting and critical point in discussing the attacker's motivations. Some reports state the country's computer infrastructure was likely the primary target.

Travis Farral, director of security strategy at Anomali, says it's interesting that this malware only spreads within an organization and not outside it. It could cripple organizations in Ukraine; in most cases, the outside companies affected either did business in Ukraine or worked with third parties that did business there.

"One could make the argument that they wanted to limit it to Ukrainian institutions because they had no mechanism to go beyond this targeting," he explains. "Anyone running the software is at risk."

This was never about money

"It doesn't appear financial gain was the intent," Kujawa says. "A lot of analysis has come to light saying it wouldn't be possible to decrypt the files anyway."

The malware overwrites the Master Boot Record (MBR) and encrypts individual files matching a list of file extensions. It requests $300 in Bitcoin to decrypt the system but despite an estimated $3,000 in payments, there has been no record of victims successfully decrypting their files.

While the malware is technically based on ransomware, Kujawa describes it as "wearing a ransomware costume." He suggests the actor intentionally made decryption impossible as a means of disrupting operations and harming users wherever it hit.

Black Hat USA returns to the fabulous Mandalay Bay in Las Vegas, Nevada, July 22-27, 2017. Click for information on the conference schedule and to register.

Farral says it's interesting that the actors put significant engineering effort into making the malware spread throughout the victim business but did not put a lot of effort into being able to collect ransom. Even WannaCry had multiple Bitcoin wallets, he notes.

"A piece of ransomware like that should be focused on gathering money for its operators," says Bitdefender senior security analyst Bogdan Botezatu. Here, he says, this was not the case.

"This was not a technique used for moneymaking," he says. "This is a technique used for destroying data and disrupting businesses."

Critical infrastructure was a target

Kaspersky analysis indicates more than 50% of businesses targeted by this malware are industrial companies. Threats like this are especially dangerous for critical infrastructure because they can potentially affect the victim's automation and control systems.

Botezatu also says the first entities to get infected were critical infrastructure networks like airports, gas and utility companies, public transportation, and banks. "We realized there were more businesses affected than regular consumers," he explains.

It could be a hacktivist ... or a nation-state

"This doesn't have the same signs as state-sponsored malware, at least from the bigger countries we've seen in cybercrime,"  says Kujawa, noting that nation-state threats are typically more secretive.

This could lend credibility to the idea that this was conducted by a hacktivist or black hat organization trying to bring awareness to the insecurities of the modern Internet. It's a loud attack, one that makes it seem like someone is trying to garner attention.

However, Farral says, this lack of complexity could also indicate a nation-state trying to cover its tracks.

"This hit Ukraine very broadly," he notes. "If you want to disguise you're a nation-state and did that, you could make it look like another WannaCry-type ransomware that's designed to spread using the same mechanisms. In that way there's plausible deniability -- this isn't a nation-state, it's just a hacker trying to make money."

Ido Wulkan, intelligence team lead at IntSights, says this threat actor has done damage before.

"What we know for sure is this threat actor has been around for at least two months and has been involved in previous campaigns," he says, recalling similarities between this incident and a campaign for infecting IoT botnets for DDoS attacks two months ago.

While Wulkan suggests this threat is more sophisticated, state-sponsored threats are typically more advanced. However, if the goal was sabotage, there is no need for using undiscovered malware. Even some state actors are reusing tools or using common tools to cover their tracks.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Privacy Careers Are Helping to Close the IT Gender Gap
Dana Simberkoff, Chief Risk, Privacy, and Information Security Officer, AvePoint, Inc.,  8/20/2018
Ohio Man Sentenced To 15 Months For BEC Scam
Dark Reading Staff 8/20/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15667
PUBLISHED: 2018-08-21
An issue was discovered in Bloop Airmail 3 3.5.9 for macOS. It registers and uses the airmail:// URL scheme. The "send" command in the URL scheme allows an external application to send arbitrary emails from an active account without authentication. The handler has no restriction on who can...
CVE-2018-15668
PUBLISHED: 2018-08-21
An issue was discovered in Bloop Airmail 3 3.5.9 for macOS. The "send" command in the airmail:// URL scheme allows an external application to send arbitrary emails from an active account. URL parameters for the "send" command with the "attachment_" prefix designate atta...
CVE-2018-15669
PUBLISHED: 2018-08-21
An issue was discovered in Bloop Airmail 3 3.5.9 for macOS. Its primary WebView instance implements "webView:decidePolicyForNavigationAction:request:frame:decisionListener:" such that requests from HTMLIFrameElements are blacklisted. However, other sub-classes of HTMLFrameOwnerElements are...
CVE-2018-15670
PUBLISHED: 2018-08-21
An issue was discovered in Bloop Airmail 3 3.5.9 for macOS. Its primary WebView instance implements "webView:decidePolicyForNavigationAction:request:frame:decisionListener:" such that OpenURL is the default URL handler. A navigation request is processed by the default URL handler only if t...
CVE-2018-15671
PUBLISHED: 2018-08-21
An issue was discovered in the HDF HDF5 1.10.2 library. Excessive stack consumption has been detected in the function H5P__get_cb() in H5Pint.c during an attempted parse of a crafted HDF file. This results in denial of service.