Welcome Guest. | Log In| Register | Membership Benefits
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

Researchers Infiltrate and 'Pollute' Storm Botnet

European botnet experts devise a method that disrupts stubborn peer-to-peer botnets like Storm

Apr 23, 2008 | 07:45 AM

By Kelly Jackson Higgins
DarkReading

Sophisticated peer-to-peer (P2P) botnets like Storm that have no centralized command and control architecture have frustrated researchers because they're tough to dismantle. But a group of European researchers has come up with a way to disrupt these stealthy botnets -- by “polluting” them.

The researchers, from the University of Mannheim and the Institut Eurecom, recently infiltrated Storm to test out a method they came up with of analyzing and disrupting P2P botnets. Their technique is a spinoff of traditional botnet tracking, but with a twist: it not only entails capturing bot binaries and infiltrating the P2P network, but it also exploits weaknesses in the botnet’s P2P protocol to inject “polluted” content into the botnet to disrupt communication among the bots, as well as to study them more closely. The researchers tested their pollution method out on Storm -- and it worked. They presented their research this month at Usenix.

“Our measurements show that our strategy can be used as a way to disable the communication within the Storm botnet to a large extent,” the researchers wrote in their paper. “As a side effect, we are able to estimate the size of the Storm botnet, in general a hard task... Our measurements are much more precise than previous measurements.”

Their Storm stats: the researchers crawled Storm every 30 minutes from December of last year through February of this year, and saw between 5,000 and 40,000 machines online at a time. Not surprisingly, the Christmas and New Year’s holidays accounted for a big jump in numbers. And the U.S. has the most Storm bots, with 23 percent, according to the researchers, who said they spotted Storm bots in 200 countries.

The researchers also tested another P2P mitigation method called an “eclipse attack,” which basically aims to separate a segment of the P2P network from the main body by luring it to their phony bots, but it didn’t work.

The pollution attack, meanwhile, “overwrites” the P2P botnet’s key, an identifier that’s used to get command information to the bots. Storm generates keys to find other bots, the researchers noted. “Since the Storm bots continue to publish their content as well, this is a race between the group performing mitigation attempts and the infected machines,” the researchers wrote. “Our experiments show that by polluting all those hashes that we identified to be storm hashes, we can disrupt the communication.”

Jose Nazario, a security researcher with Arbor Networks who has studied Storm, says the pollution technique isn't a new concept, but the researchers may be among the first "to expose such a methodology publicly," he says. "This has been a taboo subject of exploration, as people do not want to mess with other peoples' PCs by injecting commands," he says.

Bottom line: the so-called “publish/subscribe” type of communication used by Storm and other P2P botnets is vulnerable to this type of exploitation.

Not surprisingly, getting to the operators behind Storm wasn’t so simple. Storm’s two-tier architecture -- tier one being the P2P networks Overnet and Storm itself, and tier two, the better-hidden computers that send the actual commands -- made that difficult. “In future work, we plan to analyze in detail the second-tier computers and try to find ways to identify the operators of the Storm Worm,” the researchers said in their paper.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.


Subscribe to RSS










Bugs
ENTERPRISE VULNERABILITIES
Vulnerability:suse linux
Published:2010-01-22
Severity:High
Description:SUSE Linux Enterprise 10 SP3 (SLE10-SP3) configures postfix to listen on all network interfaces, which might allow remote attackers to bypass intended access restrictions.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:The URL validation functionality in Microsoft Internet Explorer 7 and 8 does not properly process input parameters, which allows remote attackers to execute arbitrary local programs via a crafted URL, aka "URL Validation Vulnerability."
Vulnerability:bind
Published:2010-01-22
Severity:Medium
Description:ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P5, 9.5 before 9.5.2-P2, 9.6 before 9.6.1-P3, and 9.7.0 beta does not properly validate DNSSEC (1) NSEC and (2) NSEC3 records, which allows remote attackers to add the Authenticated Data (AD) flag to a forged NXDOMAIN response for an existing domain.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:Microsoft Internet Explorer 6, 6 SP1, 7, and 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-2530 and CVE-2009-2531.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:Microsoft Internet Explorer 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-3671, CVE-2009-3674, and CVE-2010-0246.


Briefing Centers
POWERFUL INFORMATION
AT YOUR FINGERTIPS
(SPONSORED LINKS)