Headlines to the contrary, the WikiLeaks hacktivist attacks against Visa, MasterCard, PayPal and others last week were relatively small and disorganized, a security expert said.
"Despite the press the attacks received, they were small potatoes," said Craig Labovitz, chief scientist at Chelmsford, Mass.-based Arbor Networks and an authority on the security of the Internet's infrastructure.
In a long post to Arbor's blog earlier in the week, Labovitz compared the scale and sophistication of the pro-WikiLeaks distributed denial-of-service (DDoS) attacks to 5,000 confirmed DDoS attacks during 2010.
Labovitz's conclusion: The WikiLeaks attacks were "unremarkable."
"I'd call this the cyber equivalent of a French trucker's strike," said Labovitz in an interview Thursday. "It certainly wasn't a war, as some headlines have claimed. It was a form of protest, but one with collateral damage."
The DDoS attacks were aimed at sites belonging to Amazon.com, MasterCard , PayPal and the Swiss payment transaction firm PostFinance, apparently in retaliation after each terminated WikiLeaks accounts or pulled the plug on services. Similar attacks targeted sites of U.S. Sen. Joseph Lieberman (I-Conn.) and Sarah Palin, the former governor of Alaska. Both had blasted WikiLeaks for releasing a trove of confidential U.S. State Department cables late last month.
But when Labovitz compared those attacks with statistics compiled by Arbor -- the company supplies anti-DDoS technologies to about 75% of the world's Internet service providers -- he found the WikiLeaks campaigns wanting.
According to Labovitz, neither the round of initial attacks that targeted WikiLeaks itself or the later retaliatory strikes were massive flooding DDoS or ultra-sophisticated application level attacks.
"The type of [application level] queries from LOIC were unsophisticated," said Labovitz, referring to a free tool, Low Orbit Ion Cannon , that many of the attack participants used. "A sophisticated attack uses the right order of queries, the right set of API calls to bog down the system." The hacktivist attacks showed no traces of either.
Nor were those attacks massive.
Labovitz estimated that the pro-WikiLeaks attacks generated at their peak about 5Gbit/sec. of traffic aimed at the targets, well under the 50Gbit/sec. Arbor tracked in several other flooding DDoS attacks this year, and just a fraction of the nearly 70Gbit/sec. seen in the largest attack thus far in 2010.
And although more than 100,000 copies of LOIC were downloaded last week, Labovitz said that Arbor's data showed that the peak number of simultaneous WikiLeaks retaliatory attackers was only in the hundreds, not the thousands.
"The number of source IPs observed in the WikiLeaks retaliation attacks fell into the mid or higher end of the 5,000 validated DDoS attacks last year," he said on the blog post.
To Labovitz, that suggested that while hacktivists tried to recruit large botnets, those collections of compromised computers were not actually used.
But while the WikiLeaks attacks were easily blocked by most targets, that doesn't mean DDoS attacks aren't a serious threat to the Internet.
"The majority of attacks we see can be dealt with," Labovitz said, "but there are professionals with financial motives who are putting a lot of time and money into very sophisticated DDoS attacks." Labovitz hesitated to assign specific motives for such high-end attacks, although some, he said, were clearly extortion attempts against ISPs and companies.
"While the WikiLeaks and retaliatory attacks may not represent the start of 'cyberwar,' ... the trend towards militarization of the Internet and DDoS used as means of protest, censorship, and political attack is cause for concern," he wrote on Arbor's blog. "DDoS fueled by the growth of professional adversaries, massive botnets and increasingly sophisticated attack tools poses a real danger to the network and our increasing dependence on the Internet."
Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news for Computerworld. Follow Gregg on Twitter at @gkeizer or subscribe to Gregg's RSS feed . His e-mail address is email@example.com .
Read more about security in Computerworld's Security Topic Center.