Bot Infestations Reach Nearly 1.2M
mengel writes "According to the folks at SecurityFocus the number of bot-infested systems has surged to nearly 1.2 million. This after a
big drop in December when lots of people replaced/upgraded
systems. Time to upgrade your spam filtering software, the onslaught is coming."
These bots could be greatly limited with proper tweaking of liability laws. Under current laws, if I leave a pool or a car unsecured and somebody else gets injured or killed, I can be found totally or partially liable. But if I leave my computer unsecured and someone else uses it to cause harm to third parties, I'm in the clear.
This must be related somehow to Windows being the most secure operating system... :p
all those Linux and OS X systems, since Symantec says Windows is the most secure operating system.
..It's more like "time to put an ad in the paper, an onslaught of new customers is coming!" I wish I still had time to do spyware removals and clean up infested computers. Easy money for those who have the time and are willing to make housecalls.
Thanks to the War on Drugs, it's easier to buy meth than it is to buy cold medicine!
Welcome our new botnet overlords...
Didn't he say at the World Economic Forum at Dovos that as many as 25% of all machines connected to the internet were infected? That strikes me as a whole lot more than 1.2 million
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
Perhaps the big SEC bust actually had some effect. My personal harvest of spam has dropped recently from 1000/day to 500/day.
...So, what happened? Was there, in fact, a sort of mass-migration afterward, which made the more homogeneous operating system landscape a more inviting target than before? Did the operating systems change, but not to XP SP2 --- and if that's the case, what operating systems are the new computers running?
How does one know if their computer (or relative's, etc.) is infected by a bot? Are there special diagnostic tools for that?
Why don't ISPs start sending automated physical mail to home of obvious spam bots?
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
IMO, the real battle here is caused by greylisting. Greylisting plus a honeypot database of fake email addresses is clearly the most effective, automatic, general-purpose anti-spam mechanism to come along. Spammers are starting to feel the pinch (even though lots of people are still struggling with old-fashioned "filtering" mechanisms, and are still easy and fun targets).
The spammers who are starting to take on greylisting are doing so by two main mechanisms: massive distribution across IP address space, and direct use of infected PC MTAs.
The IP address spread is fairly simple to understand. If you have 100,000 zombie PCs with 100,000 IP addresses, then clearly you can send 100,000 pieces of spam without ever using the same IP address twice. That makes the honeypot database of greylisting useless, since I rely on waiting to see a given IP address send email to a known "bogus" email address to correctly identify that IP address as a spammer (in the short term, at least).
The direct use of infected PC MTAs is more difficult. If the zombie PC can programmatically use the unspecting owner's own ISP MTA to send the spam, then it becomes very difficult to distinguish that spam from real mail send from a real person (just as botnet click fraud is very difficult for Google to do anything about without also discounting some "real" clicks).
To respond to the massive distributed IP address spammer, I think a drastic increase in bogus email addresses would help, so that they have to transmit to 10 or 100 times more addresses in order to hope to reach the same # of real people. It's easier for website owners to create more bogus email addresses than it is for the spammers to infect more PCs. You basically always "drop" mail sent to a bogus address so that the spammer is convinced it went through and is getting to a "real" person (and probably even sells that address to other spammers as "verified").
That would push the spammers squarely into focussing on using the infected owner's own ISP's MTA for transmission, giving those ISPs an ever-increasing workload of bogus mail to send. Sorry, but that's where this war is headed anyway: to the point where ISPs will start charging customers to disinfect their PCs once they've been identified as botnet spam transmitters.
I'm going to start slowly increasing my spamming of spammer address databases today (e.g., by injecting more hidden text email addresses onto websites). Note that this is not a "solution" to spam (so please don't post that cute little form :-).
This is just an effort to push the problem where I think it's going to end up eventually anyway: on the backs of ISPs that have not yet come to view infected customer PCs as "their" problem yet.
http://www.spamhaus.org/pbl/index.lasso
How hard is that?
And if all major providers did it, then zombie spam would die out pretty quickly.
...and they have the nerve to call it the most secure Operating System.
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C1 bottles of beer on the wall. Take one down, pass it round... Oh, umm...
The article speaks of "bot-infested systems". Call a spade a spade. These
are bot-infested PCs running MS Windows. They make life hell for the rest of
us.
See http://www.spamhaus.org/zen/
Who are the idiots that buy the crap that make it worthwhile for spammers to install the bots that send out the spam? Shouldn't the people that create this financial incentive somehow be to blame too?
Now, if you'll excuse me, I've got some idea balls to remove from a manatee tank.
It's bit outdated. http://www.shadowserver.org/wiki/uploads/Stats/cci p.jpg
...
Let's play the game "find name missing/new countries (sorted by alphabet)".
A) Afganistan
B) Bosnia
C) Croatia
The IP address spread is fairly simple to understand. If you have 100,000 zombie PCs with 100,000 IP addresses, then clearly you can send 100,000 pieces of spam without ever using the same IP address twice. That makes the honeypot database of greylisting useless, since I rely on waiting to see a given IP address send email to a known "bogus" email address to correctly identify that IP address as a spammer (in the short term, at least).
That isn't greylisting at all (though it is useful against spam).
Greylisting is giving a "new" incoming SMTP connection a 400-series error message the first time they try to send email to you. A 400-series error means a temporary problem - please try again. When they try a second time they try to send email, you accept.
Since all legitimate email servers will retry when they get a 400-series error, a legitimate message will go through, at a cost of a time delay.
However, most spammers don't bother retrying (although some do), so you can block a lot of spam with greylisting, with very little bandwidth or CPU cost.
because Windows is the most secure OS:
2 1214
http://it.slashdot.org/article.pl?sid=07/03/22/21
In another reply I saw someone suggest ISPs sending automated snail mail notices to users who's machines have been owned.
I'll go one better. Cut the fucking thing off the net until the user fixes the problem.
I fail to see why it seems to hard to detect these things. When an ISP sees a machine go from sending out 4 or 5 emails a day to spitting out thousands of emails every hour, it should be obvious there's a problem.
Also, close the damn mail ports off. If a customer wants to host their own email server at home, fine...but make them call in and request that the port be opened. And make it clear that if their machine gets owned, they get cut off and fined before access will be reconnected.
And finally, spam has been a problem for years...how come the MTAs haven't been rewritten to not allow header forging, etc, in all that time? Isn't this supposed to be one of the big advantages of open source and open protocols?
I want a new quote. One that won't spill. One that don't cost too much. Or come in a pill.
I use ClamXAV on OS X, which is based on the GPLed clamAV anti-virus engine. I have also used clamAV embedded in the PostFix mail server on Linux to scan incoming email for sites I maintained. It gets decent reviews against other packages and I have been happy with it. I use a Windows variant when I am forced to deal with XP as well. Anyway, it is completely open source and all above-board. I would not touch Symantec software with 3.048 m pole these days.
The reason I use AV software on OS X is not just masochism. For one, I have a rarely used XP/bootcamp install and it is safer to scan it from OS X which a Windows virus cannot easily affect. For another, I avoid unwittingly passing virii from one Windows user to another. Lastly, I am paranoid and want to stay in good habits. It is quite likely that viruses will eventually appear on OS X as it grows in popularity, even though it is not as good a host. The practice costs me nothing and may save me something in the end.
The Spamhaus PBL is bad for maintaining a decentralized Internet. It forces users to send mail through ISP relays, which is an unnecessary and insecure process. It does little to prevent spam as any good spammer will just relay through the ISP's server anyway.
This page goes into grater detail explaining why DULs (the old name for PBLs) are bad.
The big question: how many infected systems are running Vista? If there are a significant number of infected Vista systems, Microsoft blew it again. (Remember, Microsoft said that Windows 95 was going to fix security. Then Windows XP was going to fix security. Then Vista...)
On the other hand, if Vista systems aren't being turned into zombies, we may be at the beginning of the end.
Spammers have had to resort to more and more desperate efforts to keep spamming. In the late 1990s, spammers could just buy a big pipe and start sending. That's dead. Then there was spamming through open relays. That's essentially dead. There used to be a significant amount of "legitimate spam". That was killed by the combination of CAN-SPAM and spam filters - if it comes from a known spam source, it gets deleted, and if the sender lies about the source, they've committed a felony. China finally cracked down on "bulletproof hosting". (There are some "bulletproof hosting" outfits left, but most are gone and some of the remaining ones may be sting operations.) Zombies are about the only way left to spam in bulk. And note how few different spams there are. The number of actual spammers left isn't that large. It's small enough for law enforcement to target.
If the zombie problem can be cracked, which ought to be possible, spamming may drop to a minor problem.
Absolute majority of spam now comes from desktops infected with mailing software. So no, in this case, the spammer won't simply relay through the ISP's mail servers. The reason they infect boxes in the first place is so that they can mail directly from all those IPs. The reasoning in your link is really outdated.
The bot problem is way exaggerated. They are very rare even insi FREE V1AGRA WITH YOUR LOW MORTGAGE!
Table-ized A.I.
If your computer is sending me spam, it's killing me by taking away, say, one second of otherwise useful life. It's doing that millions of times a day. If we total those seconds up, you've killed several people and you're still not liable for anything.
If you mod me down, I shall become more powerful than you could possibly imagine.
What the bots are doing is instead of directly sending spam out to the wide world from the zombie machine, they are reading the SMTP server settings from mail clients like Outlook and relaying mail through that instead (to avoid blocks on port 25 by ISPs)
Was I the only one whoe read it as "Bat Infestations Reach Nearly 1.2M?"
Man, are my eyes ever going fast. Stupid kerataconus.
Sometimes I wonder if I think too much.
So what about "Most Secure OS" then: http://it.slashdot.org/article.pl?sid=07/03/22/212 1214
Because of ninnies screaming "computers are too hard to secure" No, they are easier to secure than your car and house. Just run real software. Do it or get the hell off line.
In any case, I find that figure of 1.2M a bit doubtful. Given how easy it is for the average Winbloze user to get sucked into a botnet, I would have put the figure a lot higher.
Just two days ago, I had the unfortunate task of trying to disinfect my boss's wife's computer. I discovered that it was involved in no less than three botnets, as well as being riddled with more viruses than a ten-dollar tart. Needless to say, her AVG was out of date. It ended up being easier to wipe everything and start from scratch.
Are there any actual statistics for how many of these detected bots are running on Windows?
You could probably start by working backwards and making a few assumptions.
How many Linux-based botnets do you know of? If there are any at all, I really want to know.
How many OS X-based botnets do you know of? Again, if there are any at all, I really want to know.
Oh, you were saying? OK, maybe there are a few botnets running on IBM or Cray mainframes, but it takes a lot of them to make up 1.2 million.
First thing I thought when reading the subject line:
"Shit, Skynet finally took over."
How dumb do I feel now...
Actually, one of the nice things about PBL is the "Self-Service Removal Mechanism". If you are running an outgoing mail server on your pseudo-static dsl ip address, you can easily remove it from the PBL.
Even if spammers can send spam through ISP relays, most of them don't (at least not yet). Just yesterday, 23 spams were blocked by PBL on just my personal email address. I'm sure that many people see much higher results.
Increasingly bots _are_ retrying greylists now, and pretty soon they all will. However, you still have a window to analyze what they tried to send you the first time and simply block them outright if and when they try again.
Done with slashdot, done with nerds, getting a life.
> The Spamhaus PBL is bad for maintaining a decentralized Internet.
Too god damned bad. Since the current SMTP-based mail architecture lacks usable end-to-end authentication, we're expected to trust any random idiot on random connections, and hey look what we got. If you want your decentralized net back, go do it on another protocol, because as far as decentralization goes, the spammers ruined this one.
Done with slashdot, done with nerds, getting a life.
STOP BLOCKING OUTBOUND PORTS! This is not a good solution.
First, its the hotels and their blocking of the outbound VPN ports (Hampton Inn/Hilton -- I am looking at you!). Anymore, it's getting to be a crapshoot as to whether I can get on my company's VPN when I staying at a hotel. The Hilton group is just the worst offender but I have seen it at other hotels too.
And now, you want to close outbound port 25. So how do I send my e-mail? We use POP3.
I ask because there are a lot of stupid people implementing these "blocking" solutions and nobody is considering that business people use these things ALL the time while on the road. You can complain about how we are "behind" by using POP3 but until you are ready to come and migrate us to something else (for free), you don't get to decide what we use and don't use. POP3 is legal, technically allowed, standardized, and works.
(sidenote: we *can* use webmail, which helps mitigate this problem but seriously....its a real problem for anyone who does business on the road. Who wants to open their Outlook and "guess" why you can't check your e-mail? And trust me, the people at the hotels have NO idea what is and isn't blocked so they are no help either. Same for the tech support numbers at those hotels.)
My own experiments show much larger numbers: in January 2007, .7M probable/possible. The number of bots worldwide has been
one such experiment revealed a confirmed 1.8M bots with another
estimated by others as in the range of 100M (Evron et.al. 70M;
Cerf, 140M) so I very much question the methodology used here.
I wouldn't be suprised in the least if the worldwide numbers were
much higher. But there's no way they're less than ~100M.
I mean for offenders with infected machines, not everyone at large.
And now, you want to close outbound port 25. So how do I send my e-mail? We use POP3.
If you are using a VPN then the ports being blocked by the hotel are no longer relevant. They are blocking port usage on their network, but you are not using their network except as a conduit to your network. They cannot block port 25 on your VPN. They can block port 25 for IP traffic in and out of their network, which will not affect your VPN transactions.
Thank you oh grand overlord for taking our decentralized network from our unworthy hands.
Seriously, you want a CENTRALIZED network, go get one, using another protocol. One that's not chocked full of features you seem to take as bugs.
did you read my post? Outbound VPN ports are being blocked in a LOT of hotels. Yes, its counterintuitive -- but its going on in the name of protecting ppl from spam. I have no idea why they are blocking VPN's in the name of spam, but trust me, they are doing it. I run into it all the time and so have others.
Of course you can VPN and then hit your POP3 box through your own network. But what if outbound VPN port AND outbound port 25 are blocked on the hotel's network? What do you do then? Answer: nothing, you're screwed.
Since all legitimate email servers will retry when they get a 400-series error, a legitimate message will go through, at a cost of a time delay.
:-) I'm not counting on him fixing (i.e. replacing) his retarded proprietary mail system any time soon.
I think you meant "all legitimate, properly-designed email servers".
Our incoming email is filtered by a Postfix proxy that does, among other things, greylisting. Earlier this week, I had to deal with a "sysadmin" at a remote site whose email system interpreted our SMTP 450 codes as permanent failures (WTF?!?) and bounced emails back to its clients with a message to that effect.
A long chain of emails and phone calls later (why am I spending work time to educate someone I don't know?), he finally indicated understanding, but I put his domain into our whitelist just to be safe.
We have more to fear from the bungling of the incompetent than from the machinations of the wicked.
> Thank you oh grand overlord for taking our decentralized network from our unworthy hands.
You're most welcome. Get far playing the oppression card, do you?
Done with slashdot, done with nerds, getting a life.
For those of you who are hoping we are soon going to see an end to spam via the use of honey pots, gray listing, and the crackdown by SEC, I would suggest you don't get your hopes up too high. Yes - maybe spam could start dropping off, but these people aren't going to give up. These spammers are hooked on their easy money, and don't seem to be bothered by their conscience. They will just move into more evil things such as identity theft. What I wonder about the problem of bot nets - where is the leadership? Couldn't some - I don't know what - company - organization - government - whatever - start organizing an education campaign with newspaper and multimedia campaigns, speakers at PTA meetings, wherever people congregate to teach people all the things they need to know to reduce the problem? We could organize community volunteer drives, etc - you get the picture. The thing is - these bot nets represent a real evil in this world - and a national security risk. Home many people with p0wnd home machine go on to spread the infection to their offices, etc? How many of these people have sensitive data on their machines that can cause an impact far beyond that single individual? If we all worked together, we could make a huge dent in the problem - don't you think? Like for example, laws should be passed that all ISPs must do whatever minimal monitoring that is necessary to spot bot controlled machines, cut them off in the ways suggested. Why is there no highly organized effort - like a "Take Back the Net" campaign?
SMTP is not runed. The PBL is a lazy solution. With a few reality checks (ex. vaild HELO, plausible FROM address) using MIME-Defang, and a properly configured spamassassin, I can filter out any spam that would be rejected by the PBL. With a little work, you can too.
Over the last month I had 3 messages (out of thousands) that managed to get past my filter, and no legitimate mail was lost. Of the three messages, one came through an ISP relay, one through a major unix mailing list, and one came through a IP not listed on any block list. The PBL would not made a positive cotribution in any of thoes cases.
Realy, there is nothing wrong with using the PBL. Just don't use it alone to reject connections, insted use it as part of a scoring system that includes other factors. That's what all the major (gmail, yahoo, hotmail) providers do.
Oppression card? That's cute. You declare that the decentralized network is dead (which is the exact opposite of the truth, decentralization is just MAYBE starting to slow down) and then say I'm screaming 'oppression'.
What I was screaming about is the utter denial you're in about the situation, the thought that the decentralized network is dead because you said so. You're not oppressing me, in fact this is one case where attempts of oppression invariably fail. Why do they fail? Why, the nature of the decentralized network.
That's why I told you to go get your own network, not to give me mine back. In fact, since the decentralized network is so open and versatile, you can build your (virtual) centralized network right on top of the actual decentralized one.
In short, you're not oppressive (though your ideas would be if possible to implement) you're simply mistaken.
> You declare that the decentralized network is dead
... sorry for treating you like one of them.
I said it was basically dead for SMTP, thanks to the spammers. And I think it's more like it's moving toward federated, and yes, even balkanized, rather than centralized.
As long as we have "smart endpoint, dumb network", we can always have a decentralized net, and believe me I consider this a good thing. But not all protocols are nor should be so fully egalitarian. Go announce your own BGP4 ASN for example and see how far you get.
There's a lot of kooks with fiery rhetoric who rail and rant with vitriol against people who are trying to keep abuse from taking over the network -- anyone remember Dave Hayes? Anyway, you don't come off like that now
Done with slashdot, done with nerds, getting a life.