Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security //

Ransomware

1/14/2019
09:35 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

Ryuk Ransomware Origin Remains a Mystery

After shutting down newspaper printing facilities, as well as a cloud hosting firm, security researchers are debating who is behind the Ryuk ransomware. While it seemed that North Korea played a role, more research shows that a Russian gang might be responsible.

In the murky world of cybercrime, it's not easy to tell who or what is behind a given attack. While some evidence might point to a nation-state attempting espionage, a criminal gang might be trying to cover its tracks, and the lines can even blur more as malware is bought and sold on underground forums open to anyone with cash and the know-how.

Consider the Ryuk ransomware as an example.

At the end of 2018, the printing presses of the Tribune Publishing company suffered a cyber attack attributed to Ryuk. Later, journalist Brian Krebs reported that Data Resolution, which provides cloud and other hosting services for about 30,000 customers, also suffered an attack by the same malware. (See Ryuk Ransomware Tied to Printing Press & Cloud Service Provider Attacks.)

Like SamSam before it, Ryuk is a much more targeted piece of ransomware that specifically encrypts critical systems within a network. It's also relatively new with Check Point Research publishing a detailed analysis of the malware less than six months ago

.

Within that analysis Check Point researchers found that Ryuk shared some of the same source code as another piece of ransomware called Hermes, which would indicate that both strains are tied to the Lazarus Group, the well-known North Korean-backed Advanced Persistent Threat (APT) group known for attacks ranging from the hack of Sony Pictures to the WannaCry ransomware of 2017.

However, looks can be deceiving.

Following the Ryuk attacks in late 2018, McAfee, FireEye and CrowdStrike published separate assessments of these incidents, which all seem to point the finger away from North Korea and Lazarus and to a Russian group, which does not appear to be state-sanctioned but purely criminal in nature. (See APTs in 2018: A Mix of Old & New.)

In CrowdStrike's analysis, researcher point to a group known as Grim Spider, a cybercrime group that works out of Russia, which itself might be a sub-group of another gang called Wizard Spider, which specializes in banking malware, especially a strain called TrickBot.

The analysis points to several factors linking the group to Ryuk, including that fact that Russian-speaking forums began circulating information about the source code, and that the ransomware did not work in Russia, the Ukraine or Belarus, which would protect the hosts from their own attack.

Notably, the research finds that Hermes source code is available on various underground forums and that the malware is under continuous development. The report notes:

Code comparison between versions of Ryuk and Hermes ransomware indicates that Ryuk was derived from the Hermes source code and has been under steady development since its release. Hermes is commodity ransomware that has been observed for sale on forums and used by multiple threat actors. However, Ryuk is only used by GRIM SPIDER and, unlike Hermes, Ryuk has only been used to target enterprise environments.

The FireEye and CrowdStrike reports point out that several of the Ryuk ransomware attacks also involve the TrickBot malware, which again ties the two together and points back to a Russian-backed group.

However, there's always a possibility that Hermes started inside a Russia and was sold to other groups, including North Korea, which could have used it to disguise their own activity. For example, McAfee finds that the 2.1 version of the malware was used to rob a bank in Taiwan. Before that attack, a Russian forum advertised a version of the source code and the kit to use all for the price of $300.

"That was October 2017. Searching earlier events, we noticed a posting from August 2017 in an underground forum in which a Russian-speaking actor offered the malware kit Hermes 2.1 ransomware," according to the McAfee report. "What if the actor who attacked the Taiwanese bank simply bought a copy of Hermes and added it to the campaign to cause the distraction? Why go to the trouble to build something, when the actor can just buy the perfect distraction in an underground forum?"

In an email, John Fokker, the head of Cyber Investigations at McAfee, noted that this type of "borrowing" of malware source code happens frequently. He noted the recent Oceansalt campaign also used a similar technique. (See McAfee: Seasalt Malware Raises Its Head Again.)

Fokker added that finding the actual threat actor behind any attack is difficult since even the best researchers sometimes only have small pieces of the puzzle.

"Attribution is always hard, and this ransomware family isn't any different," Fokker told Security Now. "As a security company we only have some pieces of the puzzle. Especially when an attack first appears it is [more] important to focus on what we are good at (malware analysis and incident response) than trying to fill in the WHO question right away. Only by working together as an industry and providing authorities with the necessary data can we as a collective fill in the blanks and achieve successful attribution."

In the end, whether Hermes, TrickBot or Ryuk came from Russia, North Korea or even possibly elsewhere, the source code appears readily available for a small, upfront investment with the possibilities for a larger payment. CrowdStrike estimates that Grim Spider may have already collected about $3.7 million in ransom since it started using ransomware. (See Ransomware, New Privacy Laws Are Top Security Concerns for 2019.)

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...