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

2/28/2017
05:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Massive Necurs Spam Botnet Now Equipped to Launch DDoS Attacks

With more than one million active bots at any time, a Necurs-enabled DDoS attack could dwarf such an attack by the Mirai botnet.

In an ominous development, the world’s largest spam botnet has acquired capabilities that could allow it to be used in massive distributed denial-of-service attacks.

Security researchers at BitSight’s Anubis Labs recently observed the Necurs botnet loading a component in infected systems that allow the systems to perform DDoS attacks.

The addition of the new component appears to have started at least six months ago, which is when BitSight researchers first observed some unusual communications on a Necurs-infected system.

In addition to communicating via port 80, the Necurs-infected system was also using a different port  as well as what appeared to be a different protocol, to communicate with a set of command and control addresses.

A subsequent analysis showed the communications from the infected system to be requests to download two separate modules. One of them was for the usual spam distribution purposes. And the other was for a proxy module that would cause the bot to make HTTP or UDP requests to a target system "in an endless loop," BitSight said in a recent alert.

The bot is modular in design; the proxy and DDOS features are part of a module first was deployed in September, says Tiago Pereira, threat intelligence researcher at Bitsight's Anubis Labs. "The SOCKS/DDOS module is being loaded in all the bots in the botnet," he says. At the same time, the spam modules are also still being loaded on all infected system, he says.

Pereira says BitSight's sinkholes measured an average of over 1 million active Necurs infected system every single day. "Simply taking into account its size—more than double the size of Mirai—we would expect it to produce a very powerful DDoS attack," he says.

Security researchers estimate the overall size of the Necurs botnet to be upwards of 5 million infected systems, though only about 1 million are active at any give time. In addition to being used for spam distribution, the botnet has also been used to deliver the notorious Locky ransomware and the Dridex banking Trojan.

The botnet went offline somewhat inexplicably for a few weeks last year, resulting in an almost immediate drop-off in Locky and Dridex distributions. But it came back online equally inexplicably and with renewed vigor in June, and since then had been used to distribute spam and malware.

With the addition of the new DDoS module, Necurs appears set to become even more versatile than it is already.

Ben Herzberg, security group research manager at Imperva, says it's interesting that Necurs has now added a feature for DDoS attacks. But threat actors are likely to increasingly favor using IoT botnets such as Mirai because they are easier to infect and use than desktop botnets like Necurs, he said.

"Therefore, it seems likely that this is either a test module, or something to be used in a 'doomsday scenario' – for example when the botnet operators need it for a very good reason - not just as a normal DDoS-for-hire campaign," he said in a statement.

Word of the Necurs botnet update comes amid reports of changes to Neutrino, another well-known malware sample that has been used to assemble a large botnet. The authors of the Neutrino bot have developed a new protective loader that makes it harder for malware tools to detect the bot, Malwarebytes Labs said in an alert this week.

The new loader is designed to check whether it is being deployed in a controlled environment like a sandbox or a virtual machine and to delete itself automatically if that is indeed the case, Malwarebytes researchers Hasherezade and Jerome Segura said.

The tweak is not major. But the new protection layer is "very scrupulous in its task of fingerprinting the environment and not allowing the bot to be discovered," they said.

Related stories:

 

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
Oldest First  |  Newest First  |  Threaded View
Jet Hedon
100%
0%
Jet Hedon,
User Rank: Apprentice
3/1/2017 | 7:09:21 AM
Great info
Great info you shared here. Studying DDOS right now, this article helped me out to learn more.
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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-16123
PUBLISHED: 2020-12-04
An Ubuntu-specific patch in PulseAudio created a race condition where the snap policy module would fail to identify a client connection from a snap as coming from a snap if SCM_CREDENTIALS were missing, allowing the snap to connect to PulseAudio without proper confinement. This could be exploited by...
CVE-2018-21270
PUBLISHED: 2020-12-03
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
CVE-2020-26248
PUBLISHED: 2020-12-03
In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.
CVE-2020-29529
PUBLISHED: 2020-12-03
HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.
CVE-2020-29534
PUBLISHED: 2020-12-03
An issue was discovered in the Linux kernel before 5.9.3. io_uring takes a non-refcounted reference to the files_struct of the process that submitted a request, causing execve() to incorrectly optimize unshare_fd(), aka CID-0f2122045b94.