Slashdot Mirror


Deconstructing a Pump-and-Dump Spam Botnet

Behind the Front writes "eWeek has teamed up with Joe Stewart, a senior security researcher at SecureWorks in Atlanta, to show the inner working of a massive botnet that is responsible for the recent surge of 'pump and dump' spam. It's a detailed picture of how these sleazy operations work and why they're so hard to shut down. Sobering numbers: 70,000 infected machines capable of pumping out a billion messages a day, virtually all of them for penis enlargement and stock scams. Excellent graphics, too, including one chart that shows that Windows XP Service Pack 2 is hosting nearly half the attacked machines."

30 of 382 comments (clear)

  1. Filter by insecuritiez · · Score: 4, Insightful

    If more ISPs did egress filtering of email this sort of thing would be harder to do.

    1. Re:Filter by DeGem · · Score: 2, Insightful

      Your assuming that the spam is comming off a mail server the ISP is controling.

      --
      Smile It hurts!
    2. Re:Filter by jfengel · · Score: 5, Insightful

      I hear that. It just doesn't seem unreasonable to me to cut off a customer who is sending tens of thousands of email per day. Put the very few with a legitimate reason on a white list (after a phone call) and cut the rest off until they clean up their act.

      As Heinlein said, the answer to any question beginning with "Why don't they..." is "money". Presumably the ISPs figure you'll just take your business and your bot-infested computer elsewhere. But maybe if a few major ISPs got together and agreed to all do it, they'd cut off enough spam to make their customer bases happier, and attract back those customers who gave up in frustration.

    3. Re:Filter by giorgiofr · · Score: 2, Insightful

      Wrong solution. If a mail server admin does not want to receive spam from residential IPs, he has the means to block before it even reaches the server. Lists of such IPs abound.

      --
      Global warming is a cube.
    4. Re:Filter by ILikeRed · · Score: 2, Insightful

      No, just block port 25 to all servers other than the ISPs for dynamic IP addresses. If they do not want to use their ISPs mail server, they can purchase a static IP, or set up a proxy with a different port. If you are not capable of doing either of those things, then you should not have the privilege.

      --
      I have come to a conclusion that one useless man is a shame, two is a law firm, and three or more is a congress -J Adams
    5. Re:Filter by RichMan · · Score: 4, Insightful

      > No, just block port 25 to all servers other than the ISPs for dynamic IP addresses.

      I thought I paid for IP access. Deliberate port blocking by my ISP is blocking services I pay for.

      IP access means IP access, it does mean port 80 web surfing only. Any steps toward that are plain wrong.

      I agree it is a wild world out there but it is a problem of weak clients. The service provider should be blind unless a client is affecting network performance beyond their paid for slice. Then the client should be totally blocked.

    6. Re:Filter by Hognoxious · · Score: 3, Insightful
      If you are not capable of doing either of those things, then you should not have the privilege.
      What if I don't want to go jump through hoops, or pay double for the privelege? What if I want to acess my work mail server from home? Or a clients? Or I just want to access the email that I've been using for years via pop/smtp?

      Are you one of those imbeciles at Belgacom or something? Because they implemented the same cretinous strategy (without any advance warning, I may add) as you're suggesting.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    7. Re:Filter by berzerke · · Score: 2, Insightful

      No, just block port 25 to all servers other than the ISPs for dynamic IP addresses.

      Some ISP's do this. And this is reason I can't set up a SPF record for my domain. All my parents outgoing email would fail and their ISP (AT&T) doesn't publish any SPF records (and what if they change ISP's, something they have been talking about doing). Considering they are on dail-up, buying a static IP is out of the question. Getting AT&T to unblock them is impossible (I've tried).

    8. Re:Filter by tha_mink · · Score: 3, Insightful

      I think everyone is missing the point here. The problem really isn't spam. It's the fact that there are botnets out there that are 70,000 strong. Thank god they're only sending enlarge-your-penis emails. Instead of spending energy trying to stop the symptom, let's try and stop the disease. Forget the email, let's figure out a way to stop the infections in the first place. Then there's the issue of cutting off the funding. Why not try and stop the funders of spam. I think that BlueSecurity had it completely right. Piss off the people paying the spammers, and you stop the spam. Nobody's going to send spam for fun, and if they did, maybe we wouldn't mind reading them so much. 1. Stop the infections 2. Stop the funders of spam. 3. Profit! It's a simple as that. I hate how people miss the point on this spam stuff. The spam is only the symptom.

      --
      You'll have that sometimes...
    9. Re:Filter by jetmarc · · Score: 2, Insightful

      > No, just block port 25 to all servers other than the ISPs for
      > dynamic IP addresses. If they do not want to use their ISPs
      > mail server, they can purchase a static IP, or set up a proxy
      > with a different port.

      I did purchase a static IP and pay for it on the monthly bill. Yet half of my outgoing email is still returned as "rejected for possible spam".

      Maybe your provider keeps "static" IPS separate from "dynamic IPs". Mine appearently doesn't (just assigns me one of his IPs as static). Or the RBLs are too ignorant to learn about static and dynamic IP ranges of smaller countries like the one I live in (Spain, Europe).

      So, go ahead and do whatever you want on your own server. But please DO NOT encourage other people to block so-called "dynamic" IPs, because this blocks most non-US static IPs as well.

      I mean, that's like blocking asian senders. Quite efficient, unless you are asian abroad and want read your friends mail.

      Marc

  2. you are missing the point by weierstrass · · Score: 2, Insightful

    then they would use the massive botnets of 0wned machines for something else, that probably also wouldn't be conducive to the health and general well-being of the internet...

    --
    my password really is 'stinkypants'
  3. Infection vs Market Share by MrSplog · · Score: 4, Insightful

    The charts would be a lot more interesting if they had them compared to market share. then you've got to consider that people are more likely to target the biggest market share. i mean, how many virus writers are targeting FDOS?

    1. Re:Infection vs Market Share by Ilgaz · · Score: 2, Insightful

      I understand what you mean. Check the hacked servers http://www.phishtank.com/ , almost all run Apache on Linux. Why? It has bigger marketshare on webservers.

      I think the OS X, Linux, FreeBSD "I am invulnerable because of OS I run, I don't need security updates or basic sense of security" will cause problems soon just like phishing.

    2. Re:Infection vs Market Share by misleb · · Score: 1, Insightful

      Even more likely, it is just bad PHP (usually Linux/Apache) that allows SQL injection or XSS. You dont' necessarily have to hack the servern OS itself just to get a list of addresses. There are lot of well known, vulnerable PHP apps out there such as old versions awstats. Patching your OS (which in the case of most Linuxes would include apache) is one thing, but trying to keep all your PHP up to date and secure is quite another. Plenty of otherwise security conscious admins are running vulnerable PHP code.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  4. Rebuild the email protocol by Hoi+Polloi · · Score: 5, Insightful

    It is time to rebuild the email protocol. It needs to be redesigned to cope with modern systems and security needs. The pain of the transition would be worth it. It is just too easy to spoof header info now.

    --
    It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
    1. Re:Rebuild the email protocol by Archangel+Michael · · Score: 4, Insightful

      The "we can't change anything because it is too hard waaaaaaa" post.

      Thank you for being a wimp.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    2. Re:Rebuild the email protocol by Renegade88 · · Score: 2, Insightful

      Am I the only one who thinks this form-checkbox type of comment is trite? It's not original, it's not funny, it's annoying at best. Stop doing it.

    3. Re:Rebuild the email protocol by LordEd · · Score: 2, Insightful

      Ah.... The "we can't change anything because it is too hard waaaaaaa" post.

      Thank you for being a wimp.

    4. Re:Rebuild the email protocol by Anonymous Coward · · Score: 1, Insightful

      Funny how you can say with such certainty that it will not work, when no one has ever tried it.

      Look, all that needs to be done is adding a 'confirmation' ability. This could be an encrypted header in the email. Encrypted using the Sending Server's Private key, it requires the Server's Public key to de-crypt. The email server's Public Key is available for download from the Upstream Provider of the Email server. If spam gets sent, you complain to the upstream, and they revoke the Public key. Viola! The spammers spam keeps getting sent, but it is no longer 'confirmed'. Email clients can be configured to trash unconfirmed emails. therefore, the spam gets trashed. OR, if you are a masochist, you can tell your email client to not treat un-confirmed emails differently from confirmed emails.

      This could EASILY be done as an ADD-ON (or plug-in) to existing email software. "Old" email software WOULD CONTINUE TO WORK, just without the confirmation step. As newer versions of clients and servers came out and were installed, they could be gradually upgraded to work with the new system, and there is no problem with "existing investment in SMTP".

      Even AFTER [almost] everyone switches to the 'Email-with-confirmation', people can still continue to receive un-confirmed email. People can still send un-confirmed email. A small company or User Group or hobby mailing list can still use an un-confirmed email server- they just have to let the people they are sending to know to white-list their emails.

      'Confirmation' is just a fancy way of knowing FOR SURE who sent the mail (If the header decrypts with Company A's Public Key, then it came from Company A's email server), AND who their Upstream internet provider is (where the Public Key was downloaded from). This allows spam to be definitively traced to the sender, and the people responsible for 'certifying' the sender (the upstream). "Big-ISP" likes to confim spammers? Tell your client to ignore all their confirmations.

      It CAN be done. It WILL work. You-all just need to make it happeninstead of posting stupid (and wrong) form letter replies.

  5. thats okay, but how to detect this infection? by Anonymous Coward · · Score: 4, Insightful

    Perused the article to know how to find out if my computer is infected or not but couldn't find anything. This is such an important news for Windows users, at least tell something abou thow to verify if a particular windows machine is having this problem.

  6. C'mon by Tarlus · · Score: 3, Insightful

    Well of course Windows is going to be in the majority of affected machines... There is a dramatically higher number of people in the world using Windows than any other OS, so... wouldn't it make sense?

    As a proud user of Kubuntu, I can relate to /.'s tendency to point out everything that appears to be wrong with Windows... but come on, isn't it a little much to explicitly point it out in this case?

    --
    /* No Comment */
    1. Re:C'mon by Mark+Hood · · Score: 3, Insightful

      Actually, the dig was at Windows XP SP2 in particular - not just Windows generally.

      If these bots have control over 'the most secure Windows yet', then that is worthy of note.

      Mark

      PS Yes, I know the link is from 2004 - but they've not released anything since, so it must still be true, right?

      --
      Liked this comment? Why not buy me something nice
  7. I'm just surprised that those spams still ... by Jawood · · Score: 4, Insightful
    work. After all, the folks who are doing the "advertising" must be getting some sort of return.

    Which leads me to wonder about the folks who actually believe that those penis enlargement pills work.

    And as far as the "pump and dump" spam goes, are there folks who beleive those spams? Or are they of the mindset of the "greater sucker"? Meaning, if I buy this stock now, after this spam circulates, there will be others who buy this shit stock and push up the price allowing me to make money.

    Yeah, I know the guy who originates the "buy" recomendation is hoping for everyone to buy the stock, but what makes some of the recipients think they'll make out?

  8. Re:eweek confirms it: Linux and Mac are dying! by mrjb · · Score: 4, Insightful

    Do you really think that 0.05% of all spam comes from Linux, BSD, MacOS, Solaris and OS/2 lumped together? Then I'll have to disappoint you. Look again. Windows 95 is curiously absent from the graph. How big a part of 0.05% do you think it could handle?

    --
    Visit http://ringbreak.dnd.utwente.nl/~mrjb/growingbettersoftware to download your free copy of the book
  9. Hit the nail right between the eyes. by Rob+T+Firefly · · Score: 4, Insightful

    This is the basic problem with any single antispam measure, or really any single computer security measure.

    1. Someone comes up with a defense mechanism that works well.
    2. It works so well that more people use it.
    3. It becomes popular enough for the bad guys to beat, so they do.
    4. The defense becomes useless, forcing someone to come up with a new defense.
    5. Goto 1.

  10. Re:Class action against Microsoft by cdn-programmer · · Score: 2, Insightful

    Its like going after Boeing because someone put some tape over the port that allows outside air to get at the gauge that measures air pressure and estimates elevation on a 757.

    You can point your finger all you want at the maintenance worker who didn't read the warnings in GIANT PRINT - but Boeing was still sued and paid.

    Boeing was not being irresponsible. I do not think the same can be said of Microsoft because many of the security problems have been pointed out CONSTANTLY since before 1995.

  11. Re:Class action against Microsoft by shark72 · · Score: 2, Insightful

    "Thats crazy... that's like going after P2P admins for users sharing illegal content. It would never fly."

    It's not like that at all, but that's due to a distinction that's apparently too fine for some people.

    Take a look at your favorite torrent tracker. Unless it's legaltorrents or something of its ilk, you know they set it up to capitalize on the huge demand for pirated material (and to make ad money off same), you know most of the traffic is pirated material, and you know that the admin knows this. Running a tracker with the belief that you will simply be able to tell the authorities that you're "not responsible for your users" might make perfect sense to a 14-year-old, but they're often unaware of a crucible in the legal profession known as "the laugh test." If it has the proper locomotion, vocalizations, and behavior, smart people don't need to be told that it's a duck.

    Now, it might be funny and all to say that yes, Microsoft really does sell XP primarily for the purpose of running botnets and sending spam, but again, you, I, and everybody else know that it's simply not true. Again, the laugh test prevails.

    --
    Sitting in my day care, the art is decopainted.
  12. Re:Hasn't worked for me by bitflip · · Score: 2, Insightful

    You should be short selling them, instead.

  13. Re:where does it end? by ummit · · Score: 3, Insightful
    I hear you, but: put yourself in the shoes of "Joe Homeowner" for a moment, if you will. You know nothing about chemistry or combustion. You simply purchased your house because you needed a roof over your head. But the law requires you to install smoke detectors (and, in many jurisdictions now, also carbon monoxide detectors). In fact, the reason this is a law is precisely because the average homeowner knows nothing about chemistry or combustion; that's why people need emphatic (enforceable) reminders to install these safety devices.

    So a law that mandated safe computing clearly would not be out of the question, and would not be "blaming" those computer users who did nothing more than purchase a brand new PC in order to use it for its intended purposes.

  14. Subject by Legion303 · · Score: 3, Insightful

    There's a lot of humor potential in going to a site laced with ads and a list of 30 sponsors to read about spam.