'Virut' botnet dealt blow as registrar sinkholes domains

Had been resurrecting Kelihos bot, said Symantec

Poland's national NASK domain registrar has taken control of 23 domains it said were being used to support the Virus botnet has been attempting to resurrect the tenacious Waledec/Kelihos bot severely damaged by Microsoft in 2011.

Virut itself is relatively modest on the botnet scale at any one moment in time, with perhaps 300,000 clients in its grip, but it has proved incredibly resilient, having survived attempts to shut it down since appearing in 2006.

It is also virulent, NASK said, having infected 890,000 IP addresses during 2012 in Poland alone, which means it is able to keep finding new machines to infect even as previously infected ones are detected.

In addition to the sinkholing of the domains, NASK said it had disrupted Virut's command control infrastructure, which will put the bot on the slide for the timebeing at least.

As to what Virut has been used for, it would be easier to name the scams and malware it hasn't been involved with. NASK mentions spam, DDoS, and malware such as Zeus (a rapacious bank Trojan) and the Palevo worm, not to mention pay-per-install malware campaigns. But it is its possible involvement in attempting to revive the defunct Waledec (aka Kelihos) botnet that is the most intriguing.

According to a report from Symantec last week, Waledac.D had recently been on an upswing as a spam platform, with Virut suspected as the distribution mechanism. The best way to heal a broken botent? Using another botnet apparently.

This will dismay bot-hunters that had thought this particular nasty might be gone for good after a notable operation called 'b49' in which Microsoft shuttered the whole C&C and its associated domain infrastructure in a matter of weeks during 2011.

Since that time, Kelihos has tried to rise again but has struggled to make much impression, until now. Symantec said the number of infected machines was around the 80,000 mark, which suggests the bot was gaining traction.

Redmond's lawyers later accused a named Russian as being behind Kelihos/Waledec, a charge denied by the individual concerned. Unusually, the company later backed down on the accusation.

NASK's actions are a welcome if unexpected event, apparently carried out with the help of Spamhaus and VirusTotal.

Tags: Personal Tech, symantec, security, Microsoft

Aussie drug prescriptions sit pretty for health fraud

READ THIS ARTICLE
DO NOT SHOW THIS BOX AGAIN [ x ]
Comments are now closed.
CSO Corporate Partners
  • Webroot
  • Trend Micro
  • NetIQ
rhs_login_lockGet exclusive access to CSO, invitation only events, reports & analysis.
CSO Directory

Endpoint Management Solutions

Endpoint Security Management

Latest Jobs
Security Awareness Tip

Incident handling is a vast topic, but here are a few tips for you to consider in your incident response. I hope you never have to use them, but the odds are at some point you will and I hope being ready saves you pain (or your job!).


  1. Have an incident response plan.

  2. Pre-define your incident response team 

  3. Define your approach: watch and learn or contain and recover.

  4. Pre-distribute call cards.

  5. Forensic and incident response data capture.

  6. Get your users on-side.

  7. Know how to report crimes and engage law enforcement. 

  8. Practice makes perfect.

For the full breakdown on this article

Security ABC Guides

Warning: Tips for secure mobile holiday shopping

I’m dating myself, but I remember when holiday shopping involved pouring through ads in the Sunday paper, placing actual phone calls from tethered land lines to research product stock and availability, and actually driving places to pick things up. Now, holiday shoppers can do all of that from a smartphone or tablet in a few seconds, but there are some security pitfalls to be aware of.