We can beat the botnets
Posted on 8 Mar 2010 at 14:50
Davey Winder celebrates some GBH (grievous botnet harm)
In the space of 24 hours, its determined team of security researchers managed to co-ordinate an attack against the command and control centres that botnets rely upon to stay alive, and as a result forced a quarter of a million bots offline and effectively disabled the Mega-D/Ozdok botnet, albeit temporarily.
The point is that its approach has now been shown to work, and if the security industry, the ISP industry and law-enforcement agencies had the will to follow it through, there’s absolutely no reason why a sustained counter-attack couldn’t all but wipe out the botnet threat within a matter of months.
FireEye’s team took a highly organised approach to the problem, studying the command and control architecture over a period of many weeks. Most importantly, it made a point of understanding the fallback mechanisms in place to keep the botnet alive if attacked. Only when the researchers were absolutely sure of the evidence they’d gathered regarding the domains being used for command-and-control and fallback – and only once they fully understood the structure of the beast they were dealing with – did they strike.
Speed was the real key to success, because to beat down a botnet and prevent its fallback strategy from kicking in, you quite logically need to disable all its command and control servers before they have a chance to start setting up alternative routes to their zombies.
First, all the identified ISPs were notified about which of their hosts were being used by the botnet, whether directly by the gang or on a compromised basis, with an urgent request to suspend them. Apparently, the evidence presented was compelling enough for only four of the hosts to remain up and running.
At the same time, other researchers contacted Internet Registrars with evidence pointing to those domains that had been identified as being either in the primary command-and-control or the secondary fallback chain. A number of these were suspended too, and FireEye also succeeded in getting many zombie PCs re-routed to a sinkhole server where data that identified the owners could be collected – those owners were in turn given help to clean their machines of the malware that allowed them to be compromised in the first place.
Within just 24 hours some 264,784 machines with unique IP addresses connected to that decontamination server!
The end result was that for a week or two Mega-D was crippled, the number of reported zombies dropping from around 1,500 a day to 50 or less. Of course, the success was short-lived, as the gang behind this profitable enterprise took advantage of the fact that it was just a one-off attack, and has since been investing time and money in rebuilding its botnet.
As I write, I’m led to believe that activity is back up to about 75% of what it was before FireEye rained those 24 hours of good-guy hell on them.
Download a year of Davey Winder's Online Security columns by heading to our Free Downloads site
From around the web
Updates updates updates...
One customer's previous service provider had never turned on automatic updates (although they had installed WSUS server) and never let the AV software scan the machines (256MB RAM and 1.2Ghz processors on most, so a scan takes a couple of days!).
I was left with a network full of Conficker infected machines! If they had kept their machines up to date, I wouldn't have had that problem!
By big_D on 9 Mar 2010 ![]()
Davey Winder
Davey is a contributing editor to PC Pro, having covered the internet as a topic since the magazine started in 1994. Since that time he's won numerous awards for his journalism, but remains a small-business consultant specialising in privacy, security and usability issues.
advertisement
- Why you have to be left in the dark on OS patches
- Is Microsoft mismanaging Windows on ARM?
- Dealing with spam surrogates
- Why 3G broadband can be better and cheaper than ADSL
- Is Twitter bad for business?
- Publishing your email address isn't a security disaster
- Why you'll need a fax machine to develop iOS apps
- Learning to adapt to the mobile web
- Why you shouldn't use WPS on your Wi-Fi network
- Disabled users suffer when software breaks the rules
- Laptop bag reviews: nine tested
- Sony VAIO T Series Ultrabook review: first look
- Revealed: the military standards and robots HP uses to test its laptops
- Windows 8: multi-monitors and double standards?
- Why is TalkTalk's year-old porn filter suddenly big news?
- Why are laptop screens so far behind mobiles?
- HP EliteBook Folio review: first look
- The shoebox-sized all-in-one printer
- Forget the Ultrabook: here comes the HP Sleekbook
- HP Spectre XT review: first look
- Autonomy's Lynch joins 27,000 on way out of HP
- ICO: no fines for breaking cookie rules
- HP set to slash up to 30,000 jobs
- Government sites to miss cookie deadline
- Microsoft tweaks multi-monitor support in Windows 8
- Apple patches Leopard, despite ending support last year
- Defra opens rural broadband funding applications
- BT's broadband sales surpass calls revenue
- Apple patches multiple security issues
- FBI warns travellers to beware attacks via hotel Wi-Fi
advertisement
