Slashdot Mirror


Is the Botnet Battle Already Lost?

An anonymous reader writes "Researchers are finding it practically futile to keep up with evolving botnet attacks. 'We've known about [the threat from] botnets for a few years, but we're only now figuring out how they really work, and I'm afraid we might be two to three years behind in terms of response mechanisms,' said Marcus Sachs, a deputy director in the Computer Science Laboratory of SRI International, in Arlington, Va. There is a general feeling of hopelessness as botnet hunters discover that, after years of mitigating command and controls, the effort has largely gone to waste. 'We've managed to hold back the tide, but, for the most part, it's been useless,' said Gadi Evron, a security evangelist at Beyond Security, in Netanya, Israel, and a leader in the botnet-hunting community. 'When we disable a command-and-control server, the botnet is immediately re-created on another host. We're not hurting them anymore.' There is an interesting image gallery of a botnet in action as discovered by security researcher Sunbelt Software."

22 of 374 comments (clear)

  1. Re:Problem Solved by TCM · · Score: 2, Interesting

    I don't think that bots are invited. This wouldn't make sense from an administrative view. The channels are probably password-protected. Nothing a little sniffing can't fix.

    After all, the bot is code running locally. So if it contains any channel names, channel keys or cryptographic keys, you can get to them.

    --
    Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
  2. Restrictive Firewall Infection by Anonymous Coward · · Score: 2, Interesting

    Why hasn't anybody created a "good" trojan that uses as many common exploits as possible to infect these already infected machines with a port-80 restrictive firewall? I think for every somewhat bright for-profit trojan creator, there are thousands of brighter people that can come up with an intelligent plan to do this effectively. Use all spreading techniques that the best of the worst use, but minimize the wasted & bloated traffic, while fixing as many computers as possible. Should be simple!!

    Only issue I see is legality. Technically however, I see this as very feasible.

    1. Re:Restrictive Firewall Infection by toadlife · · Score: 3, Interesting

      Sorry, but besides the fact that it's illegal and unethical, it would probably only make things worse anyway.

      The Nachi worm that tried to fix Blaster worm infected PCs back in 2003. Unfortunately, the "cure" was worse than the disease.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  3. We need a really big lawsuit against Microsoft by Animats · · Score: 3, Interesting

    What's needed is for someone like NY Attorney General Elliot Spitzer to charge Microsoft with reckless endangerment for knowingly, willfully, and negligently distributing and continuing to distribute systems vulnerable to such attacks.

    Meanwhile, we may need some brutal firewalls:

    • All incoming e-mail is reformatted. Attachments are converted to .odf or .png, as appropriate. Stuff that can't be converted is dropped. HTML is parsed, checked for syntax, and Javascript dropped.
    • All web browsing to non-secure sites is proxied. Javascript is removed. Flash is removed. Java is removed. All binary data is removed. Images are reformatted to .png format and the HTML adjusted to match. No more "Web 2.0"; those sites just stop working.
    • Web browsing to secure sites via SSL is only permitted if the site has a SSL cert that is a high-grade "we really know who this is" cert.
    • TCP port 80 is all you get outgoing. Incoming, forget it. UDP, forget it. If you want to message, use the phone.
    • You have a machine or two around that are outside the firewall for when you desperately need to do something else. Those machines have a canned read-only disk image that's refreshed on each reboot or logout, like Internet cafe machines.

    We're probably going to see some companies going to a locked down firewall like that.

  4. use the clients against themselves by TheSHAD0W · · Score: 3, Interesting

    Modern botnets clients are pretty adaptable; they will download patches, modifying themselves to beat disinfectors. With care, and unless the net manager has taken extreme measures to prevent it, one can induce the clients to remove or disable themselves, rather than just trying to kill the control channel. Should that fail, one should be able to determine what fallback channels the botnet clients use and disable those before killing the current command channel.

  5. We need a trusted network of ISPs by Ignorant+Aardvark · · Score: 4, Interesting

    What we need is a large number of ISPs to get together and say, "We trust each other to deal with botnets." Then, with a single command, any trusted ISP within the network could instantly send a command to another ISP to shutdown a site or server that is running a botnet. All of these actions would be logged and would be reviewed to make sure that it is only being used against botnets; any sort of abuse (like using it to shut down protest sites or copyright violation sites) would result in an instant revocation of privileges. This system would be much better than what we currently have: trying to call the other ISP, trying to get them to listen to you, trying to get them to trust you ... it can take days, if ever, to shut down a botnet on another network.

  6. Re:Problem Solved by TubeSteak · · Score: 2, Interesting
    The channels are probably password-protected. Nothing a little sniffing can't fix.
    If you've ever been in an XDCC file channel on IRC, you'll see some channels even name their bots XYZ-EDU

    There is no easy solution

    http://images.slashdot.org/hc/07/4a6fece962b0.jpg
    --
    [Fuck Beta]
    o0t!
  7. Sue/address the IRC networks, first. by SuperBanana · · Score: 5, Interesting

    What's needed is for someone like NY Attorney General Elliot Spitzer to charge Microsoft with reckless endangerment for knowingly, willfully, and negligently distributing and continuing to distribute systems vulnerable to such attacks.

    Sue the IRC networks first; that's what makes it dumb shit easy for these guys to set up their botnets.

    I had a machine hacked by a german movie filesharing group, and they incldued a bot which logged into their channel on Rizon. Like a good little admin, I logged into rizon, checked out the channel. It had several thousand users, a whole slew of fserves...and ZERO conversation. None.

    I went to #help and reported the botnet attack and the response was: "hey, you want us to shut down one of the most popular channels here because of a evidenceless accusation that you were hacked by them and used as one of their fserves? LOL ZOMG GET SECURITY AHAHAHAHAHA LUSER P0WNZORED" etc. etc.

    It is patently obvious that the Rizon admins are FULLY aware that they have dozens, if not hundreds, of illegal filesharing groups that are using botnets to set up fserves, attack other systems for more bots, etc. They're doing jack shit about it (and in fact, they're making it easier- they now support SSL connections) and I think it's time someone sued them to hell and back. It's time IRC operators were taught that you can't knowingly support criminal activity, and that if users report hackings- they need to look into said reports and act on them. I also think it's time IRC traffic was considered "highly suspicous" and monitored by ISPs for fserve commands and such; fserves have no real legitimate purpose today, except illegal filesharing.

    PS: Next time you download a movie or program, bittorrent or IRC DCC....realize that it was distributed, most likely, by a group that hacked unix systems. Those systems were owned and administered by people just like you, and that person is going to have to deal with the damage and headaches. Just like you will, some day.

    1. Re:Sue/address the IRC networks, first. by dosius · · Score: 2, Interesting

      I can assure you, neither of my IRC channels that have fservs have bots from compromised hosts. I wouldn't stand for it anyway. I'd rather my bandwidth be legitimately bought and paid for (or donated as the case may be).

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
  8. Re:A modest proposal by ZSpade · · Score: 3, Interesting

    This was done with klez... a good Samaritan wrote a virus that would spread to computers as effectively as klez, look for it, and then eliminate it if found. You know how you knew if you had the Good Samaritan virus? Klez like symptoms. That is a major system slow down, as well as many, many bugs/crashes.

    Good times. Viruses like that operate at levels that were only really meant for system tasks, and yet they are were never part of that system. Windows being the careful balancing act that it already is will topple over readily when you add anything to the base.

    --
    Go ahead and call me unreliable; reliable is just a synonym for predictable.
  9. My comments.. by paulmer2003 · · Score: 5, Interesting
    A long time ago, I used to run botnets and that other bullshit...So take it as I know what I am talking about.

    It is a pity that the general open channels are a thing of the past, but so are private BBS'.
    This is not true at all. There are plenty of -sp channels on IRC. Hell, just do a /list on EFnet...thousands upon thousands. And usually, when just going around IRC, you arent just going to walk up upon a botnet..
    With care, and unless the net manager has taken extreme measures to prevent it, one can induce the clients to remove or disable themselves, rather than just trying to kill the control channel.
    No shit. Simply decompile the exec, get the password (shouldent be hard, unless it is encrypted, usually isnt), get the server ip/port/password/channel and possibly channel key, join the channel, login to the bots (.l password or what ever) and do .rm and boom, they lost their entire net (thats assuming they have it set so *!*@* can login).
    Basically this is a problem with people owning computers who don't know how to maintain them properly, and with MS making it unreasonably difficult, expensive, and time-consuming to maintain a Windows machine properly.
    Now now. I am a Linux fan and such, but blaming Microsoft here is just stupid! You know why? Because usaully the thing is exploited hasent been patched yet. Every program has bugs, thats just how it is. Get over it. And how is it expensive to maintain windows machines properly? Windows Update is free, no?
    But as someone who doesn't run Windows, I don't really care.
    While *nix botnets arent nearly as prevalent as Windows botnets, there are still ones out there...Dont think you are exempt.
    nother possibility is that somebody I do business with could get their machines owned, and gangsters could steal my identity.

    Its very easy to get your identity stolen these days..Simply do some SQL injection on a pron site or what ever, then boom, you got yourself 5k credit cards.
    Why can't we all just hit "delete"? takes only a few seconds.
    Were you dropped a child? On Windows, you cant delete a exec if its running..and most botnet execs fuck up things like the task manager and have backups of themselfs on your box.
    Why isn't it possible to simply identify the exploit being used to spread a particular botnet, and write software that uses the same exploit to travel throughout the net before activating (perhaps at some specific time) to both wipe out the botnet software and seal off the exploit?
    Easier said than done. How does your 'software' know what on the machine is a trojan? That wouldent be very good would it if your 'software' illegally compromised hosts trying to get rid of the trojans and accidently got some guys stuff that isnt infected? Also consider, when ever a new exploit is leaked in to the wild, all of the current botnet trojans are updated with it...There are widely diffrent...there is no plasuable way to just rid of all hosts comprimised with hole ____
  10. Re:Maybe I'm being complacent, ... by jcr · · Score: 2, Interesting

    But as someone who doesn't run Windows, I don't really care. Well, I do care, because a lot of the bandwidth I pay for is crowded by the spam that my hosts filter for me. Not to mention, the bandwidth wasted and the increased cost of network service that comes from millions of unsecurable windows machines trying to infect each other with the malware of the minute. If anyone ever sets up a "no windows allowed" ISP, I'd be a customer in a heartbeat. -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  11. Actually by Shadowruni · · Score: 1, Interesting

    This was the subject of "As the worm turns", in the first Stealing the Network (an AWESOME book). The protagonist disassembles a worm and then figures out how to fix, with some unintended consequences. A great read, the story is fictional but the technology is VERY real. Almost a HOWTO in fact.

    --
    "Chinese Amazons, power armor, laser swords.... things just meant to be." - Shampoo, A Very Scary Bet
  12. RBL by theglassishalf · · Score: 3, Interesting
    In the end, this problem is only going to get mitigated if we take it as seriously as we did the spam problem. For a long time, ISPs would allow spammers onto their servers because there was no incentive to kick them off. RBLs changed all that.

    ISPs that tolerate insecure computers need to get blocked. Blocked from everything. It COULD happen, if Comcast and AT&T both decide they've had enough.

    This would have the added benefit of stopping a lot of spam.

    Yes, RBLs didn't get rid of spam. But they sure did (do) help. And a good part of the reason they don't work better is botnets. (remember Blue Security?

    -Daniel

  13. Until people are punished for their system's behav by Banner · · Score: 2, Interesting

    Unitl people are punished for their system's behavior, nothing is ever going to happen. Yeah it's annoying for most people to get rooted, but other than that, why should they care? Now if you were legally liable for the damages your system did, regardless of whether or not it was rooted, we'd see a major change in botnets, and a LOT less people with rooted machines.

    People only react to that which causes them difficulty, punish them for not taking care of their responsibilities and things will get better. But until then, it will only get worse.

    You're part of a botnet? Pay a fine! Didn't know? Too bad. Just like your dog getting out and destroying property, if you don't care enough to protect others from your wanton disregard, it's going to cost you.

  14. Re:I have already said it by N3Roaster · · Score: 3, Interesting

    It already does. It's called Underrated. Still waiting for -1 Wrong, personally (not that it applies here).

    --
    Remember RFC 873!
  15. The Good Old Days... by Horar · · Score: 2, Interesting

    when high technology was its own idiot filter are long gone.

    It is illegal to drive a car on any public road without a drivers licence, for the safety of other road users. Why shouldn't it be illegal to connect a computer to the internet without the proper qualifications, again for the common good? Keep all the stupid off the internet and the situation is bound to improve because there will be less opportunity for the greedy to exploit them.

  16. There's a simpler way by Der+Huhn+Teufel · · Score: 2, Interesting

    If companies know the means of advertising (i.e. malware) are illegal, why aren't we going after the companies that use such methods? Admittedly, some viagra knock off company in Mexico is difficult to go after, but wouldn't it be easier to get rid of these intrusive networks by cutting off any reason for them to exist?

  17. Re:Until people are punished for their system's be by Anonymous Coward · · Score: 1, Interesting

    Most people, including extremely technical people, don't know exactly what is going on on their systems at all times, be those Windows, Mac, or Unix systems, or anything else. Why don't you tell us your foolproof method for knowing exactly what code is running on a system in the presence of rootkits and thread injection?

    Your dog analogy is broken: a good dog owner knows what the dog is doing at any moment in which it could cause harm to someone else's property. Even a competent technical person has no idea what's going on on their computer with a rootkit cloaking the traces.

    Guess what? I've been a professional reverse engineer for three years, and I still say this.

  18. Re:It's simple. They don't care. by RAMMS+EIN · · Score: 5, Interesting

    ``d) don't care''

    And that is a matter of economics; specifically, externalities. You would bear the cost of securing your system, but you aren't seeing the cost of running an insecure one.

    In the Netherlands, at least one large network employs a detection mechanism for exploited hosts using honeypots. A lot of the IPs on the network get assigned to honeypots, so that a compromised host is likely to hit a honeypot sooner or later. The compromised host is that put in quarantine, denying it normal Internet access (only access to information and removal tools is still available). This hurts users when their machines are compromised, encouraging them to secure their systems.

    It surprises me that this isn't done more often. Surely ISPs have something to gain from eliminating all the traffic that compromised hosts generate (seeing that 90% of email traffic is spam, and the bulk of it comes from compromised machines, just to name one thing).

    --
    Please correct me if I got my facts wrong.
  19. Re:How do you know if you've been rooted? by jofny · · Score: 2, Interesting

    Yeah...that's all well and good as long as the traffic isn't encrypted (it probably will be)..or it it's not, you know what to look for to write sigs for (you probably won't)...or you know which domains people in your network shouldnt be going to and youre watching dns logs (you probably won't). With all of the custom and targeted attack vectors, the fact that so many attacks have moved up the stack to layer 7 and above (humans), Network IDS's have passed their due date. The only thing that can really help is to engineer your host systems, create well defined policies, and install local host system monitoring software (HIDS, etc.), and secure those logs from tampering. Network security monitoring at this point is really a lot like airport security: It gives people a warm and fuzzy, but it doesn't accomplish much and the effort is better spent elsewhere.

  20. How do you Know and REMOVE them? by lordmage · · Score: 2, Interesting

    I have a lovely wife who surfs the internet constantly. She has a bot on her Windows Box. I noticed it when we sent out 86 thousand emails in one day. (it helps to monitor your port 25!!). Okay.. so she is compromised.

    Norton, Spybot, etc CANNOT detect what she has. Netstat shows the connection but taskmanager etc does not. I block port 25 from her computer as a precaution and the darn computer starts searching for smtp servers on the local network. I use qmail-auth and it prevents it.. however I have no trust that it cant use UPnP or something else to change my main router.

    So.. HOW IN THE HECK do you REMOVE stuff that you cant find? I really.. REALLY.. dont want to reformat and reinstall because there is no way this should be hidden to adminstrator on Windows XP.. but it IS!

    --
    I can program myself out of a Hello World Contest!!