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

Trojan.Agent/Gen-IExplorer[Fake] and Trojan.Agent/Gen-PEC Virus


  • Please log in to reply
19 replies to this topic

#1 Bo1965

Bo1965

  • Members
  • 235 posts
  • OFFLINE
  •  
  • Local time:08:08 AM

Posted 04 May 2011 - 01:32 PM

I have two virus' that I cant remove (Trojan.Agent/Gen-PEC and Trojan.Agent/Gen-IExplorer[Fake]). I have ran Super Anti Spyware a dozen times and it flags these two virus'. However, every time is removes them they come back. Also, they only show up after I run Rkill. Any advice?

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:08 AM

Posted 04 May 2011 - 02:02 PM

Hello ,lets run these and see. You did update SAS prior to running?

Next run MBAM (MalwareBytes):

Please download Malwarebytes Anti-Malware and save it to your desktop.
Download Link 1
Download Link 2MBAM may "make changes to your registry" as part of its disinfection routine. If using other security programs that detect registry changes (ie Spybot's Teatimer), they may interfere or alert you. Temporarily disable such programs or permit them to allow the changes.
  • Make sure you are connected to the Internet.
  • Double-click on mbam-setup.exe to install the application.
    For instructions with screenshots, please refer to the How to use Malwarebytes' Anti-Malware Guide.
  • When the installation begins, follow the prompts and do not make any changes to default settings.
  • When installation has finished, make sure you leave both of these checked:
    • Update Malwarebytes' Anti-Malware
    • Launch Malwarebytes' Anti-Malware
  • Then click Finish.
MBAM will automatically start and you will be asked to update the program before performing a scan.
  • If an update is found, the program will automatically update itself. Press the OK button to close that box and continue.
  • If you encounter any problems while downloading the definition updates, manually download them from here and just double-click on mbam-rules.exe to install.
On the Scanner tab:
  • Make sure the "Perform Quick Scan" option is selected.
  • Then click on the Scan button.
  • If asked to select the drives to scan, leave all the drives selected and click on the Start Scan button.
  • The scan will begin and "Scan in progress" will show at the top. It may take some time to complete so please be patient.
  • When the scan is finished, a message box will say "The scan completed successfully. Click 'Show Results' to display all objects found".
  • Click OK to close the message box and continue with the removal process.
Back at the main Scanner screen:
  • Click on the Show Results button to see a list of any malware that was found.
  • Make sure that everything is checked, and click Remove Selected.
  • When removal is completed, a log report will open in Notepad.
  • The log is automatically saved and can be viewed by clicking the Logs tab in MBAM.
  • Copy and paste the contents of that report in your next reply. Be sure to post the complete log to include the top portion which shows MBAM's database version and your operating system.
  • Exit MBAM when done.
Note: If MBAM encounters a file that is difficult to remove, you will be asked to reboot your computer so MBAM can proceed with the disinfection process. If asked to restart the computer, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware.

Troubleshoot Malwarebytes' Anti-Malware



I'd like us to scan your machine with ESET OnlineScan
  • Hold down Control and click on the following link to open ESET OnlineScan in a new window.
    ESET OnlineScan
  • Click the Posted Image button.
  • For alternate browsers only: (Microsoft Internet Explorer users can skip these steps)
    • Click on Posted Image to download the ESET Smart Installer. Save it to your desktop.
    • Double click on the Posted Image icon on your desktop.
  • Check Posted Image
  • Click the Posted Image button.
  • Accept any security warnings from your browser.
  • Under scan settings, check Posted Image and check Remove found threats
  • Click Advanced settings and select the following:
    • Scan potentially unwanted applications
    • Scan for potentially unsafe applications
    • Enable Anti-Stealth technology
  • ESET will then download updates for itself, install itself, and begin scanning your computer. Please be patient as this can take some time.
  • When the scan completes, push Posted Image
  • Push Posted Image, and save the file to your desktop using a unique name, such as ESETScan. Include the contents of this report in your next reply.
  • Push the Posted Image button.
  • Push Posted Image

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 Bo1965

Bo1965
  • Topic Starter

  • Members
  • 235 posts
  • OFFLINE
  •  
  • Local time:08:08 AM

Posted 04 May 2011 - 07:58 PM

Below is the result of MBAM:

Malwarebytes' Anti-Malware 1.50.1.1100
www.malwarebytes.org

Database version: 6492

Windows 6.1.7601 Service Pack 1
Internet Explorer 8.0.7601.17514

5/4/2011 6:19:28 PM
mbam-log-2011-05-04 (18-19-28).txt

Scan type: Quick scan
Objects scanned: 157429
Time elapsed: 1 minute(s), 14 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)



