Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Security Tool


  • This topic is locked This topic is locked
11 replies to this topic

#1 madman666

madman666

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Selah, WA
  • Local time:11:45 PM

Posted 03 April 2010 - 12:58 AM

Tried a manual removal of the security tool virus. essentially renamed the file and deleted it's folder. part of the process was running a program named rkill. After running that program security tool stopped popping up but none of my programs will run. i'm not sure if this is damage left over from the virus or it it was the rkill program. either way i can't run anything and i was wondering if anyone could help me get my computer back to working condition.

i am running windows xp pro on a netbook if that helps.

Edited by Budapest, 03 April 2010 - 01:06 AM.
Moved from Virus, Trojan, Spyware, and Malware Removal Logs


BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:45 AM

Posted 03 April 2010 - 10:37 AM

Try this then do the Tutorial again. Post the scan log when completed. It's the malware not rkill/.

Click on Start, Then Control Panel
Click on Users
Create a new user account with Administrative Rights
Login as that user
Now run MBAM (MalwareBytes below) ,, Run a FULL scan this will search all user accounts on your machine.
Reboot your machine.
When your machine is at the login don't login into the infected account log into the new account you made.
Logout of the new account once the machine finishes booting up.
Log into your original account that was infected. Post the MBAM log.
Hopefully we are good.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#3 madman666

madman666
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Selah, WA
  • Local time:11:45 PM

Posted 03 April 2010 - 12:39 PM

when i try yo run windows normally the login screen doesnt load. i can login when i go into safe mode. i created a new account out of the administrator account and while still in safe mode i went into the new account. i installed mbam but i can't get it to run. i get an error code that says it is unable to execute the exe file. there are some suspicious processes running. two or more instances of IEXPLORE.EXE and i am thinking this is a virus that was let in from the original infection and it might be stopping me from finishing the clean up of the original infection. also the keyboard isnt working if that tells you anything.

*****edit**** ok i went back to the tutorial you have on this site and followed the instructions for downloading the mbam exe and launching it that way. the program is now running a full scan. i will post the results.

Edited by madman666, 03 April 2010 - 12:45 PM.


#4 madman666

madman666
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Selah, WA
  • Local time:11:45 PM

Posted 03 April 2010 - 10:28 PM

ok the first scan found like 78 viruses and seemed to have removed them. there is no longer multiple instances of IEXPLORE.EXE running. I restored the host files as in the guide and deleted the new account. programs are working again. things can update and install. I've now got mbam, ad-aware, and Microsoft security essentials running. but mbam keeps finding two or three viruses with each scan. it says it removes it but a little bit later it'll find something again. also there are a few processes that it tries to quarantine on start up and shut down but the logs show that it is unsuccessful do to error code 2.

the processes it fails to quarantine are located in C:\windows\system32\warihagi.dll (trojan.vundo), C:\windows\system32\_voidympaxjsapq.dll (rootkit.tdss), C:\windows\system32\_voidqowjaflfk.dll (rootkit.tdss) and i keep getting ip blocks to the same two ip's even when not using any browsers.

i am currently running a full system scan with ad-aware and i will post results.

#5 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:45 AM

Posted 03 April 2010 - 11:14 PM

Ok yes please the logs are how we know where to go next.
  • Go to this page and Download TDSSKiller.zip to your Desktop.
  • Extract its contents to your desktop and drag TDSSKiller.exe on the desktop, not in the folder.
  • Vista Start logo >All Programs> Accessories> RIGHT-click on Command Prompt and Select Run As Administrator. Copy/paste the following bolded command and hit Enter.

    "%userprofile%\Desktop\TDSSKiller.exe" -l C:\TDSSKiller.txt -v
  • If TDSSKiller alerts you that the system needs to reboot, please consent.
  • When done, a log file should be created on your C: drive named "TDSSKiller.txt" please copy and paste the contents in your next reply.
Rerun MBAM (MalwareBytes) like this: Well you are running this..............

