Jump to content

Web Protection won't turn on - infected


Recommended Posts

@newsma it appears that your system has crashed recently.  My suspicion is that this might be part of the trouble in your case.  If you would, please move or copy the following files to your desktop:

C:\WINDOWS\Minidump\062018-18171-01.dmp
C:\WINDOWS\MEMORY.DMP

Then select them both and right-click on one of them and hover your mouse over Send to and select Compressed (zipped) folder then attach the resulting ZIP archive to your next reply or, if it's too large, upload it to WeTransfer.com and select the free option then click the ... button and beneath where it says Send as select Link.  Below is an image of what the ... button looks like so you don't miss it:

WT1.png.07423d0a4c57ec56743e60543713471b.png

Once that's done, click the ... button once more to return to the previous screen and click the + button next to Add your files then browse to your desktop and select the ZIP folder you created with the memory dumps in it and upload it.  Once it completes it should provide you with a download link, copy and paste it into your next reply.

@OzMerry how are things going?  Is Malwarebytes working properly now?  If not, there are a couple more things I see in your logs that we might need to check.

First, you have mbam.exe configured to run as administrator in its compatibility settings, but this shouldn't be necessary so I'd recommend resetting it to default by navigating to C:\Program Files\Malwarebytes\Anti-Malware and locating mbam.exe then right-clicking on it and selecting Properties, then click the Compatibility tab and uncheck the box next to Run this program as an administrator then click Apply then OK.

Once that's done, right-click on the Malwarebytes tray icon and select Quit Malwarebytes then click Yes if prompted by User Account Control, then launch Malwarebytes again normally by double-clicking the Malwarebytes desktop shortcut or START menu shortcut.  Check to see if that helped at all.

If it didn't, there's one more thing I see that has me concerned:

C:\WINDOWS\system32\DRIVERS\SETD743.tmp                                               > \C:\WINDOWS\system32\DRIVERS\mwac.sys
C:\WINDOWS\system32\DRIVERS\SET199B.tmp                                               > \C:\WINDOWS\system32\DRIVERS\mwac.sys
C:\WINDOWS\system32\DRIVERS\SET6328.tmp                                               > \C:\WINDOWS\system32\DRIVERS\mwac.sys
C:\WINDOWS\system32\DRIVERS\SET67BC.tmp                                               > \C:\WINDOWS\system32\DRIVERS\farflt.sys
C:\WINDOWS\system32\DRIVERS\SET73F1.tmp                                               > \C:\WINDOWS\system32\DRIVERS\mbam.sys
C:\WINDOWS\system32\DRIVERS\SETEA1B.tmp                                               > \C:\WINDOWS\system32\DRIVERS\mwac.sys
C:\WINDOWS\system32\DRIVERS\SETED09.tmp                                               > \C:\WINDOWS\system32\DRIVERS\farflt.sys
C:\WINDOWS\system32\DRIVERS\SETFA96.tmp                                               > \C:\WINDOWS\system32\DRIVERS\mbam.sys
C:\WINDOWS\system32\DRIVERS\SETE350.tmp                                               > \C:\WINDOWS\system32\DRIVERS\mwac.sys
C:\WINDOWS\system32\DRIVERS\SETE61F.tmp                                               > \C:\WINDOWS\system32\DRIVERS\farflt.sys
C:\WINDOWS\system32\DRIVERS\SETF3EA.tmp                                               > \C:\WINDOWS\system32\DRIVERS\mbam.sys

Those are all Malwarebytes drivers which were installed and needed to rename themselves on reboot to complete the process.  The drivers you have installed are correct, so it shouldn't be an issue, but I am wondering why those Pending File Rename Operations entries were left behind in the registry and my suspicion is that maybe it was because Kaspersky might have blocked them from being processed/deleted normally as they should be but I don't know for certain.  You have many leftover entries there, not just from Malwarebytes, but also some other programs so something may be interfering with the normal processing of such entries (Windows is supposed to process those entries on reboot and then delete them once they are completed, but instead they got left behind).  If the trouble continues, I'd suggest maybe disabling Kaspersky temporarily then performing a clean reinstall of Malwarebytes to see if that resolves the issue:

  1. Download and run the Malwarebytes Support Tool
  2. Accept the EULA and click Advanced Options on the main page (not Get Started)
  3. Click the Clean button, and allow it to restart your system and then reinstall Malwarebytes, either by allowing the tool to do so when it offers to on restart, or by downloading and installing the latest version from here

Link to post
Share on other sites

  • Root Admin

Hello @newsma

Pleases run the following to remove this rootkit infection.

 

If your computer does not have the Windows Recovery Environment installed and available you can use the following method to run the Recovery Environment from a bootable USB disk.

NOTE: This USB disk needs to be created from a clean computer. You cannot use an infected computer for this process

NOTE: An 8GB USB 2.0 stick is required or at least recommended. In some cases a USB 3.0 disk can be used but some computers have issues booting from USB 3.0 disks.