Also, ESET said there were no known threats.

I ran SAS again and sure enough, the two trojans were there. They are not showing up on MBAM or ESET.

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:08 AM

Posted 04 May 2011 - 08:15 PM

Let's see the SAS log.
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.
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 Bo1965

Bo1965
  • Topic Starter

  • Members
  • 235 posts
  • OFFLINE
  •  
  • Local time:08:08 AM

Posted 04 May 2011 - 10:56 PM

Good evening and thank you for your assistance. Below is the log of my last virus scan using SAS:

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

Generated 05/04/2011 at 09:46 PM

Application Version : 4.51.1000

Core Rules Database Version : 6992
Trace Rules Database Version: 4804

Scan type : Complete Scan
Total Scan Time : 00:11:11

Memory items scanned : 504
Memory threats detected : 0
Registry items scanned : 12328
Registry threats detected : 0
File items scanned : 25156
File threats detected : 4

Trojan.Agent/Gen-IExplorer[Fake]
C:\USERS\BO'S\APPDATA\LOCAL\TEMP\RARSFX8\NIRD\IEXPLORE.EXE
C:\Windows\Prefetch\IEXPLORE.EXE-AE852E17.pf

Trojan.Agent/Gen-PEC
C:\USERS\BO'S\APPDATA\LOCAL\TEMP\RARSFX8\PROCS\EXPLORER.EXE
C:\Windows\Prefetch\EXPLORER.EXE-C1E56B5E.pf

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:08 AM

Posted 05 May 2011 - 09:10 AM

Ok, let's clear the temp files and see if it comes back.

Run TFC by OT (Temp File Cleaner)
Please download TFC by Old Timer and save it to your desktop.
alternate download link

Save any unsaved work. TFC will close ALL open programs including your browser!
Double-click on TFC.exe to run it. If you are using Vista, right-click on the file and choose Run As Administrator.
Click the Start button to begin the cleaning process and let it run uninterrupted to completion.
Important! If TFC prompts you to reboot, please do so immediately. If not prompted, manually reboot the machine anyway to ensure a complete clean.
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 Bo1965

Bo1965
  • Topic Starter

  • Members
  • 235 posts
  • OFFLINE
  •  
  • Local time:08:08 AM

Posted 05 May 2011 - 02:29 PM

Good afternoon. Ran TFC then rebooted. After reboot I ran RKill and followed it up with SAS. Same two trojans are still there. Below is the log:

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

Generated 05/05/2011 at 01:24 PM

Application Version : 4.51.1000

Core Rules Database Version : 6996
Trace Rules Database Version: 4808

Scan type : Complete Scan
Total Scan Time : 00:10:47

Memory items scanned : 472
Memory threats detected : 0
Registry items scanned : 12328
Registry threats detected : 0
File items scanned : 24961
File threats detected : 5

Trojan.Agent/Gen-IExplorer[Fake]
C:\USERS\BO'S\APPDATA\LOCAL\TEMP\RARSFX0\NIRD\IEXPLORE.EXE

Trojan.Agent/Gen-PEC
C:\USERS\BO'S\APPDATA\LOCAL\TEMP\RARSFX0\PROCS\EXPLORER.EXE

Adware.Tracking Cookie
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@a1.interclick[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@atdmt[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@interclick[2].txt

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:08 AM

Posted 05 May 2011 - 08:47 PM

Stubborn little thing

Please download Norman Malware Cleaner and save to your desktop.
alternate download link
If you previously used Norman, delete that version and download it again as the tool is frequently updated!
  • Be sure to read all the information Norman provides on that same page.
  • Double-click on Norman_Malware_Cleaner.exe to start. Vista/Windows 7 users right-click and select Run As Administrator.
    The tool is very slow to load as it uses a special driver. This is normal so please be patient.
  • Read the End User License Agreement and click the Accept button to open the scanning window.
  • Click Start Scan to begin.
  • In some cases Norman Malware Cleaner may require that you restart the computer to completely remove an infection. If prompted, reboot to ensure that all infections are removed.
  • After the scan has finished, a log file a log file named NFix_date_time (i.e. NFix_2009-06-22_07-08-56.log) will be created on your desktop with the results.
  • Copy and paste the contents of that file in your next reply.
-- Note: If you need to scan a usb flash drives or other removable drives not listed, use the Add button to browse to the drives location, click on the drive to highlight and choose Ok.
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 Bo1965

Bo1965
  • Topic Starter

  • Members
  • 235 posts
  • OFFLINE
  •  
  • Local time:08:08 AM

Posted 06 May 2011 - 10:18 AM

Ok, these virus' are becoming a pain in my posterior region! Here is what I did:

1) Downloaded Norman Malware Cleaner
2) Ran Norman on quick scan and it found no threats
3) Rebooted my computer
4) Ran RKill
5) Reran Norman on full scan and it found one threat on RKill and Norman deleted the application
6) I reran a full scan on SAS and it found the same two virus' and an additional 17 tracking cookies

