How to Remove Rustock.b, pe386, lzx32, msguard infections, (removal instructions) |
![]() ![]() |
How to Remove Rustock.b, pe386, lzx32, msguard infections, (removal instructions) |
Dec 2 2006, 05:33 PM
Post
#1
|
|
![]() Site Administrator Posts: 17,476 From: 127.0.0.1 OS: Windows Vista Ultimate |
How to Remove Rustock.b, pe386, lzx32, msguard infections Credit: ejvindh and Swandog46 The main symptom of the trojan Rustock.b rootkit infection (sometimes identifed as pe386, lzx32 or msguard), is heavy network-activity without any obvious reason. When analysing the computer, the traditional malware tools do not typically find anything. However, tools like Gmer, Combofix, Smitfraudfix and SDfix are able to detect the infection: GMER: QUOTE ---- Services - GMER 1.0.11 ---- Service C:\WINDOWS\System32\lzx32.sys (*** hidden *** ) [SYSTEM] pe386 <-- ROOTKIT !!! ---- Registry - GMER 1.0.11 ---- Reg \Registry\MACHINE\SYSTEM\ControlSet001\Services\pe386 Reg \Registry\MACHINE\SYSTEM\ControlSet001\Services\pe386@Type 1 Reg \Registry\MACHINE\SYSTEM\ControlSet001\Services\pe386@Start 1 ........ Reg \Registry\MACHINE\SYSTEM\CurrentControlSet\Services\pe386 Reg \Registry\MACHINE\SYSTEM\CurrentControlSet\Services\pe386@Type 1 Reg \Registry\MACHINE\SYSTEM\CurrentControlSet\Services\pe386@Start 1 ......... ---- Files - GMER 1.0.11 ---- ADS ... File C:\WINDOWS\system32\lzx32.sys <-- ROOTKIT !!! COMBOFIX: QUOTE Rootkit driver pe386 is present. A rootkit scan is required or Rootkit driver lzx32 is present. A rootkit scan is required or Rootkit driver msguard is present. A rootkit scan is required SMITFRAUDFIX (search-log): QUOTE »»»»»»»»»»»»»»»»»»»»»»»» pe386-msguard pe386 detected, use a Rootkit scanner or msguard detected, use a Rootkit scanner or lzx32 detected, use a Rootkit scanner SDFIX: QUOTE Services: --------- Rootkit pe386 Present. Rootkit scan required! or Rootkit lzx32 Present. Rootkit scan required! or Rootkit msguard Present. Rootkit scan required! Rustock.b (pe386, lzx32, msguard) Removal Instructions:
QUOTE ************************* Rustock.b-fix -- By ejvindh ************************* 19-10-2006 21:59:37,90 ******************* Pre-run Status of system ******************* Rootkit driver PE386 is found. Starting the unload-procedure.... Examine the Avenger-logfile in order to assess the success of the unload-procedure Rustock.b-ADS attached to the System32-folder: :lzx32.sys 66432 Total size: 66432 bytes. Attempting to remove ADS... system32: deleted 66432 bytes in 1 streams. ******************* Post-run Status of system ******************* Rustock.b-driver on the system: NONE! Rustock.b-ADS attached to the System32-folder: No streams found. ******************************* End of Logfile ******************************** If no rustock.b-infection is found, the logfile will look like this: QUOTE ************************* Rustock.b-fix -- By ejvindh *************************
06-10-19 22:37:34.93 No Rustock.b-rootkits found ******************************* End of Logfile ******************************** |
|
|
Jul 12 2007, 04:19 PM
Post
#2
|
|
![]() Site Administrator Posts: 17,476 From: 127.0.0.1 OS: Windows Vista Ultimate |
This topic has been left open to allow specific questions and comments related ONLY to this guide. It's NOT for posting HJT logs, links to your logs, or any other general malware help. Replies not following these rules will be deleted. Thanks for your cooperation.
|
|
|
![]() ![]() |
Similar Topics
| Topic Title | Replies / Views | Topic Information | |||||
|---|---|---|---|---|---|---|---|
![]() |
72 / 270,286 | 29th November 2008 - 08:38 AM admin started - last by sari |
|||||
![]() |
49 / 43,900 | 24th November 2008 - 02:57 PM miekiemoes started - last by njay |
|||||
![]() |
59 / 51,357 | 24th November 2008 - 03:02 PM admin started - last by Rorschach112 |
|||||
![]() |
5 / 2,517 | 28th November 2008 - 08:11 PM Mike started - last by lara123 |
|||||
|
Time is now: 3rd December 2008 - 01:09 AM |
| Advertisements do not imply our endorsement of that product or service. The forum is run by volunteers who donate their time and expertise. We make every attempt to ensure that the help and advice posted is accurate and will not cause harm to your computer. However, we do not guarantee that they are accurate and they are to be used at your own risk. |