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

8/10/2015
03:00 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

DGA.Changer Gets Anti-Detection Upgrade

New 'imitation game' feature helps botnet-for-rent fool security tools that use sandboxing.

DGA.Changer has added a new trick to its arsenal:  a technique to fool security tools into thinking they've captured it while it's already slipped away, according to new research from Seculert.

DGA.Changer is a botnet-for-rent used for click fraud campaigns, information-stealing, and delivering remote access Trojans, and is sold for targeted purposes as well.

It uses an infinite domain generation algorithm (DGA), plus the command-and-control server can send issue commands to the bots to change the DGA seed (hence the name). This always made it difficult to detect, because as Seculert described when first detailing the malware in 2013, "the initial sample will reveal the domain name streams before the change — which no longer resolve to the C2 server."

Recently, the malware writers have taken those anti-detection capabilities even further.

“A new feature they added several months ago is if they detect they are in a virtualized environment like a sandbox, they generate a fake stream,” says Aviv Raff, CTO of Seculert.

DGA Changer will look for evidence of VMWare, Virtual Box and other virtualization products to check whether or not the malware is runing within a virtual machine. If so, it alters the DGA seed, communicates with the fake domains, and downloads an executable file -- but that executable does nothing more than exit after being executed.

In other words, all that’s in the sandbox is a decoy, Raff says.

As Raff wrote, "the goal here seems to be to fool sandbox solutions and/or researchers into believing the malware is fully functional and downloading additional components. ... The discovery of this new version of DGA.Changer highlights yet again the limitations of 'sandbox only' prevention approaches and the need to complement them with post-infection analytics based detection techniques." 

Kelly Jackson Higgins contributed to this story.

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Perry Cybereason
100%
0%
Perry Cybereason,
User Rank: Apprentice
8/11/2015 | 2:52:06 PM
The eternal flaw of one-shot detection methods

When you examine the attack in vitro, it is too easy for the attacker to fool you. The burden of making it work is on you and the attacker only has to choose which escape trick to use. This is especially highlighted when you use a one-shot decision model. If the malware fools you in that specific moment, it is safe to do as it will thereafter.

When you keep your eye open in the full, real environment, at all times, there is no fooling you. Detection is running in situ on the actual behavior patterns of the attacker and these are bound to reveal its true nature.

Cybereason detects the old and new variants of this malware, not by knowing them in particular, but by detecting its true nature in situ. Check out our DGA related blog posts for more details.

RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
8/11/2015 | 9:03:35 AM
Sandbox Conditional Coding
I'm curious as to what the criteria is for the DGA Changer to set up the fake stream as obviously not all virtual environments are sandboxes. Maybe they don't even risk it and just consider all virtual environments an area to which they do not want to be involved.
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
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-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...