Below is my log for Norman and SAS log is below it:

Norman Malware Cleaner v2.00.05
Copyright 1990 - 2011, Norman ASA.

Norman Scanner Engine Version: 6.07.07
nvcbin.def: Version: 6.07.00, Date: 2011/05/05 08:27:14, Variants: 11873463
nvcmacro.def: Version: 6.07.00, Date: 2011/02/01 07:21:31, Variants: 20465

Operating System: Windows 7 Service Pack 1

Switches: /iagree
Running without NSAK

Scan started: 2011/05/05 21:34:46

Running pre-scan cleanup routine...

Scanning time: 0s

Scanning system for active rootkit activity...

Scanning time: 0s

Scanning running processes and process memory...

Number of objects found: 811
Number of objects scanned: 811
Number of objects not scanned: 0
Number of malicious memory objects found: 0
Scanning time: 7s

Running full scan...
C:\ProgramData\Microsoft\BingBar\SeaPort\BBSvcConfig.cab: Error opening file for read: 0x00000005
C:\ProgramData\Microsoft\BingBar\SeaPort\SeaPort.cab: Error opening file for read: 0x00000005
C:\ProgramData\Microsoft\Microsoft Antimalware\IMpServiceEDB4FA23-53B8-4AFA-8C5D-99752CCA7094.lock: Error opening file for read: 0x00000020
C:\ProgramData\Microsoft\Microsoft Antimalware\Scans\MpDiag.bin: Error opening file for read: 0x00000020
C:\ProgramData\Microsoft\Microsoft Antimalware\Scans\History\CacheManager\MpScanCache-0.bin: Error opening file for read: 0x00000020
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log: Error opening file for read: 0x00000020
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSStmp.log: Error opening file for read: 0x00000020
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\tmp.edb: Error opening file for read: 0x00000020
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb: Error opening file for read: 0x00000020
C:\ProgramData\Microsoft\Windows\DRM\Cache\Indiv01.tmp: Error opening file for read: 0x00000020
C:\System Volume Information\Syscache.hve: Error opening file for read: 0x00000020
C:\System Volume Information\Syscache.hve.LOG1: Error opening file for read: 0x00000020
C:\System Volume Information\Syscache.hve.LOG2: Error opening file for read: 0x00000020
C:\Users\Bo's\ntuser.dat: Error opening file for read: 0x00000020
C:\Users\Bo's\ntuser.dat.LOG1: Error opening file for read: 0x00000020
C:\Users\Bo's\ntuser.dat.LOG2: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Microsoft\BingBar\Apps\Search_6f21d9007fa34bc78d94309126de58f5\VersionIndependent\searchhs.dat: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Microsoft\Internet Explorer\Recovery\Active\RecoveryStore.{D727E665-778E-11E0-B83A-001FBC087838}.dat: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Microsoft\Internet Explorer\Recovery\Active\{D727E666-778E-11E0-B83A-001FBC087838}.dat: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Microsoft\Windows\UsrClass.dat: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG1: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG2: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Temp\~DF47817C6324AEE41C.TMP: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Temp\~DF56466364A6AFEA83.TMP: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Temp\~DF98C5EDC9242075F0.TMP: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Temp\~DF9BB19BBF15F30BE3.TMP: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Temp\~DFBC49E2F9F648B04A.TMP: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Temp\~DFC3C65B14CB4364DB.TMP: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Temp\~DFDA8004F6C2D3A6EF.TMP: Error opening file for read: 0x00000020
C:\Users\Bo's\AppData\Local\Temp\~DFEF0D0775694DE4E9.TMP: Error opening file for read: 0x00000020
C:\Users\Bo's\Desktop\rkill.exe: File infected with W32/Agent.VBCZ
Deleted file: C:\Users\Bo's\Desktop\rkill.exe
C:\Windows\Installer\14e99.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\1ee4a4.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\2095b.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\2095c.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\3bbaed.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\49bbbc.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\49bbd0.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\49bbe5.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\49bc0c.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\58a88.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\6af3a8.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\894169.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\89417e.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\894198.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\8941ae.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\93a9b.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\9c5524.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\9c552b.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\9d791.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\d7cf05.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadcb5.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadcca.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadcdf.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadcf4.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadd09.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadd1f.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadd34.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadd4c.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadd63.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadd78.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadd8d.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadda5.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\daddc2.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\daddc3.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadddc.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dadddd.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\daddf2.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dade06.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dade1b.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dade3a.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dade4f.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dade64.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\de28a.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\dade89.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\fdc85.msp: Error opening file for read: 0x00000005
C:\Windows\Installer\$PatchCache$\Managed\9040111900063D11C8EF10054038389C\11.0.5614\ACMAIN11.CHM_1033: Error opening file for read: 0x00000005
C:\Windows\Installer\$PatchCache$\Managed\9040111900063D11C8EF10054038389C\11.0.5614\SMSW.CHM_1033: Error opening file for read: 0x00000005
C:\Windows\Installer\$PatchCache$\Managed\9040111900063D11C8EF10054038389C\11.0.5614\VBAAC10.CHM_1033: Error opening file for read: 0x00000005
C:\Windows\Installer\$PatchCache$\Managed\9040111900063D11C8EF10054038389C\11.0.5614\XLMAIN11.CHM_1033: Error opening file for read: 0x00000005
C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT.LOG1: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT.LOG2: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\LocalService\AppData\Local\lastalive0.dat: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\LocalService\AppData\Local\lastalive1.dat: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\2b6a7bd30f07c17d4fda9f882dec77e74d1b2746.HomeGroupClassifier\0a59bd8a8abd6ffe9f185b90ef175269\grouping\db.mdb: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\2b6a7bd30f07c17d4fda9f882dec77e74d1b2746.HomeGroupClassifier\0a59bd8a8abd6ffe9f185b90ef175269\grouping\edb.log: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\2b6a7bd30f07c17d4fda9f882dec77e74d1b2746.HomeGroupClassifier\0a59bd8a8abd6ffe9f185b90ef175269\grouping\tmp.edb: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT.LOG1: Error opening file for read: 0x00000020
C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT.LOG2: Error opening file for read: 0x00000020
C:\Windows\System32\catroot2\edb.log: Error opening file for read: 0x00000020
C:\Windows\System32\catroot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}\catdb: Error opening file for read: 0x00000020
C:\Windows\System32\catroot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb: Error opening file for read: 0x00000020
C:\Windows\System32\config\DEFAULT: Error opening file for read: 0x00000020
C:\Windows\System32\config\DEFAULT.LOG1: Error opening file for read: 0x00000020
C:\Windows\System32\config\DEFAULT.LOG2: Error opening file for read: 0x00000020
C:\Windows\System32\config\SECURITY: Error opening file for read: 0x00000020
C:\Windows\System32\config\SOFTWARE: Error opening file for read: 0x00000020
C:\Windows\System32\config\SECURITY.LOG2: Error opening file for read: 0x00000020
C:\Windows\System32\config\SOFTWARE.LOG1: Error opening file for read: 0x00000020
C:\Windows\System32\config\SOFTWARE.LOG2: Error opening file for read: 0x00000020
C:\Windows\System32\config\SYSTEM: Error opening file for read: 0x00000020
C:\Windows\System32\config\SYSTEM.LOG1: Error opening file for read: 0x00000020
C:\Windows\System32\config\SYSTEM.LOG2: Error opening file for read: 0x00000020
C:\Windows\System32\config\RegBack\DEFAULT: Error opening file for read: 0x00000020
C:\Windows\System32\config\RegBack\SAM: Error opening file for read: 0x00000020
C:\Windows\System32\config\RegBack\SECURITY: Error opening file for read: 0x00000020
C:\Windows\System32\config\RegBack\SOFTWARE: Error opening file for read: 0x00000020
C:\Windows\System32\config\RegBack\SYSTEM: Error opening file for read: 0x00000020
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTDiagLog.etl: Error opening file for read: 0x00000020
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventLog-Application.etl: Error opening file for read: 0x00000020
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventlog-Security.etl: Error opening file for read: 0x00000020
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventLog-System.etl: Error opening file for read: 0x00000020
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTUBPM.etl: Error opening file for read: 0x00000020
C:\Windows\Temp\TMP00000016169839F9E94B710F: Error opening file for read: 0x00000020