Open MBAM in normal mode and click Update tab, select Check for Updates,when done
click Scanner tab,select Quick scan and scan (normal mode).
After scan click Remove Selected, Post new scan log and Reboot into normal mode.


Next run ATF and SAS: If you cannot access Safe Mode,run in normal ,but let me know.

Note: On Vista, "Windows Temp" is disabled. To empty "Windows Temp" ATF-Cleaner must be "Run as an Administrator".

From your regular user account..
Download Attribune's ATF Cleaner and then SUPERAntiSpyware , Free Home Version. Save both to desktop ..
DO NOT run yet.
Open SUPER from icon and install and Update it
Under Scanner Options make sure the following are checked (leave all others unchecked):
Close browsers before scanning.
Scan for tracking cookies.
Terminate memory threats before quarantining
.
Click the "Close" button to leave the control center screen and exit the program. DO NOT run yet.

Now reboot into Safe Mode: How to enter safe mode(XP)
Using the F8 Method
Restart your computer.
When the machine first starts again it will generally list some equipment that is installed in your machine, amount of memory, hard drives installed etc. At this point you should gently tap the F8 key repeatedly until you are presented with a Windows XP Advanced Options menu.
Select the option for Safe Mode using the arrow keys.
Then press enter on your keyboard to boot into Safe Mode
.

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

If you use Firefox or Opera browser click that browser at the top and choose: Select All
Click the Empty Selected button.
If you would like to keep your saved passwords, please click No at the prompt.
Click Exit on the Main menu to close the program
.

NOW Scan with SUPER
Open from the desktop icon or the program Files list
On the left, make sure you check C:\Fixed Drive.
Perform a Complete scan. After scan,Verify they are all checked.
Click OK on the summary screen to quarantine all found items.
If asked if you want to reboot, click "Yes" and reboot normally.

To retrieve the removal information after reboot, launch SUPERAntispyware again.
Click Preferences, then click the Statistics/Logs tab.
Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
If there are several logs, click the current dated log and press View log.
A text file will open in your default text editor.
Please copy and paste the Scan Log results in your next reply.
Click Close to exit the program.


Please ask any needed questions,post logs and Let us know how the PC is running now.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#6 madman666

madman666
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Selah, WA
  • Local time:11:45 PM

Posted 04 April 2010 - 02:35 PM

12:26:30:843 3412 TDSS rootkit removing tool 2.2.8.1 Mar 22 2010 10:43:04
12:26:30:843 3412 ================================================================================
12:26:30:843 3412 SystemInfo:

