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.

Attacks/Breaches

11/17/2020
09:05 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Ransomware Operator Promotes Distributed Storage for Stolen Data

The criminals behind the DarkSide ransomware-as-a-service operation say the system will be harder to take down.

News last week about a ransomware-as-a-service (RaaS) operation called DarkSide setting up a distributed storage system in Iran for storing data stolen from victims of its attacks could mean big trouble for organizations.

If the model proves successful, other ransomware operators are likely to implement similar systems, making it even harder for defenders to prevent crooks from leaking sensitive corporate data stolen in ransomware attacks.

Related Content:

Rising Ransomware Breaches Underscore Cybersecurity Failures

The Changing Face of Threat Intelligence

New on The Edge: We Secured the Election. Now How Do We Secure Trust in Results?

"Such servers in Iran and [other] countries will be harder to discover, block, and cease due to a lack of cooperation from local authorities," says Victoria Kivilevich, threat intelligence analyst at Israel-based security firm KELA, which first discovered the scheme.

At the same time, storing stolen data on a distributed system will make it easier for cybercriminals to access the data compared with downloading files through Tor, which is how it's typically done now, she says. "All in all, such a step shows that ransomware developers increase their efforts to scale their operations and form a complex ecosystem designed to cause significant damage to victims."

Security researchers from KELA observed two recent announcements that DarkSide's operators posted on a blog. The first advertisement on Nov. 11 proclaimed plans by the DarkSide group to create a distributed storage system that customers (or so-called affiliates) of its ransomware services could use to store data stolen from victims. "We are already working on a sustainable storage system for your data," the advertisement noted. "All your data will be replicated between multiple servers, blocking one server won't delete data." The advertisement guaranteed affiliates that stolen data would be stored for a minimum of six months.

In this context, affiliates are criminal groups that use a RaaS offering such as DarkSide to target organizations, launch attacks, and extract money from victims. As developers of the service, operators like DarkSide get to keep a substantial cut of the ransom.

Kivilevich says that based on what DarkSide's developers have stated, the planned distributed storage system is intended to store data only belonging to DarkSide victims. "So far, there is no indication that they intend to provide other ransomware gangs with access to their system."

DarkSide's post suggested that the storage system was being set up in response to recent efforts by security vendors and law enforcement to take down sites that ransomware operators often set up to leak data belonging to victims that refuse to pay a demanded ransom. In recent months, many ransomware groups have taken to stealing critical data from victims before encrypting it, and then threatening to release the data publicly via sites set up explicitly for the purpose unless a ransom is paid.

DarkSide's Nov. 11 post claimed the group would specifically use distributed storage servers in Iran and "unrecognized republics" so the infrastructure could not be easily taken down. An "automatic system" would direct criminals interested in purchasing stolen data to specific servers from where it would be available for download.

Working on the Details
A subsequent note that DarkSide posted on Nov. 15, however, suggested that the group might not have entirely thought through its plans to store stolen data on servers in Iran. The US Department of Treasury's Office of Foreign Assets Control (OFAC) recently made very clear that US ransomware victims could end up in legal trouble if they paid any kind of ransom to criminal groups with a nexus to entities or countries (including Iran) that are on US sanctions lists.

In its second note, DarkSide clarified that no stolen data was currently being stored on any servers in Iran. It also clarified that data stolen from ransomware victims would not be stored in countries on the US government's sanctions list. "Therefore, you cannot worry, we are not on the sanctions lists and are not citizens of Iran," said the note, which KELA shared with Dark Reading.

Kivilevich says that this is the first time KELA has seen ransomware operator publicly announce that they are developing a distributed storage system for stolen files. Based on available information, it's unclear how large DarkSide's proposed distributed storage system will be. But the group has the financial muscle to land a big deal with a bulletproof hosting provider that might have access to Iranian infrastructure, she says.

News of DarkSide's proposed storage system comes amid an overall increase in RaaS operations. In a blog post this week, threat intelligence firm Intel 471 said it has been tracking at least 25 significant RaaS crews over the past year alone. According to the company, there are many other private gangs that operate in tight-knit criminal circles using private communication channels, such as Telegram, that are hard to track.

The biggest and the most dangerous among these groups are DopplePaymer, Netwalker, Egregor/Maze, and Sodinokibi (aka REvil), the threat intelligence firm said.

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 11/19/2020
New Proposed DNS Security Features Released
Kelly Jackson Higgins, Executive Editor at Dark Reading,  11/19/2020
How to Identify Cobalt Strike on Your Network
Zohar Buber, Security Analyst,  11/18/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25159
PUBLISHED: 2020-11-24
499ES EtherNet/IP (ENIP) Adaptor Source Code is vulnerable to a stack-based buffer overflow, which may allow an attacker to send a specially crafted packet that may result in a denial-of-service condition or code execution.
CVE-2020-25654
PUBLISHED: 2020-11-24
An ACL bypass flaw was found in pacemaker before 1.1.24-rc1 and 2.0.5-rc2. An attacker having a local account on the cluster and in the haclient group could use IPC communication with various daemons directly to perform certain tasks that they would be prevented by ACLs from doing if they went throu...
CVE-2020-28329
PUBLISHED: 2020-11-24
Barco wePresent WiPG-1600W firmware includes a hardcoded API account and password that is discoverable by inspecting the firmware image. A malicious actor could use this password to access authenticated, administrative functions in the API. Affected Version(s): 2.5.1.8, 2.5.0.25, 2.5.0.24, 2.4.1.19.
CVE-2020-29053
PUBLISHED: 2020-11-24
HRSALE 2.0.0 allows XSS via the admin/project/projects_calendar set_date parameter.
CVE-2020-25640
PUBLISHED: 2020-11-24
A flaw was discovered in WildFly before 21.0.0.Final where, Resource adapter logs plain text JMS password at warning level on connection error, inserting sensitive information in the log file.