Vundo just won't die!

Please see the following for the empty logs:
Using ShowNew
Using GetRunKey
Note the possible errors and their fixes.

Now:
Run HijackThis (select Do a system scan only) and select the following lines but DO NOT CLICK FIX until you exit all browser sessions including the one you are reading in right now:

After clicking Fix, exit HJT.

Now download The Avenger by Swandog469, and save it to your Desktop.

* Extract avenger.exe from the Zip file and save it to your desktop
* Run avenger.exe by double-clicking on it.
* Check the 'Input script manually' box.
* Click on the magnifying glass icon.
* Copy everything in the Quote box below, and paste it in the box that opens:

* Now click the 'Done' button.
* Click on the traffic light icon and OK the prompt.
* You will be prompted to restart, OK the prompt and your PC should reboot, if not, reboot it yourself.
* A log file from Avenger will be produced at C:\avenger.txt
Attach new logs for:
ShowNew
GetRunKeys
HJT
Avenger

 

Re-run HJT and have it fix this item:
O20 - Winlogon Notify: winwim32 - winwim32.dll (file missing)



Download the attached GetRunKeys.zip file into the same folder as you downloaded them before. Extract the GetRunKey.bat file from the ZIP file into that same folder thus overwriting the current version that is there.

Now run the GetRunKeys.bat file by double clicking on it. Then attach the newGetRUnKeys.txtfile that will be created by running this.
Attached Files http://forums.majorgeeks.com/images/attach/zip.gif GetRunKey.zip (11.2 KB, 2 views)

 

Uninstall the tools (ShowNew. GetRunKeys, HJT) ....then download this: Using MGtools

 

Right click the folders and choose delete ..... I think we have some of the major stuff handled but I want to see those two logs.

 

Did you double click the exe file to get it to run?

 

Did you turn off Teatimer as directed in the Read and Run FIrst? It very well could be stopping the scans......and it is probably in your system 32 files as well as your reg keys that we need to see and remove....

 

It seems like your PC could be having a problem with a couple of built in DOS commands that are part of Windows. It could be having an issue with the one of the below two commands:

ver
find

Or it could be having an issue with what is referred to a the "pipe" command. A "pipe" is when the about of one command is forwarded to another command. This is what GetLogs.bat, GetRunKey.bat and ShowNew.bat all make use of when the check for the Windows version and then "pipe" the output to a "find" command to match a particular string. This string will tell us the Windows version. Try the below.

Click Start, Run, and enter cmd and click OK. This will open a command prompt. Enter the below commands in bold black at the command prompt and follow each by the enter key. I give you in bold purple what the output from the command should be.

ver
Microsoft Windows XP [Version 5.1.2600]

find
FIND: Parameter format not correct


Are those two purple lines what you get?


Also download the attached OStest.zip file and extract the Ostest.bat file from it. You can put it anywhere but I suggest you put it into the C:\MGtools folder if it exists. Then run the Ostest.bat file and tell me what you get for output. If is works properly, you should see something like below in the command prompt window:

Code:

Your Windows OS is Windows XP
 
write down what you see for your OS before hitting a key.
Press any key to continue . . . 

 

It just confirms my suspicion about where the problem lies. Your PC cannot do pipes (also called redirection - which you can read about here: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/redirection.mspx?mfr=true ) for some reason. This is problem within the Windows OS. This is not a malware related issue as far as I know and at this time I have no idea what a possible fix for it would be. The OStest.bat file is a very simple batch file that should easily run on all Windows PCs. There is nothing very complex in it.

 

Because you probably never run any DOS type commands like this.

I doubt it.

This does not come from running ostest.bat. This comes from just opening the command prompt window.

I wonder if it is saying it cannot find ostest.bat or if that message is due to when it tries to run something in the batch file. Try running this modfied version that I named OsTest2.bat that is in the attached ZIP file. Do you still get the same output? Are you sure you put ostest.bat and ostest2.bat into the C:\MGtools folder? Did you extract them from the ZIP file? Do the below at the command prompt while you are in the MGtools folder.