12:26:30:843 3412 OS Version: 5.1.2600 ServicePack: 3.0
12:26:30:843 3412 Product type: Workstation
12:26:30:843 3412 ComputerName: HOME-8B9CC4D22D
12:26:30:843 3412 UserName: Mike
12:26:30:843 3412 Windows directory: C:\WINDOWS
12:26:30:843 3412 Processor architecture: Intel x86
12:26:30:843 3412 Number of processors: 2
12:26:30:843 3412 Page size: 0x1000
12:26:30:859 3412 Boot type: Normal boot
12:26:30:859 3412 ================================================================================
12:26:30:859 3412 UnloadDriverW: NtUnloadDriver error 2
12:26:30:859 3412 ForceUnloadDriverW: UnloadDriverW(klmd21) error 2
12:26:31:062 3412 wfopen_ex: Trying to open file C:\WINDOWS\system32\config\system
12:26:31:062 3412 wfopen_ex: MyNtCreateFileW error 32 (C0000043)
12:26:31:062 3412 wfopen_ex: Trying to KLMD file open
12:26:31:062 3412 wfopen_ex: File opened ok (Flags 2)
12:26:31:062 3412 wfopen_ex: Trying to open file C:\WINDOWS\system32\config\software
12:26:31:062 3412 wfopen_ex: MyNtCreateFileW error 32 (C0000043)
12:26:31:062 3412 wfopen_ex: Trying to KLMD file open
12:26:31:062 3412 wfopen_ex: File opened ok (Flags 2)
12:26:31:062 3412 Initialize success
12:26:31:062 3412
12:26:31:062 3412 Scanning Services ...
12:26:31:218 3412 Raw services enum returned 330 services
12:26:31:250 3412
12:26:31:250 3412 Scanning Kernel memory ...
12:26:31:250 3412 Devices to scan: 4
12:26:31:250 3412
12:26:31:250 3412 Driver Name: Disk
12:26:31:250 3412 IRP_MJ_CREATE : F75E2BB0
12:26:31:250 3412 IRP_MJ_CREATE_NAMED_PIPE : 804F4562
12:26:31:250 3412 IRP_MJ_CLOSE : F75E2BB0
12:26:31:250 3412 IRP_MJ_READ : F75DCD1F
12:26:31:250 3412 IRP_MJ_WRITE : F75DCD1F
12:26:31:250 3412 IRP_MJ_QUERY_INFORMATION : 804F4562
12:26:31:250 3412 IRP_MJ_SET_INFORMATION : 804F4562
12:26:31:250 3412 IRP_MJ_QUERY_EA : 804F4562
12:26:31:250 3412 IRP_MJ_SET_EA : 804F4562
12:26:31:250 3412 IRP_MJ_FLUSH_BUFFERS : F75DD2E2
12:26:31:250 3412 IRP_MJ_QUERY_VOLUME_INFORMATION : 804F4562
12:26:31:250 3412 IRP_MJ_SET_VOLUME_INFORMATION : 804F4562
12:26:31:250 3412 IRP_MJ_DIRECTORY_CONTROL : 804F4562
12:26:31:250 3412 IRP_MJ_FILE_SYSTEM_CONTROL : 804F4562
12:26:31:250 3412 IRP_MJ_DEVICE_CONTROL : F75DD3BB
12:26:31:250 3412 IRP_MJ_INTERNAL_DEVICE_CONTROL : F75E0F28
12:26:31:250 3412 IRP_MJ_SHUTDOWN : F75DD2E2
12:26:31:250 3412 IRP_MJ_LOCK_CONTROL : 804F4562
12:26:31:250 3412 IRP_MJ_CLEANUP : 804F4562
12:26:31:250 3412 IRP_MJ_CREATE_MAILSLOT : 804F4562
12:26:31:250 3412 IRP_MJ_QUERY_SECURITY : 804F4562
12:26:31:250 3412 IRP_MJ_SET_SECURITY : 804F4562
12:26:31:250 3412 IRP_MJ_POWER : F75DEC82
12:26:31:250 3412 IRP_MJ_SYSTEM_CONTROL : F75E399E
12:26:31:250 3412 IRP_MJ_DEVICE_CHANGE : 804F4562
12:26:31:250 3412 IRP_MJ_QUERY_QUOTA : 804F4562
12:26:31:250 3412 IRP_MJ_SET_QUOTA : 804F4562
12:26:31:281 3412 C:\WINDOWS\system32\DRIVERS\disk.sys - Verdict: 1
12:26:31:281 3412
12:26:31:281 3412 Driver Name: Disk
12:26:31:281 3412 IRP_MJ_CREATE : F75E2BB0
12:26:31:281 3412 IRP_MJ_CREATE_NAMED_PIPE : 804F4562
12:26:31:281 3412 IRP_MJ_CLOSE : F75E2BB0
12:26:31:281 3412 IRP_MJ_READ : F75DCD1F
12:26:31:281 3412 IRP_MJ_WRITE : F75DCD1F
12:26:31:281 3412 IRP_MJ_QUERY_INFORMATION : 804F4562
12:26:31:281 3412 IRP_MJ_SET_INFORMATION : 804F4562
12:26:31:281 3412 IRP_MJ_QUERY_EA : 804F4562
12:26:31:281 3412 IRP_MJ_SET_EA : 804F4562
12:26:31:281 3412 IRP_MJ_FLUSH_BUFFERS : F75DD2E2
12:26:31:281 3412 IRP_MJ_QUERY_VOLUME_INFORMATION : 804F4562
12:26:31:281 3412 IRP_MJ_SET_VOLUME_INFORMATION : 804F4562
12:26:31:281 3412 IRP_MJ_DIRECTORY_CONTROL : 804F4562
12:26:31:281 3412 IRP_MJ_FILE_SYSTEM_CONTROL : 804F4562
12:26:31:281 3412 IRP_MJ_DEVICE_CONTROL : F75DD3BB
12:26:31:281 3412 IRP_MJ_INTERNAL_DEVICE_CONTROL : F75E0F28
12:26:31:281 3412 IRP_MJ_SHUTDOWN : F75DD2E2
12:26:31:281 3412 IRP_MJ_LOCK_CONTROL : 804F4562
12:26:31:281 3412 IRP_MJ_CLEANUP : 804F4562
12:26:31:281 3412 IRP_MJ_CREATE_MAILSLOT : 804F4562
12:26:31:281 3412 IRP_MJ_QUERY_SECURITY : 804F4562
12:26:31:281 3412 IRP_MJ_SET_SECURITY : 804F4562
12:26:31:281 3412 IRP_MJ_POWER : F75DEC82
12:26:31:281 3412 IRP_MJ_SYSTEM_CONTROL : F75E399E
12:26:31:281 3412 IRP_MJ_DEVICE_CHANGE : 804F4562
12:26:31:281 3412 IRP_MJ_QUERY_QUOTA : 804F4562
12:26:31:281 3412 IRP_MJ_SET_QUOTA : 804F4562
12:26:31:296 3412 C:\WINDOWS\system32\DRIVERS\disk.sys - Verdict: 1
12:26:31:296 3412
12:26:31:296 3412 Driver Name: Disk
12:26:31:296 3412 IRP_MJ_CREATE : F75E2BB0
12:26:31:296 3412 IRP_MJ_CREATE_NAMED_PIPE : 804F4562
12:26:31:296 3412 IRP_MJ_CLOSE : F75E2BB0
12:26:31:296 3412 IRP_MJ_READ : F75DCD1F
12:26:31:296 3412 IRP_MJ_WRITE : F75DCD1F
12:26:31:296 3412 IRP_MJ_QUERY_INFORMATION : 804F4562
12:26:31:296 3412 IRP_MJ_SET_INFORMATION : 804F4562
12:26:31:296 3412 IRP_MJ_QUERY_EA : 804F4562
12:26:31:296 3412 IRP_MJ_SET_EA : 804F4562
12:26:31:296 3412 IRP_MJ_FLUSH_BUFFERS : F75DD2E2
12:26:31:296 3412 IRP_MJ_QUERY_VOLUME_INFORMATION : 804F4562
12:26:31:296 3412 IRP_MJ_SET_VOLUME_INFORMATION : 804F4562
12:26:31:296 3412 IRP_MJ_DIRECTORY_CONTROL : 804F4562
12:26:31:296 3412 IRP_MJ_FILE_SYSTEM_CONTROL : 804F4562
12:26:31:296 3412 IRP_MJ_DEVICE_CONTROL : F75DD3BB
12:26:31:296 3412 IRP_MJ_INTERNAL_DEVICE_CONTROL : F75E0F28
12:26:31:296 3412 IRP_MJ_SHUTDOWN : F75DD2E2
12:26:31:296 3412 IRP_MJ_LOCK_CONTROL : 804F4562
12:26:31:296 3412 IRP_MJ_CLEANUP : 804F4562
12:26:31:296 3412 IRP_MJ_CREATE_MAILSLOT : 804F4562
12:26:31:296 3412 IRP_MJ_QUERY_SECURITY : 804F4562
12:26:31:296 3412 IRP_MJ_SET_SECURITY : 804F4562
12:26:31:296 3412 IRP_MJ_POWER : F75DEC82
12:26:31:296 3412 IRP_MJ_SYSTEM_CONTROL : F75E399E
12:26:31:296 3412 IRP_MJ_DEVICE_CHANGE : 804F4562
12:26:31:296 3412 IRP_MJ_QUERY_QUOTA : 804F4562
12:26:31:296 3412 IRP_MJ_SET_QUOTA : 804F4562
12:26:31:296 3412 C:\WINDOWS\system32\DRIVERS\disk.sys - Verdict: 1
12:26:31:296 3412
12:26:31:296 3412 Driver Name: iaStor
12:26:31:296 3412 IRP_MJ_CREATE : 86492AC8
12:26:31:296 3412 IRP_MJ_CREATE_NAMED_PIPE : 86492AC8
12:26:31:296 3412 IRP_MJ_CLOSE : 86492AC8
12:26:31:296 3412 IRP_MJ_READ : 86492AC8
12:26:31:296 3412 IRP_MJ_WRITE : 86492AC8
12:26:31:296 3412 IRP_MJ_QUERY_INFORMATION : 86492AC8
12:26:31:296 3412 IRP_MJ_SET_INFORMATION : 86492AC8
12:26:31:296 3412 IRP_MJ_QUERY_EA : 86492AC8
12:26:31:296 3412 IRP_MJ_SET_EA : 86492AC8
12:26:31:296 3412 IRP_MJ_FLUSH_BUFFERS : 86492AC8
12:26:31:296 3412 IRP_MJ_QUERY_VOLUME_INFORMATION : 86492AC8
12:26:31:296 3412 IRP_MJ_SET_VOLUME_INFORMATION : 86492AC8
12:26:31:296 3412 IRP_MJ_DIRECTORY_CONTROL : 86492AC8
12:26:31:296 3412 IRP_MJ_FILE_SYSTEM_CONTROL : 86492AC8
12:26:31:296 3412 IRP_MJ_DEVICE_CONTROL : 86492AC8
12:26:31:296 3412 IRP_MJ_INTERNAL_DEVICE_CONTROL : 86492AC8
12:26:31:296 3412 IRP_MJ_SHUTDOWN : 86492AC8
12:26:31:296 3412 IRP_MJ_LOCK_CONTROL : 86492AC8
12:26:31:296 3412 IRP_MJ_CLEANUP : 86492AC8
12:26:31:296 3412 IRP_MJ_CREATE_MAILSLOT : 86492AC8
12:26:31:296 3412 IRP_MJ_QUERY_SECURITY : 86492AC8
12:26:31:296 3412 IRP_MJ_SET_SECURITY : 86492AC8
12:26:31:296 3412 IRP_MJ_POWER : 86492AC8
12:26:31:296 3412 IRP_MJ_SYSTEM_CONTROL : 86492AC8
12:26:31:296 3412 IRP_MJ_DEVICE_CHANGE : 86492AC8
12:26:31:296 3412 IRP_MJ_QUERY_QUOTA : 86492AC8
12:26:31:296 3412 IRP_MJ_SET_QUOTA : 86492AC8
12:26:31:296 3412 Driver "iaStor" infected by TDSS rootkit!
12:26:31:328 3412 C:\WINDOWS\system32\DRIVERS\iaStor.sys - Verdict: 1
12:26:31:328 3412 File "C:\WINDOWS\system32\DRIVERS\iaStor.sys" infected by TDSS rootkit ... 12:26:31:328 3412 Processing driver file: C:\WINDOWS\system32\DRIVERS\iaStor.sys
12:26:31:328 3412 ProcessDirEnumEx: FindFirstFile(C:\WINDOWS\system32\DriverStore\FileRepository\*) error 3
12:26:31:562 3412 ProcessDirEnumEx: FindFirstFile(C:\WINDOWS\ServicePackFiles\*) error 3
12:26:31:578 3412 !fdfb7
12:26:31:750 3412 !vfvi1: 1813
12:26:31:750 3412 !vdf6
12:26:31:750 3412 Backup copy not found, trying to cure infected file..
12:26:31:750 3412 C:\WINDOWS\system32\DRIVERS\iaStor.sys - Verdict: Cure failed (0)
12:26:31:750 3412 cure failed
12:26:31:750 3412
12:26:31:750 3412 Completed
12:26:31:750 3412
12:26:31:750 3412 Results:
12:26:31:750 3412 Memory objects infected / cured / cured on reboot: 1 / 0 / 0
12:26:31:750 3412 Registry objects infected / cured / cured on reboot: 0 / 0 / 0
12:26:31:765 3412 File objects infected / cured / cured on reboot: 1 / 0 / 0
12:26:31:765 3412
12:26:31:765 3412 fclose_ex: Trying to close file C:\WINDOWS\system32\config\system
12:26:31:765 3412 fclose_ex: Trying to close file C:\WINDOWS\system32\config\software
12:26:31:765 3412 KLMD(ARK) unloaded successfully

