Slashdot Mirror


Windows/NetBIOS pop-up Spam:

bofus writes "This article from Wired News presents a new way to deliver unsolicited advertising content - the MS Windows Messenger service. It appears that the client software hasn't been widely distributed yet, but it's probably only a matter of time before a free clone is circulating. This method could become the delivery method of choice for all kinds of unsolicited junk, given the number of unsecured PCs out there. On the flip side, if you run a relatively secured machine and have some sort of firewall, this probably shouldn't concern you."

27 of 411 comments (clear)

  1. ahh nuts! by Quasar1999 · · Score: 5, Funny

    I wasn't sure how to take this message...

    Hello, would you like to get laid? Call me at xxx-xxx-xxxx

    alas, now that I know it's spam.. my hopes have been crushed... :(

    --

    ---
    Programming is like sex... Make one mistake and support it the rest of your life.
    1. Re:ahh nuts! by blonde+rser · · Score: 5, Funny

      I wasn't sure how to take this message...

      Hello, would you like to get laid? Call me at xxx-xxx-xxxx

      alas, now that I know it's spam.. my hopes have been crushed... :(


      Of course I meant it. But you never called :(

  2. what client ?!?1 by Archfeld · · Score: 5, Informative

    try "net send IPADDR"

    it is a cli and batchable, this can be supremely irritating as the only info given with the popup is wins name which is useless unless you are in the same domain/ou.

    --
    errr....umm...*whooosh* *whoosh* Is this thing on ?
  3. Good article, real funny by LittleBigScript · · Score: 5, Funny

    "I have customers who call me back and tell me they love it and it generates hundreds of calls right away," said Kovacs, who noted blah...blah...blah..

    That sure is a funny way to say "death threats."

    "The girls of the internet. Ooh, I'd go online with them anyday!"
    -Homer Simpson

  4. net send by mrgrey · · Score: 5, Funny
    I get really bored in my NT4 Server class one day and wrote a small stupid batch file that utilized the net send command.

    :one
    net send %1 "crapflood of info"
    goto one


    It was kind of amusing to watch. People would click the OK button on the message and as soon as it went away another popped up. The best thing is the beep that accompanies the message. Oh the assinine joy....

    --
    -Tolerate my intolerance
  5. Re:SPAM by Jucius+Maximus · · Score: 5, Funny
    This is so much more up close and personal than e-mail spam.

    All it will take is a few pr0n campaigns through this thing, and backlash will be quick to follow.

    You might be able to increase the intensity and speed of the backlash by sending a pr0n ad to a machine conennected to a WiFi network during a powerpoint presentation to stockholders or upper management. (teehee!)

  6. Do yourself a favor - kill this service anyways. by Ian+Wolf · · Score: 5, Informative

    While you're at it disable Remote Registry while you are at it. It truly amazes what services Microsoft deems the average user needs running. I find the whole concept of Remote Registry particularly disturbing.

    "Cool this service allows people to modify my registry remotely, sweet!"

    While I know there are some legitimate and possibly useful reasons to have these services enabled, why on earth are they enabled by default?

    --
    "The words of the prophets are written on the Slashdot walls."
  7. its almost as if... by diesel_jackass · · Score: 5, Informative

    ...we just talked about this :-)

    There were many helpful suggestions in those posts.

  8. Re:MSN Messanger Alternative by Dr+Caleb · · Score: 5, Informative
    It has nothing to do with MSN Messenger, but the "Messenger" service in Win2k and XP. As in from a cli "Net send..."

    Much worse in my opinion. MSN Messenger could be uninstalled.

    --
    "History doesn't repeat itself, but it does rhyme." Mark Twain
  9. net send slashdot "First post!" by Nintendork · · Score: 5, Funny

    Don't tell the spammers that there's already a utility that can abuse the messenger service. There is no such thing as the net.exe command line utility.

  10. Only "positive" feedback? by gpinzone · · Score: 5, Funny

    "I have customers who call me back and tell me they love it and it generates hundreds of calls right away," said Kovacs.

    What about the thousands of calls that go something like, "YOU MOTHER F*CKER!!! STOP MAKING THESE F*CKING POPUPS COME UP WHEN I'M PLAYING COUNTERSTRIKE OR I'LL F*CKING RIP OFF YOUR F*CKING HEAD AND F*CKING SH*T DOWN YOUR F*CKING NECK!!!!!"

    Sorry, I don't have anything else to say. The stupid lameness filter is censoring my post for yelling.

  11. How to disable it in windows 2000 by Jucius+Maximus · · Score: 5, Informative
    Here are my homebrew instructions on how to turn off the Messaging service that's used to receive the spam on Windows 2000. (Of course you will miss legit messages from your admin if your corporate IT people use that feature.)

    1. Log on as administrator or at least with an account that has admin access.

    2. Enter control panel

    3. Enter "Administrative Tools"

    4. Enter "Services"

    5. Scroll down and find "Messenger"

    6. Right click > properties > startup type > Disabled.

    Scroll through the list and see if there's anything else you might want to disable. (You know, like remote registry editing and all that stuff that Microsoft enabled so you wouldn't have to be troubled to do it yourself :-)

    1. Re:How to disable it in windows 2000 by NexusTw1n · · Score: 5, Informative

      Go here for a full list of what is good and bad to disable in the windows services screen.

      --
      It has become appallingly obvious that our technology has exceeded our humanity. --Albert Einstein
    2. Re:How to disable it in windows 2000 by murat · · Score: 5, Informative

      You can start and stop services from the command line fast.

      open a cmd [ (leftwindows)r(/leftwindows) cmd (enter) ]

      Type "net stop messenger" without the quotes.

      You can start it back by typing "net start messenger".

      Say, you need to send a message to someone in your LAN, you open it, then close it back.

  12. already out there by htmlboy · · Score: 5, Interesting

    two weeks ago, we had a big hulabaloo here at uiuc.edu because of this. all the win2k/xp machines on all of campus still running the messenger service got a popup describing how great our lives would be if only we had a diploma from a non-accredited university. most of the "administrative" users assumed it was a virus and panicked. then three more of the same came in this morning.

    i just wish windows would log things like the origin of said messages so the abuse could be addressed at its source.

  13. This is old hat... by Mysticalfruit · · Score: 5, Interesting

    If you've got a machine out on the internet and you've windows networking turned on, you've probably got bigger problems.

    A couple years ago, a co-worker of mine were at his house when he turned on windows networking and set his domain to "WORKGROUP" did the obligatory reboot suffle and started surfing all the shares in the area. It was hilarious, people had their entire C:\ drives shared, etc. Needless to say, after we got him setup with a firewall (linux/maq box) sure enough the logs just rolled with people trying to connect to ports 137/138/139. In one regard may ISP's block the netbios ports on their ingress and egress gateways.

    --
    Yes Francis, the world has gone crazy.
  14. Re:Least of your problems. by zulux · · Score: 5, Funny

    Close off ports 137 and 138 on any WAN connections. Of course, any competent windows network admin already knows this.

    I can't find a port setting on my NT Lan Manager - what are you talking about?

    Are you useing that TCP/IP thing? That's for hackers on the internet.

    You should be useing NetBEUI - now that's a stable protocall, made by the fine folks at Microsoft. Not one of those "Internet" (read: hacker) protocalls made by one of those unwashed UNIX people.

    I've heard the MSN is going to move to NetBEUI - so I know it's the network protocall of the future!

    If you can't use NetBEUI - at least give Banyan Vines a try. Works great with our Windows for Workgroups!

    Stay away from OS/2 - thats bad Mojo. Amiga people like OS/2 so I know it's bad.

    --

    Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

  15. Heh, we've been getting this.. by stratjakt · · Score: 5, Funny

    One of our gateway boxes is terribly insecure, and gets these pretty much every day now.

    It's usually selling "diplomas from prestigious non-accredited Universities, based on work experience. No testing or coursework required"

    I guess not locking down the box, they just assume we'd be stupid enough to fall for it.

    Every once in awhile I'll do a
    "NET SEND * ALL YOUR BASE ARE BELONG TO US"

    Noone here has a clue what it means or where it came from.

    --
    I don't need no instructions to know how to rock!!!!
  16. Re:Do yourself a favor - kill this service anyways by afidel · · Score: 5, Informative

    Sorry but I use remote registry service daily. If you want to do performance monitoring on a remote pc you need remote registry right because the perfdata is a section of the registry. It's also nice when you have a busted uninstaller and need to cleanup the registry before a reboot for a remote client, it's saved me a couple days worth of travel time this year alone! Whether it should have the default permissions that MS sets is another matter, but that is true for just about any MS default.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  17. Anyone remember Code Red? by ncc74656 · · Score: 5, Funny
    I configured Apache to pop up a window on an infected machine every time my server received an attempt at compromising it. It exploited the hole created by Code Red to pop up a message on the infected server. /default.ida used a server-side include to call Lynx with a URL that caused this command to execute on the infected server:

    net send localhost "Your webserver has been infected with the CodeRed2 worm. You have a security hole so big that you can drive a Mack truck through it. You should fix it before some script kiddie comes along and takes advantage of it. Remove root.exe and shell.exe from c:\inetpub\scripts (or wherever your CGI scripts live, though c:\inetpub\scripts is the default location)."

    Damn...if I had thought of it (and if I didn't think Internet advertising is evil), I could've made a mint off all of the lusers who let their servers get infected with Code Red! If I had figured out how to do something similar with Nimda, I could've made an even bigger killing!

    (Details of my adventures with Code Red are up here. The live counter is gone now because my rusty SQL skillz resulted in MySQL thrashing away for more than a minute to generate four numbers.)

    --
    20 January 2017: the End of an Error.
  18. Re:Least of your problems. by nuxx · · Score: 5, Informative

    Actually, if you really want to keep people out of your file & printer sharing stuff on a home network, using NetBEUI is a good idea. It's lightweight, fast, and it works just fine. Use IP for your internet stuff, NetBEUI for file & printer sharing.

    Works like a charm and doesn't require any extra software. Hell, you could have the cable modem company's favorate version of multiple machines on a cable modem (modem with multiple IP service plus the client machines all plugged into one hub) using this and you'll still be safe.

  19. XWindows? by Vic · · Score: 5, Informative

    I am glad that I don't have to worry about it here, XWindows baby.

    If anything, a poorly configured X server would be even MORE annoying. If you let anyone attach to your X session remotely, they could display pretty much anything on your screen, not just annoying pop-up messages.

    I love X, but you have to be careful with it too.

    Cheers,
    Vic

  20. Re:Simple fix... by TheTomcat · · Score: 5, Funny

    So what's next? Spam on my HP Printer [digitaltrust.it]?

    I've sent messages to random printers before. Back in the days before Napster, there was a P2Pish search engine that scoured the net for open SMB shares. People would often share their whole C drive (retardedly), but the most fun was to send messages like "I'm running out of ink. I'm running out of ink. I'm running out of ink. I'm running out of ink. (etc)" or "You should reall secure your machine.." to remote printers shared to the world over SMB.

    S

  21. Here it is again... by Da+VinMan · · Score: 5, Informative

    This is from my previous post at http://slashdot.org/comments.pl?sid=42016&cid=4432 394

    Note, I'm not karma whoring, I could care less.

    --

    (You will have to graduate from newbie status in order to take advantage of my advice. This means that you will have to climb the learning curve and actually go read some stuff. You can spend a chunk of cash on products to avoid doing just that, but that's much less fun.)

    If you're doing things like turning on file sharing or sharing printers, it's (supposedly) very easy to hack you. I say supposedly only because I haven't actually tried this. It's such an infamous hole though that I do believe it. To turn this off, unbind the NetBIOS protocol from the modem/network card that connects you to the Internet. In Windows 2000, that you means you go to the Properties for your network connection (in the Control Panel) and uncheck the 'File and Printer Sharing for Microsoft Networks' option. (It's very easy to fix this in Win9x too using roughly the same technique.) You may have to reboot, I don't recall. That problem will then be solved.

    Now to protect yourself from other intrusions and threats.

    If you're just running a dial-up connection and don't leave your machine on the network for extended periods of time, then a product like ZoneAlarm (www.zonelabs.com - look for the free version) will serve you well. Actually, it serves you well in two ways: 1) it protects your machine from the outside world coming into your machine in an unauthorized fashion and 2) it protects adware on your machine from phoning home without your permission (actually it prevents everything from using the Internet until you grant permission, not just adware). This is sufficient for dialup.

    For broadband users and users who want to leave their machine on the Internet for extended periods of time (more than a couple hours at a time), I recommend using an honest to goodness separate firewall. There is a lot that can be said about this, far more than I know really, but I well give you a couple pointers.

    First of all, one of your options is to use a second PC as the firewall. It will need to have 2 network cards, you will need a router or hub for your home LAN, and you will have to get the cable modem (or DSL for that matter; with which I have no experience - shouldn't be too hard) working with that extra PC (via Windows would be easiest to start with). Once that's setup, go grab a Linux distribution like IPCop (or SmoothWall - they're very similar, in fact they were the same product at one time), and install it on that PC. It will require that you reformat the hard drive, so don't plan on storing any files on it. A small hard drive is sufficient. There are FAQs and forums on the IPCop and SmoothWall sites that will help get you setup.

    Your second option in the category of 'real protection' (for home users anyway) is to just go buy a hardware firewall. So instead of a second PC, you just go buy a device that does essentially the same thing. I won't go into detail on these as I have no experience with them. I just thought you should know about them.

    Two last points:
    -PLEASE keep a current anti-virus product actively running on your machine and keep it up to date. If you need a free one, go to http://www.grisoft.com to get the free personal version of the AVG anti-virus product. This one has saved my butt several times from several infections. It may or may not be the best product out there, but it works for me.

    -To protect yourself from browser window popups and other shenanigans, go grab WebWasher at http://www.webwasher.com/en/products/wwash/downloa d_license.htm. You will occasionally find that it interferese with pages that make heavy use of Javascript, but you can turn it off when needed. The added protection from annoying web sites is worth the small inconvenience it may sometimes cause.

    As always, this advice is just a starting point. Today's perfect security solution may be an open door tomorrow. It's up to you to keep yourself informed and to take action when problems arise.

    Good luck and have fun!

    --
    Please mod this post only if you think others should/n't read this. I have enough ego^H^H^Hkarma. Thanks!
  22. Does anyone here actually understand TCP/IP? by Nintendork · · Score: 5, Informative
    You can't just close off a port. You have to close off the correct port number for the correct protocol.

    A lot of "Paper MCSEs" understand this because the networking exam covers the OSI model. The same thing goes for those "Paper CCNAs".

    Here's how it works. When I do a net send "Message", the following occurs. Once the data portion of the net send information is formatted by the appropriate layers, it's handed down to the protocol layer and wrapped in a UDP header with a port number. UDP is the protocol responsible for maintaining a communication session between hosts. The port number is like an apartment number in a street address. A lot of services have to talk using the UDP protocol, so it's divided into port numbers (As an FYI, the same is done for TCP). This in turn is handed down to the network layer where it will get a source and destination address stamp (The IP addresses). That in turn is handed down to the data link layer which stamps on the source and destination MAC addresses (Your computer and the default gateway). From there, it hits the physical layer and is on the wire. Along the way, the data link layer changes every hop that is made because the MAC addresses involved change at each router hop. Once it gets to the destination IP address, the recipient strips off the layers to reveal the data. It knows to hand that data up to the NetBIOS services because they're the ones listening on UDP port 138. Finally, you get a little window trying to sell pr0n. Here's a picture that shows the different layers of a TCP packet and their function.

    Here's a rundown on NetBIOS port usage.

    UDP port 137 is used for NetBIOS name resolution.

    UDP port 138 is used for browsing, domain authentication, and datagrams (This is what the messenger service uses).

    TCP port 139 is used for the actual session. This is what you transfer files through.

    TCP port 135 is the RPC service. Some people often confuse it with the NetBIOS ports. I don't know why.

    So, technically, you'll want to block UDP ports 137 and 138 and TCP port 139. Unfortunately, a lot of home equipment is geared towards the novice and they don't separate the UDP and TCP protocols. You are forced to block both TCP and UDP for any given port number. Because of this, you end up blocking more than is required.

    For those interested in this brief tutorial, I highly encourage you to get a CCNA study guide even if you're not going to get the certification. Lots of valuable networking info.

    Lucas
    MCSE, CCNA, Ex-Microsoft NT Networking and Security Support Rep

    1. Re:Does anyone here actually understand TCP/IP? by AKnightCowboy · · Score: 5, Insightful
      You are forced to block both TCP and UDP for any given port number. Because of this, you end up blocking more than is required.

      And the problem with this is what exactly? Your firewall should block everything unless you specifically exempt it. Only people living in 1994 are still trying to play the "I'll just block dangerous ports" whack-a-mole game with their firewalls. Any el-cheapo home Linksys box will block all inbound connections by default. There isn't any reason to be using NetBIOS across the Internet period. It's a horribly insecure protocol that was never designed to be used across a WAN. Keep it on the intranet where it is meant to be used.

  23. another way to stop this spam by Jeriki · · Score: 5, Informative

    open up the advanced tab of you TCP/IP settings and goto the WINS tab and click 'disable NetBIOS over TCP/IP' and then 'OK'.

    --
    -witty .sig