Number of files found: 99975

C:\Users\Bo's\Desktop\rkill.exe: File infected with !32/Agent.VBCZ
Deleted file: C:\Users\Bo's\Desktop\rkill.exe
Number of archives unpacked: 765
Number of objects found: 262391
Number of objects scanned: 262237
Number of objects not scanned: 119
Number of malicious objects found: 1
Number of malicious objects cleaned: 1
Number of malicious files found: 1
Number of malicious files cleaned: 1
Scanning time: 19m 33s
Running post-scan cleanup routine...

Scanning time: 0s

Results:
Total number of files found: 99975
Total number of archives unpacked: 765
Total number of objects found: 263202
Total number of objects scanned: 263048
Total number of objects not scanned: 119
Total number of malicious objects found: 1
Total number of malicious objects cleaned: 1
Total number of malicious files found: 1
Total number of malicious files cleaned: 1
Total scanning time: 19m 40s




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

Generated 05/06/2011 at 09:11 AM

Application Version : 4.51.1000

Core Rules Database Version : 7001
Trace Rules Database Version: 4813

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

Memory items scanned : 497
Memory threats detected : 0
Registry items scanned : 12328
Registry threats detected : 0
File items scanned : 25209
File threats detected : 21

Trojan.Agent/Gen-IExplorer[Fake]
C:\USERS\BO'S\APPDATA\LOCAL\TEMP\RARSFX1\NIRD\IEXPLORE.EXE
C:\Windows\Prefetch\IEXPLORE.EXE-02436FC4.pf