#7 madman666

madman666
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Selah, WA
  • Local time:11:45 PM

Posted 04 April 2010 - 02:49 PM

Malwarebytes' Anti-Malware 1.45
www.malwarebytes.org

Database version: 3954

Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

4/4/2010 12:48:49 PM
mbam-log-2010-04-04 (12-48-49).txt

Scan type: Quick scan
Objects scanned: 152240
Time elapsed: 8 minute(s), 23 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:45 AM

Posted 04 April 2010 - 02:54 PM

Looking good
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#9 madman666

madman666
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Selah, WA
  • Local time:11:45 PM

Posted 04 April 2010 - 04:37 PM

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 04/04/2010 at 02:26 PM

Application Version : 4.35.1002

Core Rules Database Version : 4768
Trace Rules Database Version: 2580

Scan type : Complete Scan
Total Scan Time : 00:33:08

Memory items scanned : 278
Memory threats detected : 0
Registry items scanned : 4876
Registry threats detected : 4
File items scanned : 30792
File threats detected : 3

Rogue.MalwareDefense
HKU\.DEFAULT\Software\Malware Defense
HKU\S-1-5-18\Software\Malware Defense

Rogue.PaladinAntivirus
HKU\.DEFAULT\Software\Paladin Antivirus
HKU\S-1-5-18\Software\Paladin Antivirus

