In a blog posted Tuesday, Richard Boscovich, senior attorney for Microsoft's Digital Crimes Unit, said Kelihos was brought down in an operation, code-named "Operation b79," that used similar legal and technical measures as the company's previous botnet takedowns.
The takedown will be the first time Microsoft has named a defendant in one of its civil cases involving a botnet, Boscovich says.
"The Kelihos takedown is intended to send a strong message to those behind botnets that it’s unwise for them to simply try to update their code and rebuild a botnet once we’ve dismantled it," the blog says. "When Microsoft takes a botnet down, we intend to keep it down – and we will continue to take action to protect our customers and platforms and hold botherders accountable for their actions."
In the complaint, Microsoft alleges that Dominique Alexander Piatti, dotFREE Group SRO, and 22 unnamed actors operated and controlled the Kelihos botnet.
"Naming defendants in this case marks a big step forward for Microsoft in making good on its commitment to aggressively protect its platform and customers against abuse from whomever and wherever it may originate," the blog says. "Naming these defendants also helps expose how cybercrime is enabled when domain providers and other cyber infrastructure providers fail to know their customers.
"Through this case, we hope to demonstrate that if domain owners don’t hold themselves accountable for knowing their customers, they will be held accountable for what is happening on their infrastructure," the blog states. "Our goal is for this case to spur an industry-wide discussion for more public and accountable subdomain registration practices to enable a safer, more secure Internet for all users."
Microsoft’s analysis of the Kelihos botnet showed large portions of Kelihos code were shared with Waledac, which suggested that Kelihos was either from the same parties or that the code was obtained, updated, and reused. "Once we learned of the apparent relationship to Waledac, we immediately began developing a plan to take out Kelihos using similar technical measures," the blog says.
Kelihos is much smaller than Rustock, comprising approximately 41,000 computers worldwide, Microsoft says. Still, the botnet was capable of sending 3.8 billion spam e-mails per day.
Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.
| To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
Choosing the Right Vulnerability Scanner for Your Organization
Vulnerability scanners can be used to help detect and fix systemic problems in an organization's security program and monitor the effectiveness of security controls. However, a vulnerability scanner can improve the organization?s security posture only when it is used as part of a vulnerability management program, in which products, processes and people are working together to find, identify, prioritize and mitigate threats. Here are some tips on choosing and implementing vulnerability scanners in your enterprise.
Using Google to Find Vulnerabilities In Your IT Environment
Attackers are increasingly using a simple method for finding flaws in websites and applications: they Google them. Using Google code search, hackers can identify crucial vulnerabilities in application code strings, providing the entry point they need to break through application security. Sound scary? It is, but there is good news: You can use these same methods to find flaws before the bad guys do. In this special report, we outline methods for using search engines such as Google and Bing to identify vulnerabilities in your applications, systems and services--and to fix them before they can be exploited.
Security Pro's Guide to Patch Management
It's no longer sufficient to patch just Windows, Office and IE. With the massive array of applications now residing on enterprise PCs, and the proliferation of mobile and cloud-based applications, your business is far too vulnerable to exploitation unless you have a solid strategy for patch prioritization, deployment and quality assurance. Follow these steps to put your plan in place.
Other reports from the Vulnerability Management Tech Center:
MORE NEWSFEED >>>