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

spyware.passwords.xgen infection?


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

#1 drews247

drews247

  • Members
  • 85 posts
  • OFFLINE
  •  
  • Local time:10:54 PM

Posted 02 June 2011 - 10:55 AM

Hi,

Last night I ran Norton Endpoint and it came up with a simple tracking cookie and removed it. I then ran MBAM and it came up with 2 spyware.passwords.xgen entries. I have pasted the MBAM log below. It appears it was able to remove them, but I just want to be sure my computer is safe before I change all my passwords.

Thank you in advance for your help.

Malwarebytes' Anti-Malware 1.51.0.1200
www.malwarebytes.org

Database version: 6752

Windows 6.1.7601 Service Pack 1
Internet Explorer 9.0.8112.16421

6/2/2011 11:12:10 AM
mbam-log-2011-06-02 (11-12-10).txt

Scan type: Full scan (C:\|)
Objects scanned: 290584
Time elapsed: 1 hour(s), 27 minute(s), 3 second(s)

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

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs\C:\PROGRAM FILES\HP\DIGITAL IMAGING\HELP\PLAYER\FLASHPLA.EXE (Spyware.Passwords.XGen) -> Value: FLASHPLA.EXE -> Quarantined and deleted successfully.

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
c:\program files\HP\digital imaging\help\player\FlashPla.exe (Spyware.Passwords.XGen) -> Quarantined and deleted successfully.

Edited by hamluis, 02 June 2011 - 01:29 PM.
Moved from MRL to AII, no logs.


BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:03:54 AM

Posted 05 June 2011 - 01:21 PM

Hello,

And welcome to BleepingComputer.com, before we can assist you with your question of: Am I infected? You will need to perform the following tasks and post the logs of each if you can.


SUPERAntiSpyware:

Please download and scan with SUPERAntiSpyware Free

  • Double-click SUPERAntiSypware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If it will not start, go to Start > All Prgrams > SUPERAntiSpyware and click on Alternate Start.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the "General and Startup" tab, and under Start-up Options, make sure "Start SUPERAntiSpyware when Windows starts" box is unchecked.
  • Click the "Scanning Control" tab, and 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 a scan just yet.
Reboot your computer in "Safe Mode" using the F8 method. To do this, restart your computer and after hearing your computer beep once during startup (but before the Windows icon appears) press the F8 key repeatedly. A menu will appear with several options. Use the arrow keys to navigate and select the option to run Windows in "Safe Mode".

Scan with SUPERAntiSpyware as follows:
  • Launch the program and back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan and click "Next".
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • 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.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the SUPERAntiSpyware Portable Scanner instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.

Instructions:

Download and scan with SUPERAntiSpyware Free for Home Users
  • Double-click SUPERAntiSpyware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the Scanning Control tab.
  • 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.
  • Back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan.
  • Click "Next" to start the scan. Please be patient while it scans your computer.
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes".
  • 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.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the SUPERAntiSpyware Portable Scanner instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.


Now GMER

GMER does not work in 64bit Mode!!!!!!

Please download GMER from one of the following locations and save it to your desktop:

  • Main Mirror
    This version will download a randomly named file (Recommended)
  • Zipped Mirror
    This version will download a zip file you will need to extract first. If you use this mirror, please extract the zip file to your desktop.
  • Disconnect from the Internet and close all running programs.
  • Temporarily disable any real-time active protection so your security programs will not conflict with gmer's driver.
  • Double-click on the randomly named GMER file (i.e. n7gmo46c.exe) and allow the gmer.sys driver to load if asked.
  • Note: If you downloaded the zipped version, extract the file to its own folder such as C:\gmer and then double-click on gmer.exe.

    Posted Image
  • GMER will open to the Rootkit/Malware tab and perform an automatic Full Scan when first run. (do not use the computer while the scan is in progress)
  • If you receive a WARNING!!! about rootkit activity and are asked to fully scan your system...click NO.
  • Now click the Scan button. If you see a rootkit warning window, click OK.
  • When the scan is finished, click the Save... button to save the scan results to your Desktop. Save the file as gmer.log.
  • Click the Copy button and paste the results into your next reply.
  • Exit GMER and be sure to re-enable your anti-virus, Firewall and any other security programs you had disabled.
-- If you encounter any problems, try running GMER in safe mode.
-- If GMER crashes or keeps resulting in a BSODs, uncheck Devices on the right side before scanning
.



#3 drews247

drews247
  • Topic Starter

  • Members
  • 85 posts
  • OFFLINE
  •  
  • Local time:10:54 PM