dir > c:\filelist.txt


Attach the c:\filelist.txt file to your next message.

I have no idea at this point. I'm not sure what the exact cause is. All I can tell is that it looks like you cannot use the pipe form of redirection.

Your malware is gone! We are just trying to figure out why you cannot run batch files properly.

 

No problem! No offense was taken.

Again this double confirms my suspicion. The OStest.bat file is failing as soon as it gets to the below lines:

This is the first test in a series to determine the Window OS version. You are failing on the ver | find "Windows 2000">NUL which is the pipe command that I have been referring to.

If you enter the below at the command prompt, what happens.

ver | find "Windows XP"

 

Yes from the command prompt, but maybe not from within a batch file.

What happens if you enter the below from a command prompt:

ver | find "Windows XP" > nul


Do you just get a prompt back with no output? That is what should happen.

 

Run the OStest3.bat file from the command prompt after extracting it from the attached ZIP file


What do get?

 

Yes John it does and thanks for helping us work thru this to determine what is really going on. Based on this last result form Ostest3.bat, it would seem that the problem is not really in the pipe form of redirection. The problem is in the redirection of standard output to a particular filename. On your PC (and not on literally thousands of others) the system does not understand the nul filename. Each test for Windows OS version redirects the standard output to a nul file by using the > nul at the end of the line. This was evident in the line I had you run:

ver | find "Windows XP" > nul

This is supposed just prevent the normal out from the ver | find "Windows XP" command from being seen when you don't want it to be seen (usually because it is not necessary and/or could cause confusion ). So this problem is fairly unique to your PC. I say fairly because thinking back, we may have run into a couple other cases overtime where a problem like this occurred but we were not able to work thru the details with the user to find out why. Which I again thank you for helping us to work this out.

I can now give you a modified version of MGtools.exe to download that I want you to try running. Just download from this blue line to your C:\ folder and then double click on the MGtools.exe file to begin the installation and automatic running of all the scans. If this runs properly, you should end up with text like below on the last 7 lines in the command prompt window.

Then attach the C:\MGlogs.zip that should result if all works well.

 

Yes it is very helpful to us when we can get a user like yourself to work thru and find a solution to making our tools run better. We cannot debug a problem that we cannot create. Thus getting you to run steps to help us find the problem is the only way we can get to the bottom of the issue. Once I determined where the problem was actually coming from, I modified our tools to work around the issue that seems to exist on your PC (and maybe a few others we have seen). So it is sometimes a two way street where you can help us to help you better. Thanks again! And the new tools were already officially posted since I was sure that this would work.

Not quite clean! We have some left overs from Vundo and Winlogonhook to cleanup and a few performance related things to remove with HijackThis.


Run C:\MGtools\analyse.exe by double clicking on it. This is really HijackThis (select Do a system scan only) and select the following lines but DO NOT CLICK FIX until you exit all browser sessions including the one you are reading in right now:

O3 - Toolbar: (no name) - {8B68564D-53FD-4293-B80C-993A9F3988EE} - (no file)
O4 - HKLM\..\Run: [QuickTime Task] "C:\Program Files\QuickTime\QTTask.exe" -atboottime
O4 - HKLM\..\Run: [SunJavaUpdateSched] "C:\Program Files\Java\jre1.6.0_03\bin\jusched.exe"

After clicking Fix, exit HJT.

Copy the bold text below to notepad. Save it as fixme.reg to your desktop. Be sure the "Save as" type is set to "all files" Once you have saved it
double click it and allow it to merge with the registry.

Now download The Avenger by Swandog46, and save it to your Desktop.

• Extract avenger.exe from the Zip file and save it to your desktop
• Run avenger.exe by double-clicking on it.
• Check the 'Input script manually' box.
• Click on the magnifying glass icon.
• Copy everything in the Quote box below, and paste it in the box that opens:

• Now click the 'Done' button.
• Click on the traffic light icon and OK the prompt.
• You will be prompted to restart, OK the prompt and your PC should reboot, if not, reboot it yourself.
• A log file from Avenger will be produced at C:\avenger.txt

