Slashdot Log In
Storm Worm More Powerful Than Top Supercomputers
Posted by
ScuttleMonkey
on Fri Sep 07, 2007 07:19 AM
from the spamalot dept.
from the spamalot dept.
Stony Stevenson writes to mention that some security researchers are claiming that the Storm Worm has grown so massive that it could rival the world's top supercomputers in terms of raw power. "Sergeant said researchers at MessageLabs see about 2 million different computers in the botnet sending out spam on any given day, and he adds that he estimates the botnet generally is operating at about 10 percent of capacity. 'We've seen spikes where the owner is experimenting with something and those spikes are usually five to 10 times what we normally see,' he said, noting he suspects the botnet could be as large as 50 million computers. 'That means they can turn on the taps whenever they want to.'"
Related Stories
[+]
Storm Worm Rising 218 comments
The Storm worm has been an increasing problem in the last few months, but a change in tactics may mean something big is going to happen. The article discusses a bit of back story about the worm, including the somewhat frightening numbers about the millions of spam emails carrying the worm payload. They estimate between a quarter and a million infected systems usable for spam or DDOS attacks.
[+]
Storm Botnet Is Behind Two New Attacks 226 comments
We've gotten a number of submissions about the new tricks the massive Storm botnet has been up to. Estimates of the size of this botnet range from 250K-1M to 5M-10M compromised machines. Reader cottagetrees notes a writeup at Exploit Prevention Labs on a new social engineering attack involving YouTube. The emails, which may be targeted at people who use private domain registrations, warn the recipient that their "face is all over 'net" on a YouTube video. The link is to a Storm-infected bot that attacks using the Q4Rollup exploit (a package of about a dozen encrypted exploits). And reader thefickler writes that the recent wave of "confirmation spam" is also due to Storm, as was the earlier, months-long "e-card from a friend" series of attack emails.
[+]
Storm Worm Botnet Partitions May Be Up For Sale 192 comments
Bowling for cents writes "There is evidence that the massive Storm Worm botnet is being broken up into smaller networks, and a ZDNet post thinks that's a surefire sign that the CPU power is up for sale to spammers and denial-of-service attackers. The latest variants of Storm are now using a 40-byte key to encrypt their Overnet/eDonkey peer-to-peer traffic, meaning that each node will only be able to communicate with nodes that use the same key. This effectively allows the Storm author to segment the Storm botnet into smaller networks. This could be a precursor to selling Storm to other spammers, as an end-to-end spam botnet system, complete with fast-flux DNS and hosting capabilities."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Massive storm worm? (Score:5, Funny)
Re: (Score:3, Funny)
Re:Massive storm worm? (Score:4, Funny)
Some guys have all the luck. I'd be happy just planning to be laid.
Parent
Re:Massive storm worm? (Score:4, Funny)
Parent
Usul, we have wormsign... (Score:3, Funny)
Fine the technically illiterate (Score:4, Insightful)
Re:Fine the technically illiterate (Score:4, Insightful)
That sort of self-righteous bullshit is exactly how criminals rationalize their own misdeeds — such as botnets.
Parent
Re:Fine the technically illiterate (Score:4, Insightful)
If you want to start regulating who and what can or cannot connect to the Internet (you can't, it's not politically feasible to introduce such a rule, or practical to enforce it; but let's say you can) then you should ban all PCs from the Internet. People would only be allowed to access the Internet via network appliances like the Foleo, which are relatively resistant to malware because they don't support on-the-fly software installation.
Right now, you're sputtering and saying something that begins with "Why should I have to give up
Parent
Re:Fine the technically illiterate (Score:4, Insightful)
By doing this they immediately stop both DoS and spam vectors. They alert the user owning the computer their computer has been infected. By simply uninstalling the NIC driver, they have not caused any long term damage. If they manage to annoy both the end user and ISP enough, one or the other is likely to do something to prevent recurring issues.
Obviously the botnet owner can attempt to prevent this but at least it turns into a cat and mouse game between the owner and the DoD. As such, the botnet owner must now spend resources protecting their harvest rather than exploiting its capabilities. So it seems like a win-win to me.
Parent
Re:Fine the technically illiterate (Score:5, Funny)
Parent
Re:Fine the technically illiterate (Score:4, Insightful)
MS already offer a range of products that do just that, I hear they are very popular.
Parent
Imagine... (Score:5, Funny)
Co-opt it.. remove it. (Score:5, Interesting)
Re:Co-opt it.. remove it. (Score:5, Interesting)
I see storm as a monoculture problem, the blame can largely be leveled at Microsoft.
Parent
monoculture problem? (Score:5, Insightful)
Suppose the market were evenly divided, 1/4 Windows, 1/4 Linux, 1/4 Macintosh, and 1/4 online game consoles that are always connected to the internet. Where would the botnets be hosted? Probably Windows. Botnets will begin to run on other platforms within about 48 hours after the security of Windows systems rises to a level equivalent to the other available platforms.
Parent
Re:monoculture problem? (Score:4, Funny)
Parent
Re:Co-opt it.. remove it. (Score:4, Informative)
Of course, this is just a guess.
Parent
Re:Co-opt it.. remove it. (Score:5, Interesting)
Parent
Re:Co-opt it.. remove it. (Score:5, Interesting)
Parent
Re:Co-opt it.. remove it. (Score:5, Insightful)
I think the real question is -- what are the FBI / police doing about it? There's a huge, ongoing, major crime happening, and there is apparently no police activity at all.
Rich.
Parent
Storm Worm - good name for sci-fi novel (Score:5, Insightful)
Plot idea 2: Now-ish. Script kiddie unleashes attack using enormous botnet. Runs out of control. Becomes so deeply imbedded into internet that it's impossible to shut down without "rebooting" the whole infrastructure. With hilarious consequences.
Plot idea 3: Medium future. Internet and control of botnets becomes so intrinsic to society that governments have less importance than internet societies. Whole "countries" exist as virtual connections of affiliated machines. With hilarious consequences.
Any of the above would work well as a Hollywood movie given Angelina Jolie and lots of gratuitous and incorrect techno-babble.
Peter
Re:Storm Worm - good name for sci-fi novel (Score:5, Interesting)
(for various versions of "script kiddie", I guess)
Of course, the above are only approximations of the listed plots. Someone with a deeper knowledge might be able to provide a better match.
Have you considered visiting your library? =)
Parent
Re:Storm Worm - good name for sci-fi novel (Score:5, Funny)
Parent
Follow the money (Score:4, Interesting)
As a side issue, how hard is it for an ISP to see an IP sending out the typical spam mail and closing off that IP/client.
Perhaps now is a good time to push for better adoption of SPF (though surely RMX would have been faster to implement?)
Re:Follow the money (Score:4, Insightful)
Parent
And again we go through this. (Score:4, Interesting)
It would be EASY for ISP's to block outgoing port 25 connections. Some of them already do.
That means that the worm would have to send through the ISP's mail servers.
Which means that the ISP can easily monitor the NUMBER of messages sent by any user. No need to dig into everyone's email. Just look for the senders who are X% higher than the average.
And watch for sudden increases in a user's mail usage. It should be easy to establish a baseline for each account.
I do that where I work to watch out for dueling vacation replies.
Parent
Re:Follow the money (Score:4, Insightful)
Parent
"Add the computers together"? (Score:5, Insightful)
Re:"Add the computers together"? (Score:5, Funny)
Parent
Threat to national security? (Score:5, Interesting)
Letters of Marque (Score:4, Interesting)
Parent
Re:Letters of Marque (Score:4, Funny)
Parent
Microsoft can help, but isn't (Score:5, Interesting)
Re:Microsoft can help, but isn't (Score:5, Interesting)
Why don't more ISPs (like Comcast and Roadrunner) self-police their machines on a much more frequent basis and knock these customers offline? 99% of the limited spam and the massive amounts of trackback attempts, other web attacks, etc all come from residential cable connections.
I know that Comcast can check their network for infected hosts and shut them off. They need to do a much better job of it.
Parent
Re:Microsoft can help, but isn't (Score:5, Interesting)
Parent
That 60s reassurance, "we can always unplug them" (Score:5, Interesting)
It's funny how things work out:
"If you add up all 500 of the top supercomputers, it blows them all away with just 2 million of its machines. It's very frightening that criminals have access to that much computing power, but there's not much we can do about it." (emphasis supplied)
So much for "we can always unplug them," eh?
It's not the servers. (Score:4, Interesting)
With that in mind, the Storm Worm specifically doesn't infect Windows 2003 server - a deliberate decision on the part of the author, I'm sure. If you upset enough businesses, they'll devote enough money to the problem to fix it.
The problem is desktops. Specifically, Windows desktops in the hands of the technically illiterate.
Just connecting an unpatched Windows box directly to the internet is enough. It belongs to a hacker in very short order. Even if you patch it up, the sheer number of services running on your average Windows box that listen to network ports is worrying. Never mind being on the internet, with the number of laptops moving in and out of corporate networks, it's not even safe "indoors". And it's hard to turn a lot of this stuff off without adversely affecting it's functionality.
I wouldn't even trust a general-purpose Linux installation on the internet ; it's just too difficult to track all the potential vulnerabilities. I keep a dedicated firewall running in my router, and the only services it runs are network translation, and a secure shell for administration, which reduces the target footprint to two highly secured services which were designed to be secure in the first place.
Windows users don't help, they are daft enough to infest themselves with everything going. Even if they are not quite daft enough to double-click executable attachments, they will download all the worst sorts of "Freeware" and click straight through the license agreement. Not only are they pwned, they actually agreed to it!
A case in point - one of our accountants was mailing around an executable Flash package (some kind of novelty). I deleted it instantly, and made a point of telling her that it could have been anything and done anything. Ten minutes later, I mailed her a VB executable decorated with the Flash icon. All it did was plonk up a dialogue box which said "Erasing hard drive". Somewhat predictably, she executed it. I almost pretended that I didn't send it and that it was a virus that emailed it.
The root problem is the design of Windows and windows applications.
1) Double-click to open OR execute
This isn't all Windows fault. People don't make a distinction between running a program and opening a file, because there isn't one in terms of the user action required. I'm willing to bet that the average user doesn't even understand the difference. If you had to perform a different action from double-click to execute programs, viral infection rates would drop enormously. You could still keep the d-click to open files with their registered program, just stop running programs themselves by this method. You've not lost the convenience of file-association. Just put "execute" on the context menu and make it a non-default action.
2) No executable flag in filesystems.
In Linux, a file isn't executable until you grant it permission to be so. If you had to open the permissions dialogue and check the "executable" box, it would hammer home the difference between executables and mere content. And by making it something more than a casual action, it would reduce the "impulse" running of many of these things, where people have their caution overridden momentarily by the promise of naked flesh or other inducements. Heck, you can even have whole filesystems that refuse to execute files - download all internet content into one of these and before you run it, you'll have to unpack it, move it to an executable folder, and check it's execute bit. This would seem too much work for the average Joe for a quick glimpse at Jessica Alba with no bra...
Parent
Does this work on Linux? (Score:5, Funny)
I'll tell you - as long as there are no worms for GNU/Linux, we won't see the masses converting to free operation system! RMS has to write a Gworm at last! If an open-source worm beats closed and proprietary Storm Worm this will be a clear indication of superiority of FLOSS!
Re:Does this work on Linux? (Score:5, Funny)
A simple email message: "This is a linux virus. It works on the honor principle. Please forward the attached bash script to everyone in your .mailrc and then execute it. Thanks."
Parent
Who'd have guessed that Windows can scale so well (Score:4, Funny)
Not really like a supercomputer though (Score:5, Funny)
Re:Not really like a supercomputer though (Score:4, Insightful)
Additionally, many botnet operations don't involve the whole botnet. A few members of the botnet may be used for warez or pr0n storage, and which only involves computers working together to achieve redundancy. Also, the use of a botnet to allow for misdirection in tracking a hacker only requires the bots to be used serially.
Parent
Where's the investigation (Score:5, Insightful)
I guess the answer has something to do with priorities. Which is exactly what I think the problem is.
Can somebody explain (Score:5, Interesting)
Re:Can somebody explain (Score:5, Funny)
This would cause a bleu screen of death on said rouge nodes.
Parent
STILL NOT A WORM (Score:5, Informative)
d8" "8b
Y8, 88 88 88 88 `8b 88 88
`Y8aaaaa, MM88MMM 88 88 88 88 `8b 88 ,adPPYba, MM88MMM
`"""""8b, 88 88 88 88 88 `8b 88 a8" "8a 88
`8b 88 88 88 88 88 `8b 88 8b d8 88
Y8a a8P 88, 88 88 88 88 `8888 "8a, ,a8" 88,
"Y88888P" "Y888 88 88 88 88 `888 `"YbbdP"' "Y888
db
d88b
d8'`8b
d8' `8b
d8YaaaaY8b
d8""""""""8b
d8' `8b
d8' `8b
I8, 8
`8b d8b d8'
"8, ,8"8, ,8"
Y8 8P Y8 8P ,adPPYba, 8b,dPPYba, 88,dPYba,,adPYba,
`8b d8' `8b d8' a8" "8a 88P' "Y8 88P' "88" "8a
`8a a8' `8a a8' 8b d8 88 88 88 88
`8a8' `8a8' "8a, ,a8" 88 88 88 88
`8' `8' `"YbbdP"' 88 88 88 88
Yes, nasty ASCII art.
Just in case you hadn't guessed (which it appears that the meeedia has not) - This Is A Trojan. Which means that it's Powered By Stupid People (tm). A worm would be Powered By Stupid Programmers (tm).
The Storm Worm is in fact already defined - It was an IIS worm. Please, feel free to look at the reputable AV lists.
Re:STILL NOT A WORM (Score:5, Informative)
gives you some information on how it operates (as of 2/07, and the names of the executables you had to click on to infect yourself have probably changed since then)
The original storm.worm (2001) attacked unpatched MS IIS servers, and actually was a worm.
http://www.securiteam.com/securitynews/5DP0B0K4KG
How this got so large is a pretty sad commentary. First off, it's proof that people will still click on attachments without verifying whether they're legitimate. I'm not convinced that any amount of training will ever stop this behavior. It hasn't worked over the *last* ten years, at any rate. Second, several virus scanners would have detected it, if they'd been kept updated. Thirdly, I've seen this running from within a couple of corporate LANs, which implies that even corporations don't always keep anti-virus software up to date, or monitor for P2P traffic, which IMO should very seldom be allowed on a corporate network.
Parent
Re:STILL NOT A WORM (Score:4, Interesting)
You have to explicitly check boxes in the configuration system to allow HTML, and/or allow external references to be loaded. The warning is right there, not buried in a dialog box man would click through:
WARNING: Allowing HTML in email may increase the risk that your system will be compromised by present and anticipated security exploits. More about HTML mails... More about external references...
The two 'more' items are links for more information.
Another box, related to MDNS responses does basically the same thing, and has the following warning:
WARNING: Unconditionally returning confirmations undermines your privacy. More...
Again, nothing in click-through dialog boxes. That was such an obviously better way to code that I adopted it as soon as I saw it. Better to have at least a brief warning and a link right there.
I'm hoping it's easier to configure Outlook this way now. In Outlook 2K, you really had to look for the settings. But even this is a teaching issue. Example: a guy I know is 100% Windows. His development shop has all the Microsoft certifications, etc. They do mostly VB apps. He complained at one point that I wasn't reading his mail, because he wasn't getting an auto-response. He couldn't imagine an environment where people didn't use that 'feature'. I actually had to take some time out and explain that it was a privacy issue (What gives you the right to know what I'm doing on my system, in a non-business environment?) and that it was wildly inaccurate anyway, as some mail systems will open a mail if you select it even if you're only dragging to another folder, while some require a double click. Or you might open it but be called away, etc.
I've known this guy forever, and he's actually pretty smart. Always did well in school, has a degree in nuclear engineering, etc. We most definitely are *not* talking IQ equal to shoe size. There's some sort of mind-set issue in play that is very difficult to get a handle on.
Parent
Block tcp/25 (Score:5, Interesting)
There's a reason why we only get 1-2 spam complaints (LARTs) per week. We aren't a source of spam. Spamming botnets are all but worthless on our network. Looking at the counters on the blocked outbound tcp/25 connections in our ACLs I literally seeing billions of hits per week. That's billions, with a B. Ba, Ba, B. Considering that we're a relatively small ISP, that's saying something. These spamming botnets would be far less useful to spammers if more ISPs took a stance and fought spam. That takes effort though.
Why nothing gets done about it. (Score:5, Interesting)
Remember Amit Yoran? [eweek.com] He was "cyber-security czar" at the US Department of Homeland Security. He started talking about the vulnerabilities implicit in Microsoft's software. His position was downgraded and he resigned in 2004.
Yoran's successor, Gregory Garcia, was a professional lobbyist, not a security expert.