Trojan.Agent/Gen-PEC
C:\USERS\BO'S\APPDATA\LOCAL\TEMP\RARSFX1\PROCS\EXPLORER.EXE
C:\Windows\Prefetch\EXPLORER.EXE-9652A183.pf

Adware.Tracking Cookie
ia.media-imdb.com [ C:\Users\Bo's\AppData\Roaming\Macromedia\Flash Player\#SharedObjects\5G4UV699 ]
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ad.wsod[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ad.yieldmanager[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@adbrite[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ads.bleepingcomputer[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@adxpose[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@apmebf[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@atdmt[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@collective-media[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@media.calvaryftl[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@doubleclick[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@imrworldwide[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@insightexpressai[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@mediaplex[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@solvemedia[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@revsci[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@tribalfusion[1].txt

#10 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:08 AM

Posted 06 May 2011 - 12:56 PM

Ok, this maybe a TDDS virus. Perhaps a new one..
Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.4.0.0) from Kaspersky's website and not TDSSKiller.zip which appears to be an older version 2.3.2.2 of the tool.
  • Double-click on TDSSKiller.exe to run the tool for known TDSS variants.
    Vista/Windows 7 users right-click and select Run As Administrator.
  • If TDSSKiller does not run, try renaming it.
  • To do this, right-click on TDSSKiller.exe, select Rename and give it a random name with the .com file extension (i.e. 123abc.com). If you do not see the file extension, please refer to How to change the file extension.
  • Click the Start Scan button.
  • Do not use the computer during the scan
  • If the scan completes with nothing found, click Close to exit.
  • If malicious objects are found, they will show in the Scan results - Select action for found objects and offer three options.
  • Ensure Cure (default) is selected, then click Continue > Reboot now to finish the cleaning process.
  • A log file named TDSSKiller_version_date_time_log.txt (i.e. TDSSKiller.2.4.0.0_27.07.2010_09.o7.26_log.txt) will be created and saved to the root directory (usually Local Disk C:).
  • Copy and paste the contents of that file in your next reply.


If TDSSKiller does not run, try renaming it. To do this, right-click on TDSSKiller.exe, select Rename and give it a random name with the .com file extension (i.e. 123abc.com). If you do not see the file extension, please refer to these[/color] instructions. [color=green]In some cases it may be necessary to redownload TDSSKiller and randomly rename it before downloading and saving to the computer.
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 lkegley9

lkegley9

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:09:08 AM

Posted 06 May 2011 - 03:06 PM

Not meaning to bud in on your help boopme, but one thing to keep in mind. When you run rkill, it generates its 'variants' in C:\USERS\~USERNAME~\APPDATA\LOCAL\TEMP\RARSFX0\. So SAS generally picks up on that and labels them as a fake Iexplore and a PEC virus. I wouldn't worry about those two. Generally after running Rkill and I run a SAS scan, I usually un-check them because I know of it.

Edited by lkegley9, 06 May 2011 - 03:06 PM.


#12 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:08 AM

Posted 06 May 2011 - 03:24 PM

Not a problem ikegley.. I wanted another scan because I was wondering why is SAS flagging rkil now,it had never before. Perhaps somethong else was going on.
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

#13 Bo1965

Bo1965
  • Topic Starter

  • Members
  • 235 posts
  • OFFLINE
  •  
  • Local time:08:08 AM

Posted 06 May 2011 - 07:42 PM

Ok, with that information, things are probably better. However, I am not entirely sure that there isnt something else bugging my computer. The reason why I say that is because the minute I click into IE, my computer starts running as though I am loading a program. Also, when I run SAS immediately after logging on, I have the same adware showing up on my computer. I ran the TDDS Rootkit Removing Tool and there were no threats detected. So, after logging on, I ran another SAS and below is the result. And even now as I am typing, my processor is running as though I am downloading something.

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

Generated 05/06/2011 at 06:04 PM

Application Version : 4.51.1000

Core Rules Database Version : 7008
Trace Rules Database Version: 4820

Scan type : Complete Scan
Total Scan Time : 00:10:13

Memory items scanned : 496
Memory threats detected : 0
Registry items scanned : 12328
Registry threats detected : 0
File items scanned : 25045
File threats detected : 5

Adware.Tracking Cookie
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ad.wsod[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@doubleclick[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@imrworldwide[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@revsci[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ad.yieldmanager[1].txt

#14 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:08 AM

Posted 06 May 2011 - 08:43 PM

Did you tell SAS to ignore them?

Let do another rootkit scan as it does appear there is something hidden.

Please download Rootkit Unhooker from one of the following links and save it to your desktop.
Link 1 (.exe file)
Link 2 (zipped file)
Link 3 (.rar file)In order to use this tool if you downloaded from either of the second two links, you will need to extract the RKUnhookerLE.exe file using a program capable of extracing ZIP and RAR compressed files. If you don't have an extraction program, you can downlaod, install and use the free 7-zip utility.

  • Double-click on RKUnhookerLE.exe to start the program.
    Vista/Windows 7 users right-click and select Run As Administrator.
  • Click the Report tab, then click Scan.
  • Check Drivers, Stealth, and uncheck the rest.
  • Click OK.
  • Wait until it's finished and then go to File > Save Report.
  • Save the report to your Desktop.
  • Copy and paste the contents of the report into your next reply.
-- Note: You may get this warning...just ignore it, click OK and continue: "Rootkit Unhooker has detected a parasite inside itself! It is recommended to remove parasite, okay?".

Edited by boopme, 06 May 2011 - 08:44 PM.

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

#15 Bo1965

Bo1965
  • Topic Starter

  • Members
  • 235 posts
  • OFFLINE
  •  
  • Local time:08:08 AM

Posted 07 May 2011 - 10:00 AM

I agree with you that something is there. I woke up this morning and performed a fresh SAS and it identified 17 malware. So I know there is deffinitely something hiding. I would go a week and never see more than 2 malware before. So, I loaded the SAS log below. I have not performed the Rootkit Unhooker. I will do that when I get back. I will not be around my computer for the next couple of days so this will be my last post until I am back late Monday. I will run the Rootkit when I get back. So, please do not close this thread. I will not be able to do anything until Monday. Thanks again for all of your help and I will reply back to you on Monday with the results of the Rootkit run.


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

Generated 05/07/2011 at 08:22 AM

Application Version : 4.51.1000

Core Rules Database Version : 7009
Trace Rules Database Version: 4821

Scan type : Complete Scan
Total Scan Time : 00:11:22

Memory items scanned : 464
Memory threats detected : 0
Registry items scanned : 12328
Registry threats detected : 0
File items scanned : 25399
File threats detected : 17

Adware.Tracking Cookie
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ad.wsod[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@112.2o7[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ad.yieldmanager[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@adbrite[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ads.pointroll[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@advertising[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@atdmt[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@content.yieldmanager[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@mediabrandsww[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@doubleclick[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@imrworldwide[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@invitemedia[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@mlbam.112.2o7[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@ru4[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@pointroll[2].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@revsci[1].txt
C:\Users\Bo's\AppData\Roaming\Microsoft\Windows\Cookies\Low\bo's@tribalfusion[1].txt




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users