Please download ATF Cleaner by Atribune. This program does not require an installation. The executable actually runs the program.

NOTE: This program is for Windows XP and Windows 2000 only. ATF Cleaner will remove all files from the items that are checked so if you have some cookies you'd like to save. Please move them to a different directory first.

• Double-click ATF-Cleaner.exe to run the program.
• Under Main choose: Select All
• Click the Empty Selected button.

If you use Firefox browser

• Click Firefox at the top and choose: Select All
• Click the Empty Selected button.
  • NOTE: If you would like to keep your saved passwords, please click No at the prompt.

If you use Opera browser

• Click Opera at the top and choose: Select All
• Click the Empty Selected button.
  • NOTE: If you would like to keep your saved passwords, please click No at the prompt.

Click Exit on the Main ATF Cleaner menu to close the program.

Now run the C:\MGtools\GetLogs.bat file by double clicking on it. Then attach the new C:\MGlogs.zip file that will be created by running this and also attach the log from Avenger.

Make sure you tell me how things are working now!

 

You're welcome John!

Empty your browser cache and then click refresh a couple of times. That usually fixes this. Let us know.


Flusing the Internet Explorer Cache

1. Run Internet Explorer
2. Click Tools and select Internet Options
3. Now on the General tab, click Delete Files and select Delete all Offline content too on the next window, Click OK. When it finishes Click OK.

 

Apparently ATF-cleaner and also CCleaner are not emptying your temp folders for some reason as I can see in your newfiles.txt log. Please goto each of the below two folders and manually delete everything in those folders. Windows will block you from deleting a couple of files from the current date. The first folder has over 1000 files in it and all those winxx.tmp files are from Winlogonhook.

C:\WINDOWS\Temp\
C:\Documents and Settings\John\Local Settings\Temp

Other than the above needing to be emptied, you are clean and I will repeat finally procedures below even though you have already done some of them. You do need to repeat the removal of unnecessary files and also toggling System Restore.


Also I'm curious. Are you a friend of David's? I refer to the below in your HJT log.
O24 - Desktop Component 0: (no name) - http://www.davidparry.co.uk/images/bg8.jpg



If you are not having any other malware problems, it is time to do our final steps:

1. If we used Pocket Killbox during your cleanup, do the below
   • Run Pocket Killbox and select File, Cleanup, Delete All Backups
2. If we used ComboFix, you can delete the ComboFix.exe file, C:\ComboFix folder, C:\QooBox folder, C:\WINDOWS\nircmd.exe, C:\combofix.txt and C:\ComboFix-quarantined-files.txt logs that was created.
3. If we user SDFix you can delete all the SDFix related files and folders from your Desktop or whereever you installed it.
4. If we used SmitFraudFix, you can delete all files and folders related to it now including the c:\rapport.txt log.
5. If we used VundoFix, you can delete the VundoFix.exe file and the C:\VundoFix Backups folder and C:\vundofix.txt log that was created.
6. If we had your run FixWareOut, you can delete the Fixwareout.exe file and the C:\fixwareout folder.
7. If we had you run Avenger, you can delete all files related to Avenger now.
8. If we had you download any registry patches like fixme.reg or fixWLK.reg (or any others), you can delete these files now.
9. You can delete the C:\MGtools folder and the C:\MGtools.exe file. You can also delete the C:\MGlogs.zip
10. If you are running Windows XP or Windows ME, do the below:
    • go back to step 8 of the READ & RUN ME to Disable System Restore which will flush your Restore Points.
    • Then reboot and Enable System Restore to create a new clean Restore Point.
11. After doing the above, you should work thru the below link:
    • How to Protect yourself from malware!

 

Yes that was part of what I gave you in my last message. Notice step 10?

No not famous. It just matches the name of someone I know in England. And I was curious. You can fix those lines as they are not important nor are they malware.

You're welcome and thank you again too for helping us improve our tools.

 

Yes that would be the easiest way to remove that.

Never! You're welcome.