Attacks/Breaches

5/7/2018
05:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

SynAck Ransomware Gets Dangerous 'Doppleganging' Feature

New Process Doppelganging, obfuscation features makes the malware much harder to spot and stop.

The authors of the SynAck ransomware family appear to have found a way to make the malware considerably more dangerous for enterprises.

Kaspersky Lab this week reported discovering a new version of SynAck that uses a very sophisticated technique called Process Doppelganging to try and evade anti-malware tools. In an advisory this week, Kaspersky Lab researchers said they have observed the new variant being used in limited but highly targeted attacks against organizations in the United States, Germany, Kuwait and Iran.

"Enterprises should be aware that threat actors [have] switched to targeted attacks with ransomware," says Anton Ivanov, lead malware analyst, Kaspersky Lab. "Threat actors are beginning to use custom made ransomware with complicated techniques to bypass security solutions," Ivanov says. 

The authors of the new SynAck version have been using a combination of remote desktop protocol brute-force attacks and manual downloads to install the malware on vulnerable systems. The ransomware is designed to encrypt office documents, multimedia files, and database files.

Ransom amounts associated with the new variant have tended to average $3,000, which is a somewhat modest amount considering the sophistication behind the malware and the targeted nature of the campaign. That suggests that the threat actor behind the new SynAck is hoping to make money through volume infections rather than by attempting to extort large sums of money from a small number of victims.

The SynAck version is the first ransomware sample to use the Doppelganging Process, which basically involves a way to run malicious code in the guise of a harmless and legitimate Windows process. Security vendor enSilo demonstrated the technique at Black Hat Europe 2017 last December.

enSilo has described Process Doppelganging as a fileless evasion technique for bypassing real-time file scanning by most AV software and next generation AV tools for all versions of Windows since Windows Vista. Unlike malware that has to be written to disk or run completely from memory, with Process Doppelganging, threat actors can build malware that can run from what appears to be a completely legitimate-looking file.

"By manipulating how Windows handles file transactions, attackers can pass off malicious actions as harmless, legitimate processes, even if they are using known malicious code," Kaspersky Lab security researchers said in their advisory. The technique allows attackers to run malicious code without leaving any trace behind, making intrusions extremely hard to detect.

Doppelganging is not the only feature that sets the new SynAck variant apart from other ransomware tools.

Other notable features of the variant include the manner in which the malware obfuscates its executable code before compilation. Instead of using a custom packer to protect the malware code, the new SynAck version obfuscates the executable before compilation, thereby making it significantly harder for security researchers to reverse-engineer the code.

SynAck's latest version also can detect whether it's being launched from an automated sandbox: if so, it will promptly exit the sandbox. Before it actually begins to encrypt files, SynAck also checks the hashes of all processes that are running on the compromised machine, and tries to kill any processes that match a list of processes hard-coded into the malware.

Processes that SynAck is designed to kill include virtual machines, database applications, backup systems, and gaming applications in what appears to be a bid to make it easier to seize high-value files which may otherwise be tied to a running process, Kaspersky Lab said in its report.

Related Content:

 

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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.