msblast.exe ---> worm/virus?
Tuesday, August 12, 2003 by Cross1492 | Discussion: WinCustomize Talk
According to my ISP the problem is a vulnerability in Windows OS/possible worm. Microsoft is supposed to be working on a fix.
So BEWARE! The Trivial Transfer Protocol is being used to send this file/worm. To check if this file is on your system restart in safe mode, delete the file msblast.exe (Windows/system32), and open msconfig to uncheck the startup of this file. Block Trivial Transfer (tftp.exe) in your firewall as well.
I hope this helps anyone who is having this problem. If anyone else has a better fix please post it here!
Reply #2 Tuesday, August 12, 2003 9:54 AM
http://vil.nai.com/vil/stinger/
Reply #3 Tuesday, August 12, 2003 10:17 AM
Reply #4 Tuesday, August 12, 2003 11:05 AM

Reply #5 Tuesday, August 12, 2003 11:33 AM
If you're sick of windows, get a mac, or at least get linux. ANYTHING is better than an OS ripped from an OS which was ripped from Xerox, of all people.

Reply #6 Tuesday, August 12, 2003 11:49 AM
macrobaye, please keep your comments constructive and on topic. Please also remember that this site is populated by Windows users who are discussing windows issues and are trying to help each other.
There is also another reason why you don't see viruses for other OSs: the people who program viruses/worms/etc. like to hit a large market. The 5% market share that Mac has and the 1% that Linux has just isn't worth the effort 
This worm is a real pain. Not hard to get rid of, so I hope everyone is zapping it!
Reply #7 Tuesday, August 12, 2003 12:11 PM
ZoneAlarm blocked traffic to port 135 on your machine from port 3441 on a remote computer. This communication attempt may have been a port scan, or simply one of the millions of unsolicited commercial or network control messages that are routinely sent out over the Internet. Such unsolicited messages are often called Internet background noise.
The above is only one of many targeting port 135, I had 138 yesterday and today in a 2 hour period 76 hits.
>

Reply #8 Tuesday, August 12, 2003 12:12 PM
Apple and Linux have never had problems, because those OS's don't have the bugs that Windows does. Microsoft only released XP when they did because they were threatened by Mac OSX and it's obvious advantages of 2000 (and now still over XP). Microsoft needs to stop releasing BETA software and calling it a fully developed version.
GOD! I hope they don't mess up with Longhorn. But knowing Microsoft's history of moronic security holes and bugs, they will.
Anyone remember the Passport bug? Oh yeah, that one. The one where a hacker could steal a Windows (AND mac, linux) user's personal and sensitive information, effectively stealing their identity? Bill Gates needs to wake up from his dream.
As MSBLASTER.exe says: Billy Gates, why do you make this possible? Stop making money and fix your software!!!
It is now believed (and factually backed up) that a Mac user created the bug!
Reply #9 Tuesday, August 12, 2003 1:20 PM

Reply #10 Tuesday, August 12, 2003 1:28 PM
White Moth: yes, there had been an increase in Port 135 scans for weeks and speculation was that some of the stuff that was seen may have been reconnoitering or a testing phase for a release of an exploit. Reportedly there was an IRC bot release at least similar to (if not the same as) msblaster before msblaster started propagating through the net via ports. At least 3 variants of msblaster were identified yesterday by people running honeypots.
Symantec has a free removal tool here and there are also inro for those who may wish to see what the worm does and instructionf for those who may wish to remove it manually: http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm.html

Reply #11 Tuesday, August 12, 2003 2:34 PM
| #9 by Developer wombat_1 - 8/12/2003 1:20:31 PM This particular little nasty has already been dealt with by Nortons update, 12.08.2003. |
They were late with this one because I run Norton, it failed to stop the worm ... the update was late and I had to get rid of it manually.
Norton allowed my port to be probed.

Reply #12 Tuesday, August 12, 2003 3:13 PM
Reply #13 Tuesday, August 12, 2003 3:31 PM
Reply #14 Tuesday, August 12, 2003 3:39 PM
Reply #15 Tuesday, August 12, 2003 3:51 PM
The Security Update (823980) solved the problem.
macro, instead of 'complaining' about what you hate about MS OS in this site, shouldnt you be writing to Bill Gates about this issues?
And always remember, no matter how hack-proff they make a system, there is always someone out there that eventually is gonna find a way to hack it.
Reply #16 Tuesday, August 12, 2003 4:20 PM
Kona: Please no personal attacks. If you can sit there and say that you're not annoyed by all the BS you've had to put up with as a Windows user, you will now become the most tolerant person I know. So please, I wasn't attacking any of you, nor did I make any distasteful or improper comments. So please mind your manners. There's no reason to get mad at me over a few comments made on a public message boad.
Reply #17 Tuesday, August 12, 2003 4:21 PM
Reply #18 Tuesday, August 12, 2003 4:23 PM
Reply #19 Tuesday, August 12, 2003 4:33 PM

Reply #20 Tuesday, August 12, 2003 4:35 PM
macrobaye...this is not a 'bash Microsoft' thread....it is a virus notification thread.
If you wish to bash anything, start a thread as its topic and allow this one to serve its purpose.
Thankyou.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #1 Tuesday, August 12, 2003 9:52 AM
https://www.wincustomize.com/msgboard.asp?BID=WC&id=176083
It started really spreading around this morning/last night.
You can protect yourself against it by getting the windows update critical update Q331953 or by blocking port 135 on your computer.