Attacks/Breaches
3/29/2012
05:23 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%
Repost This

It's (Already) Baaack: Kelihos Botnet Rebounds With New Variant

Botnet hunters debate whether Kelihos/Hlux operators can reclaim rescued bots

Less than one day after botnet hunters announced they had crippled the Kelihos.B/Hlux.B botnet, a new version of the tenacious botnet is now back up and running today.

Researchers at Seculert were the first to point out the Kelihos/Hlux botnet was in action: Aviv Raff, co-founder and CTO at Seculert, late yesterday confirmed that his firm had seen the botnet spreading via a Facebook worm despite the announcement yesterday by Kaspersky, CrowdStrike, Dell SecureWorks, and The Honeynet Project that they had knocked the botnet offline. Raff says there's still communication under way via its command-and-control (C&C) servers.

"We still see infected Kelihos.B machines, even new ones, sending spam and communicating with the C&C server," Seculert's Raff says.

But researchers from Kaspersky Lab, CrowdStrike, Fortinet, and Unveillance contend that this is a new variant of Kelihos/Hlux, not the same botnet that was taken down over the past few days. That one, KelihosB/HluxB -- which was built for spamming, information-stealing, DDoSing, as well as for pilfering Bitcoins and electronic wallets -- was sunk when the team poisoned it with their own code in order to redirect some 110,000 bots to their sinkhole server and away from the operator's control. It was about three times as large as the first Hlux/Kelihos botnet, which was crippled last fall by a team led by Microsoft and that included Kaspersky.

Marco Preuss, head of global research and analysis in Germany for Kaspersky Lab, says the new botnet activity is coming from Hlux.C/Kelihos.C, and that the one that his firm and others took down remains offline. "We confirm that a new Hlux/Kelihos sample exists, but it has a different configuration, which means it's coming from a new Hlux botnet (Hlux C). The previous generation (Hlux B) is under control by the sinkhole server. It is not uncommon for new versions of botnets to appear that are operated by the same group," Preuss says.

CrowdStrike's Tillmann Werner says the Kelihos.B-infected machines in the sinkhole set up by CrowdStrike and the other research teams can no longer be used by the botnet operators, and has confirmed that the C&C infrastructure doesn't use the Kelihos.B protocol anymore. The researchers say they diverted some 110,000 infected machines to their sinkhole server.

The new Kelihos.C variant, which Werner says was released "shortly" after the sinkhole operation began, is "completely separate" and is spreading via social networks. It contains a tweaked message format for spreading commands to its peers, he says.

CrowdStrike isn't aware of any way for the new botnet to steal back its bots from the sinkhole, he says.

Bit Seculert maintains that this new botnet activity is still Kelihos.B: "Some might call this 'a new variant' or Kelihos.C. However, as the new infected machines are operated by the same group of criminals, which can also regain access to the sinkholed bots through the Facebook worm malware, we believe that it is better to still refer this botnet as Kelihos.B," according to a blog post by the company that says more than 70,000 Facebook users were infected with the worm.

Debates aside, Kelihos/Hlux's comeback was not unexpected by the botnet hunters. But it was certainly faster than most had predicted. Why the quick turnaround?

Kyle Yang, manager of AV engine development at Fortinet, says the botnet operators obviously were ready for a takedown this time around. According to Yang's findings, the botnet operators had in their possession two "job" servers from the first Kelihos/Hlux variant taken down by Microsoft. Job servers are controlled by C&C servers.

"Pretty much those guys were ready for a takedown. They were just waiting for it," Yang says. "The reason why [they did it] so quickly was they still had two [job] servers alive" from the first botnet, he says. Those were not servers crippled by this week's botnet takedown, however, he says.

Yang says he hasn't been able to figure out just how the malware authors regained control of those two servers from the first round. The attackers also since have put up three additional job servers in support of the C version of the botnet, he says.

Unveillance, meanwhile, was able to confirm that the new variant uses a different protocol. "We can also confirm that the live sample we've been observing is what they are calling .C ... The two older binaries use well-formed HTTP and .C does not," says Karim Hijazi, CEO at Unveillance.

"In reference to Seculert's claim that because the same botmasters may be operating this new version that it should be called .B instead of .C, we disagree. Due to the change in the communication protocol, it seems perfectly in keeping with standard AV naming convention to give this a new version name," he says. "AV naming convention does not take into account distinct botnets within a given malware type. For example, the Mariposa C2 samples are still named Palevo/Rimecud, not Mariposa."

Most everyone does agree, however, that the only way to really kill a botnet is to apprehend its operators.

Next Page: Legal implications of taking over a P2P botnet? Kelly Jackson Higgins is Senior Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise Magazine, ... View Full Bio

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Bprince
50%
50%
Bprince,
User Rank: Ninja
3/30/2012 | 11:14:48 PM
re: It's (Already) Baaack: Kelihos Botnet Rebounds With New Variant
It's a non-stop game of whack-a-mole. I think it should be expected at this point that botnet operators are going to look for ways to build a more resilient network in light of the success these take downs are having.
Brian Prince, InformationWeek/Dark Reading Comment Moderator
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-3946
Published: 2014-04-24
Cisco IOS before 15.3(2)S allows remote attackers to bypass interface ACL restrictions in opportunistic circumstances by sending IPv6 packets in an unspecified scenario in which expected packet drops do not occur for "a small percentage" of the packets, aka Bug ID CSCty73682.

CVE-2012-5723
Published: 2014-04-24
Cisco ASR 1000 devices with software before 3.8S, when BDI routing is enabled, allow remote attackers to cause a denial of service (device reload) via crafted (1) broadcast or (2) multicast ICMP packets with fragmentation, aka Bug ID CSCub55948.

CVE-2013-6738
Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in IBM SmartCloud Analytics Log Analysis 1.1 and 1.2 before 1.2.0.0-CSI-SCALA-IF0003 allows remote attackers to inject arbitrary web script or HTML via an invalid query parameter in a response from an OAuth authorization endpoint.

CVE-2014-0188
Published: 2014-04-24
The openshift-origin-broker in Red Hat OpenShift Enterprise 2.0.5, 1.2.7, and earlier does not properly handle authentication requests from the remote-user auth plugin, which allows remote attackers to bypass authentication and impersonate arbitrary users via the X-Remote-User header in a request to...

CVE-2014-2391
Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

Best of the Web