Posted 05 June 2011 - 08:36 PM

SAS Log

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

Generated 06/05/2011 at 08:26 PM

Application Version : 4.53.1000

Core Rules Database Version : 7205
Trace Rules Database Version: 5017

Scan type : Complete Scan
Total Scan Time : 01:39:00

Memory items scanned : 407
Memory threats detected : 0
Registry items scanned : 8296
Registry threats detected : 0
File items scanned : 141125
File threats detected : 23

Adware.Tracking Cookie
ads2.msads.net [ C:\Users\Drew\AppData\Roaming\Macromedia\Flash Player\#SharedObjects\PQY7GRTF ]
secure-us.imrworldwide.com [ C:\Users\Drew\AppData\Roaming\Macromedia\Flash Player\#SharedObjects\PQY7GRTF ]
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ad.wsod[2].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ad.yieldmanager[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ads.pubmatic[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ads.undertone[2].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ar.atwola[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ar.atwola[2].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ar.atwola[3].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ar.atwola[4].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ar.atwola[5].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@ar.atwola[6].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@at.atwola[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@atwola[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@interclick[2].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@invitemedia[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@lfstmedia[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@lucidmedia[2].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@media.adfrontiers[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@media6degrees[2].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@revsci[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@steelhousemedia[1].txt
C:\Users\Drew\AppData\Roaming\Microsoft\Windows\Cookies\Low\drew@tacoda.at.atwola[1].txt




GMER Log

GMER 1.0.15.15640 - http://www.gmer.net
Rootkit scan 2011-06-05 21:31:54
Windows 6.1.7601 Service Pack 1 Harddisk1\DR1 -> \Device\Ide\IAAStorageDevice-0 rev.
Running: i9ckq33g.exe; Driver: C:\Users\Drew\AppData\Local\Temp\kxldapob.sys


---- System - GMER 1.0.15 ----

SSDT 87D2B478 ZwAlertResumeThread
SSDT 87D2B558 ZwAlertThread
SSDT 87D11E68 ZwAllocateVirtualMemory
SSDT 87CF2260 ZwConnectPort
SSDT 87D28F80 ZwCreateMutant
SSDT 87D11FB0 ZwCreateThread
SSDT 87D1F458 ZwFreeVirtualMemory
SSDT 87D2B2B8 ZwImpersonateAnonymousToken
SSDT 87D2B398 ZwImpersonateThread
SSDT 87D293D8 ZwMapViewOfSection
SSDT 87D28EA0 ZwOpenEvent
SSDT 87D11F38 ZwOpenProcessToken
SSDT 87D2BA30 ZwOpenThreadToken
SSDT \??\C:\Windows\system32\drivers\wpsdrvnt.sys ZwProtectVirtualMemory [0x8E1E2B90]
SSDT 87BCF788 ZwResumeThread
SSDT 87D2B950 ZwSetContextThread
SSDT 87D2BB20 ZwSetInformationProcess
SSDT 87D2B860 ZwSetInformationThread
SSDT 87D28DC0 ZwSuspendProcess
SSDT 87D2B6A0 ZwSuspendThread
SSDT 87D150A0 ZwTerminateProcess
SSDT 87D2B780 ZwTerminateThread
SSDT 87D29318 ZwUnmapViewOfSection
SSDT 87D1F528 ZwWriteVirtualMemory

---- Kernel code sections - GMER 1.0.15 ----

.text ntkrnlpa.exe!ZwSaveKey + 13C1 82E49339 1 Byte [06]
.text ntkrnlpa.exe!KiDispatchInterrupt + 5A2 82E82D52 19 Bytes [E0, 0F, BA, F0, 07, 73, 09, ...] {LOOPNZ 0x11; MOV EDX, 0x97307f0; MOV CR4, EAX; OR AL, 0x80; MOV CR4, EAX; RET ; MOV ECX, CR3}
.text ntkrnlpa.exe!KeRemoveQueueEx + 10DB 82E89DD0 8 Bytes [78, B4, D2, 87, 58, B5, D2, ...] {JS 0xffffffffffffffb6; ROL BYTE [EDI-0x782d4aa8], CL}
.text ntkrnlpa.exe!KeRemoveQueueEx + 10F3 82E89DE8 4 Bytes [68, 1E, D1, 87]
.text ntkrnlpa.exe!KeRemoveQueueEx + 1193 82E89E88 4 Bytes [60, 22, CF, 87]
.text ntkrnlpa.exe!KeRemoveQueueEx + 11CF 82E89EC4 4 Bytes [80, 8F, D2, 87]
.text ntkrnlpa.exe!KeRemoveQueueEx + 1203 82E89EF8 4 Bytes [B0, 1F, D1, 87]
.text ...

---- User IAT/EAT - GMER 1.0.15 ----

IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipAlloc] [73B42437] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdiplusStartup] [73B25600] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdiplusShutdown] [73B256BE] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipFree] [73B424B2] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipDeleteGraphics] [73B38514] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipDisposeImage] [73B34CC8] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipGetImageWidth] [73B3506F] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipGetImageHeight] [73B35144] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipCreateBitmapFromHBITMAP] [73B36671] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipCreateFromHDC] [73B3826B] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipSetCompositingMode] [73B387BA] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipSetInterpolationMode] [73B3901B] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipDrawImageRectI] [73B3E1BE] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[580] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipCloneImage] [73B34BFA] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\System32\rundll32.exe[1816] @ C:\Windows\system32\USER32.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Windows\System32\rundll32.exe[1816] @ C:\Windows\system32\GDI32.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Windows\System32\rundll32.exe[1816] @ C:\Windows\system32\SHLWAPI.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Windows\System32\rundll32.exe[1816] @ C:\Windows\system32\ADVAPI32.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Program Files\Lenovo\System Update\SUService.exe[3204] @ C:\Windows\system32\SHLWAPI.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Program Files\Lenovo\System Update\SUService.exe[3204] @ C:\Windows\system32\GDI32.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Program Files\Lenovo\System Update\SUService.exe[3204] @ C:\Windows\system32\USER32.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Program Files\Lenovo\System Update\SUService.exe[3204] @ C:\Windows\system32\ADVAPI32.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Program Files\Lenovo\System Update\SUService.exe[3204] @ C:\Windows\system32\WININET.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)
IAT C:\Program Files\Lenovo\System Update\SUService.exe[3204] @ C:\Windows\system32\CRYPT32.dll [KERNEL32.dll!GetProcAddress] [74F4FFF6] C:\Windows\system32\apphelp.dll (Application Compatibility Client Library/Microsoft Corporation)

