Attacks/Breaches
4/12/2012
02:41 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%
Repost This

Controversy Erupts Over Microsoft's Recent Takedown Of A Zeus Botnet

Dutch researchers accuse Microsoft of mishandling the recent Zeus botnet takedown and hurting other investigations -- but others defend Microsoft's operation as thorough

Microsoft's unprecedented aggressive legal strategy in botnet takedowns came under fire from researchers in the Netherlands, charging that the software giant's most recent botnet dismantlement operation has ultimately damaged international law enforcement and private research investigations.

Michael Sandee, principal security expert at Netherlands-based Fox-IT, wrote in a blog post today that rather than truly injuring the Zeus botnet operations last month, Microsoft instead has hampered investigations into these operations by its actions last month of removing and confiscating two of the command-and-control (C&C) servers under a federal court order. With U.S. marshals escorting them, a team from Microsoft, FS-ISAC, which represents 4,400 financial institutions, and NACHA on March 23 physically removed C&C servers used in the operation that were running out of two hosting services centers -- one in Scranton, Pa., and the other in Lombard, Ill. -- which resulted in the takedown of two IP addresses of the C&C infrastructure.

Microsoft acknowledged at the time that the operation would not stop Zeus-based operations, and that the goal was not to permanently kill all of the Zeus botnets targeted in the operation, but instead to disrupt this segment of the operation.

But Fox-IT's Sandee says Microsoft's actions did harm to the good guys. "Microsoft has endangered the success of countless ongoing investigations in both the private as the public sector all over the world from east to west," Sandee said in his post today. "Obviously as most of these folks are located in Russia and Eastern Europe, the cooperation between parties in those regions and in western countries on both public and private sector side has been hurt more than you can expect, and also years of trust building has potentially been lost ... In our discussions with Law Enforcement Officers, private investigators and members of NGOs researching these threats from across the globe we have found nothing but disappointment and disbelief regarding the irresponsible actions executed by Microsoft. Various other researchers have outed their disappointment."

Richard Boscovich, senior attorney for Microsoft's Digital Crimes Unit, said in a statement that Fox-IT's post "is based at least in part on some factual misunderstandings about the operation which we are more than happy to discuss with Fox IT."

Boscovich says he can't comment on details of the case because it's a legal matter, but noted that the details in the court filings are not all of the evidence and intelligence gathered in the operation. "To be clear, information in the legal filings for this case came from Microsoft's independent research as well as information provided by third party partners and researchers with their explicit permission and intent for inclusion, sourced from their own research or what they hold from sources widely exchanged within the security community," he said. "There are times when, for operational security reasons, we cannot provide advance information to all researchers out there monitoring a particular threat and there are, by law, firm restrictions on investigative collaboration between private companies and law enforcement. Despite these limitations, Microsoft's commitment to trustworthy partnership with the research and enforcement community has never wavered."

Microsoft's legal team was conspicuously missing from the most recent takedown of the second-generation Kelihos botnet, a.k.a. Hlux.B or Kelihos.B, which was spearheaded by Kaspersky Lab, CrowdStrike, Dell SecureWorks, and The Honeynet Project. They poisoned the peer-to-peer network-based botnet with their own code, which initially diverted some 110,000 infected machines to their sinkhole server and out of the hands of the botnet operators.

Kelihos/Hlux (a.k.a. Hlux/Kelihos), which was initially taken down in the fall by Microsoft, Kaspersky, and researchers from several other organizations, had been spotted by researchers re-emerging over the past few months with a new version of its malware.

[The shutdown of Waledac 2.0 by Microsoft and Kaspersky aims to send a message, but also raises questions, legal and otherwise. See Microsoft: No Resurrection For Dead Botnets. ]

Fox-IT is one of the first security firms to voice growing concerns about the ramifications of botnet takedowns in general. Previously, other security experts have quietly or carefully voiced their worries about the legal and ethical issues surrounding these operations.

The Honeynet Project has led the industry in helping define proper botnet takedown procedures. Botnet takedowns are complicated and care must be taken not to overstep the legal or other boundaries, according to Honeynet officials.

Christian Seifert, chief communications officer for the Honeynet Project, and Dave Dittrich, chief legal and ethics officer for the Honeynet Project, say that Microsoft was clear up front with the Zeus operation. "Microsoft clearly defined beforehand intention, justification, harm/benefit of their operation and, as such, went beyond what others may do," they said in a statement.

Sandee's points about sources and sharing information, however, were valid, they said. "One should attribute sources, share data and intent if possible, minimize harm to other fellow researchers, etc."

The Honeynet Project recently issued a proposed code of conduct for these operations to ensure that the benefits outweigh the risks. "Again, our hope is that the code of conduct guides researchers in making the risk/benefit assessment in a systematic way and construct their operation in a way that maximizes benefits and minimizes harm. It's not a black/white world though, so there is not going to be a situation where we only have benefits and no harm/risks," they said.

Next Page: A 'Code of Conduct' for botnet takedowns 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
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-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

CVE-2012-1317
Published: 2014-04-23
The multicast implementation in Cisco IOS before 15.1(1)SY allows remote attackers to cause a denial of service (Route Processor crash) by sending packets at a high rate, aka Bug ID CSCts37717.

CVE-2012-1366
Published: 2014-04-23
Cisco IOS before 15.1(1)SY on ASR 1000 devices, when Multicast Listener Discovery (MLD) tracking is enabled for IPv6, allows remote attackers to cause a denial of service (device reload) via crafted MLD packets, aka Bug ID CSCtz28544.

CVE-2012-3062
Published: 2014-04-23
Cisco IOS before 15.1(1)SY, when Multicast Listener Discovery (MLD) snooping is enabled, allows remote attackers to cause a denial of service (CPU consumption or device crash) via MLD packets on a network that contains many IPv6 hosts, aka Bug ID CSCtr88193.

CVE-2012-3918
Published: 2014-04-23
Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

Best of the Web