Example drive (no endorsement implied, example only) - This drive example has not been tested by me. It is an older 2015 model with many good reviews though.
Amazon: Kingston 8GB DataTraveler 101 G2 USB 2.0 Flash Drive (DT101G2/8GBZ)
NewEgg: Kingston 8GB DataTraveler 101 G2 USB 2.0 Flash Drive (DT101G2/8GBZ)


STEP 1
Download a Windows 10 ISO image from Microsoft.

Method A: Using the Microsoft Media Creation Tool
https://www.microsoft.com/en-gb/software-download/windows10
Download the Media Creation Tool: https://go.microsoft.com/fwlink/?LinkId=691209

Follow the instructions displayed on the tool to download the Windows 10 ISO image.

In my testing I was not prompted for a license key to download the latest Windows 10 ISO image.
At the time of this writing 2017/12/21 there was only one ISO image offered. Windows 10

32-bit x86  or  64-bit x64

Note: You need to run the version compatible with your system.
You can check here if you're not sure if your computer is 32-bit or 64-bit
 

Method B: If Method A: above is not working for you then you can try the following method
Microsoft Windows and Office ISO Download Tool (this is not an authorized Microsoft tool, but appears to be legal)
https://www.heidoc.net/joomla/technology-science/microsoft/67-microsoft-windows-and-office-iso-download-tool
Download: https://www.heidoc.net/php/Windows%20ISO%20Downloader.exe

STEP 2
If you were unable to use the Windows Media Creation Tool in STEP 1 to create a USB disk then you can use this tool to burn the Windows 10 ISO image from STEP 1 above.

Download the Windows USB/DVD Download Tool from Gitbub and save to your computer.
English version: https://github.com/mantas-masidlauskas/wudt/raw/master/Downloads/Windows7-USB-DVD-Download-Tool-Installer-en-US.exe

Then install the Windows USB/DVD Download Tool and run it to burn a bootable USB disk from the ISO image. Browse to the location where you saved the Windows 10 ISO image in STEP 1
Note: This tool should work on XP, Vista, Windows 7, or Windows 10 - it is simply used to make a bootable USB disk. Remember, all of this needs to be done on a clean computer.

MCWx4mf.jpg

5IvFX1o.jpg

1hzeggf.jpg

g1iLLSH.jpg

KkzebK6.jpg

 
STEP 3
Please download the Farbar Recovery Scan Tool and save it to your desktop or other location you know where it's saved to. Then copy it to the USB disk you just created.

Note: You need to run the version compatible with your system.
You can check here if you're not sure if your computer is 32-bit or 64-bit

STEP 4
Shut down the infected computer. Do Not insert the USB disk you created until the infected computer has been shut down.
Once the computer is shut down then insert the newly created Windows 10 USB disk into the infected computer and power it back on and press the appropriate key to bring up the boot menu. The link below will help show you which key for various computers manufacturers is used to bring up the boot menu. Most will be either USB or UEFI depending on hardware and settings. If the computer boots up into the Normal Windows instead of the USB stick it may become infected and need to be completely redone again. Make sure you select the correct boot option.

How to Boot Your Computer from a USB Flash Drive

STEP 5
Once the computer starts to boot up from the USB disk, follow the screens and directions below.

Gvt31DC.jpg

wk8hs0E.jpg

F2gCAoF.jpg

X8NEEvb.jpg

You will need to open NOTEPAD.EXE to help find out which drive is your Windows drive and which drive is your USB disk drive you just created

O27kz3e.jpg

RRI6og4.jpg

For the more advanced user you could also use DISKPART to help locate which drive is mapped to your USB disk. In most cases the USB disk will be either ? or E: but depending on hardware the drive could be a much higher level such as H: or higher.

Example only - your hardware will look different

DISKPART> list volume
	  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     Z                       DVD-ROM         0 B  No Media
  Volume 1     C                NTFS   Partition    931 GB  Healthy    System
  Volume 2     Q   SEA-USB-4.0  NTFS   Partition   3725 GB  Healthy
  Volume 3     D                NTFS   Removable   7636 MB  Healthy


Go back to the DOS Command Prompt (if you used DISKPART type in Exit and press the Enter key) and type in the following and press the Enter key.

CD /D  ? (or E: or whichever drive letter the USB stick is on)

Then type in CD\
and press the Enter key to get to the root or top of the USB disk.

Then type in FRST   or   FRST64  (depending on which version your computer uses) and click the Scan button.

A log called FRST.txt will be saved on your USB Flash Drive. Attach it in your next reply.

If all went well you should now be able to boot into Normal Mode and run Malwarebytes and run a Threat Scan to have it finish the removal process.

 

Link to post
Share on other sites

  • 3 weeks later...
  • Root Admin

Due to the lack of feedback, this topic is closed to prevent others from posting here.

If you need this topic reopened, please send a Private Message to any one of the moderating team members. Please include a link to this topic with your request.

This applies only to the originator of this topic. Other members who need assistance please start your own topic in a new thread.

Thanks

 

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.