---- Devices - GMER 1.0.15 ----

AttachedDevice \Driver\kbdclass \Device\KeyboardClass0 Wdf01000.sys (Kernel Mode Driver Framework Runtime/Microsoft Corporation)
AttachedDevice \Driver\tdx \Device\Tcp SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume1 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume2 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume3 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume4 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\tdx \Device\Udp SYMTDI.SYS (Network Dispatch Driver/Symantec Corporation)

Device \Driver\ACPI_HAL \Device\0000006c halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation)

AttachedDevice \FileSystem\fastfat \Fat fltmgr.sys (Microsoft Filesystem Filter Manager/Microsoft Corporation)

---- Threads - GMER 1.0.15 ----

Thread System [4:3368] A98C3F2E

---- Registry - GMER 1.0.15 ----

Reg HKLM\SYSTEM\CurrentControlSet\services\BTHPORT\Parameters\Keys\001e4cf643d1
Reg HKLM\SYSTEM\ControlSet002\services\BTHPORT\Parameters\Keys\001e4cf643d1 (not active ControlSet)

---- Disk sectors - GMER 1.0.15 ----

Disk \Device\Harddisk1\DR1 sector 00: rootkit-like behavior

---- EOF - GMER 1.0.15 ----

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 72,906 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:54 PM

Posted 05 June 2011 - 09:13 PM

Hello there is Rootkit activity here that will need specifoc attention.

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

Create a DDS log and post it in the new topic explained in step 9 which is here Virus, Trojan, Spyware, and Malware Removal Logs and not in this topic,thanks.
Include the GMER log you posted earlier.
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

#5 drews247

drews247
  • Topic Starter

  • Members
  • 85 posts
  • OFFLINE
  •  
  • Local time:10:54 PM

Posted 05 June 2011 - 09:44 PM

Hello there is Rootkit activity here that will need specifoc attention.

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

Create a DDS log and post it in the new topic explained in step 9 which is here Virus, Trojan, Spyware, and Malware Removal Logs and not in this topic,thanks.
Include the GMER log you posted earlier.
Let me know if that went well.

should i generate a new gmer log as well? i noticed that i need to uncheck some options in these instructions for gmer

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 72,906 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:54 PM

Posted 05 June 2011 - 09:50 PM

Sure then it will all br perfect.
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

#7 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,573 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:54 PM

Posted 06 June 2011 - 02:06 AM

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 MR Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users