Adware.Tracking Cookie
C:\Documents and Settings\NetworkService.NT AUTHORITY\Cookies\system@advertise[1].txt
C:\Documents and Settings\NetworkService.NT AUTHORITY\Cookies\system@overture[1].txt
C:\Documents and Settings\NetworkService.NT AUTHORITY\Cookies\system@trafficengine[1].txt


after all this got on the previously infected computer and mbam is still blocking ips and while typing this message a new window opened up without me doing it anything else to do would be greatly appreciated and thanks for all the help you have done

#10 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:45 AM

Posted 04 April 2010 - 05:08 PM

We need a deeper look something is protecting this. Please go here....
Preparation Guide ,do steps 6 - 9.

Create a DDS log and post it in the new topic explained in step 9 and not here,thanks.
If Gmer won't run,skip it and move on.
Let me know if that went well.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#11 madman666

madman666
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Selah, WA
  • Local time:11:45 PM

Posted 04 April 2010 - 07:40 PM

ok did the scans, and posted the logs in a new topic. everything went fine. hopefully we can finally get this over with. thanks for all the help you've provided. i'd be lost without it.

#12 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:45 AM

Posted 04 April 2010 - 08:20 PM

Thanks, looks good and we will.

Now that your log is properly posted, you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a Malware Removal Team member, nor should you continue to ask for help elsewhere. Doing so can result in system changes which may not show it the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the Malware Removal Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the Malware Removal Team members are very busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the Malware Removal Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another HJT Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users