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.

Vulnerabilities / Threats

5/1/2015
02:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Dyre Trojan Adds New Sandbox-Evasion Feature

New tactic makes it that much harder to detect, says Seculert.

The Dyre malware tool, which has emerged as one of the most significant banking Trojans since the takedown of the Gameover Zeus botnet last June, has added an effective new trick for avoiding detection by anti-malware tools.

Security researchers at Seculert recently discovered a new version of Dyre that is able to evade sandbox detection tools by checking how many processor cores the machine has.

If it discovers the machine has just one core it immediately terminates on the system it has infected before it can be spotted, Seculert’s CTO and co-founder Aviv Raff, said in a blog Thursday.

 A security sandbox is basically a secure virtualized environment for executing and running unfamiliar or untrusted code to see if it contains any malware. Several security tools are currently available that offer sandboxing as a technique for detecting and blocking malicious code.

Typically, sandboxes are configured with just one processor and one core, to save system resources, Raff said in his blog. So checking the number of cores present on a system, like the latest version of Dyre does, is a simple and effective way for the malware to know if it is running in a sandbox environment or not.

Typically, modern malware tools employ multiple techniques to try and avoid being caught in the sandbox Raff said pointing to a research paper that enumerates some of the methods.

For example, a malware tool might search for a specific process name on the system it has infected to see if it can detect the presence of a sandbox or virtual machine. The goal is to try and find process names like vmsrvc.exe, or vmtoolsd.exe and similar that suggests to the malware that it is running in a virtual environment, the paper noted.

Similarly, some malware tools might look for specific registry entries or publicly known module names used by security sandboxes to detect the presence of one. Others look to see if they can find the backdoor that many virtual machines use to communicate with the guest operating system, the paper noted.

The latest version of Dyre that Seculert observed however relies just on the processor core counting technique to make a determination of whether it is running in a sandbox, Raff said. The reason could be that the malware authors have determined this one particular technique is good enough, he noted.

When Seculert tested several commercial and non-commercial sandbox technologies to see if they could detect the new version of Dyre, not one of them did, Raff said.

It is possible the [the malware authors] conducted their own research and determined that this one particular technique or check was the key to remaining undetected by sandboxing solutions,” he said. He added that Seculert had provided details of its discovery to relevant security vendors.

The new sandbox evasion technique is part of a string of modifications and tweaks that have made Dyre an increasingly potent threat since it first emerged last year. Earlier this year, IBM researchers spotted a new malware campaign where attackers used a Dyre variant dubbed Dyre Wolf to steal more than $1 million from businesses.

In a recent report Dell SecureWorks highlighted Dyre as one of the major new banking Trojans to have emerged in the post-Zeus era.

 

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
Newest First  |  Oldest First  |  Threaded View
RetiredUser
0%
100%
RetiredUser,
User Rank: Ninja
5/3/2015 | 5:13:28 PM
Variability in Programming: Overhead or Security?
The ability for malicious code to examine the host and perform data collection and analysis based upon known process naming conventions is something that goes back quite some time.  Just as with writing complex debug code during development to aid software bug tracking during testing is a topic of divide amongst some programmers and management (there is overhead involved, both time to write the debug code and in some cases run it), so too is the question at the software application architecture level of whether to program variability into software when it comes to process, file, and directory structure naming.  

In fact, beyond the idea of writing a piece of security software that can dynamically change the names of key elements of the program that malware might search for to determine if a system it is attacking is protected by such security applications, there are other features that could be programmed such as encryption and masking/cloaking (taking on attributes of other non-security programs not installed on the system, but that pose no threat to the malware).

To write antivirus software with such capabilities is the future of InfoSec, I believe, but is the overhead it will take to get such applications there worth it?  I think so.  Think about it:  Your antivirus software to any other observer is an instance of Adobe Acrobat, and your sandbox is programmed such that it mirrors a normal OS with no references to VM or similar processes.  The ultimate cloaking device.   

Virus and malware writers are already thinking ahead of InfoSec professionals by engaging creative thinking like this.  Let's get ahead of them and build the perfect mouse trap.
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31664
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-33185
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
CVE-2021-33186
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-31272
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.
CVE-2021-31660
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 85da504d2dc30188b89f44c3276fc5a25b31251f contains a buffer overflow which could allow attackers to obtain sensitive information.