wmcagent.exe & associated malware

[sgt_flippy]

After trying to install a program from a third party website my PC got a virus. At first I recognized something was wrong because a bunch of random desktop apps appeared and my browser (chrome) redirected to yahoo when I tried to search up "Bitdefender". I also began to see "wmcagent.exe", and processes consisting of random letters in task manager. I uninstalled any suspicious programs and deleted chrome and ran scans from HitmanPro, Kaspersky, and Malwarebytes. At first i tried to delete the "wmcagent" folder in AppData/Local (and suspicious files 'mbdrklu" and "scrxmpt") but it gave the message "access is denied." I tried to change the permissions of the folder, 'access is denied." I tried to force kill the "wmcagent.exe" process using Command Prompt but it again said "access is denied." There are multiple other folders that I cannot delete that look suspicious in AppData/Local. As mentioned before, I  then used various anti-malware programs but none were able to remove the malware folders/files upon reboot. I've tried using multiple of those programs but none can remove the "wmcagent.exe" processes. which still appear. 

I've been able to delete some malware files when I run anti-malware, maybe they stopped their process just to trick the program. Also, once when I was able to get into the malware folder and changed the malware.exe file to "thisismalware.exe", the description of the malware process in task manager changed to "thisismalware". 

 

Any help would be greatly appreciated!

[sgt_flippy]

Also, kaspersky stopped a malicious link several times called "http://freshrefreshnerer24rb.info/192h4mjie.pkh

 

There is also a malware detected in system32/driver and something in system memory. Thanks.

[sgt_flippy]

Forgot to add this earlier: My PC is Windows 7 x64

[sgt_flippy]

I downloaded and ran FRST. Here are the FRST.txt and Addition.txt files. 

Addition.txt

FRST.txt

[AdvancedSetup]

Hello @sgt_flippy and

 

Please run the following steps and post back the logs as an attachment when ready.

STEP 01

• If you're already running Malwarebytes 3 then open Malwarebytes and check for updates. Then click on the Scan tab and select Threat Scan and click on Start Scan button.
• If you don't have Malwarebytes 3 installed yet please download it from here and install it.
• Once installed then open Malwarebytes and check for updates. Then click on the Scan tab and select Threat Scan and click on Start Scan button.
• Once the scan is completed click on the Export Summary button and save the file as a Text file to your desktop or other location you can find, and attach that log on your next reply.
• If Malwarebytes won't run then please skip to the next step and let me know on your next reply.

STEP 02

Please download AdwCleaner by Malwarebytes and save the file to your Desktop.

• Right-click on the program and select Run as Administrator to start the tool.
• Accept the Terms of use.
• Wait until the database is updated.
• Click Scan.
• When finished, please click Clean.
• Your PC should reboot now if any items were found.
• After reboot, a log file will be opened. Copy its content into your next reply.

 

RESTART THE COMPUTER Before running Step 3

STEP 03
Please download the Farbar Recovery Scan Tool and save it to your desktop.

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

• Double-click to run it. When the tool opens, click Yes to disclaimer.
• Press the Scan button.
• It will make a log (FRST.txt) in the same directory the tool is run. Please attach it to your reply.
• The first time the tool is run, it also makes another log (Addition.txt). If you've, run the tool before you need to place a check mark here.
• Please attach the Additions.txt log to your reply as well.

 

Thanks

Ron

 

[sgt_flippy]

Hi Ron,

Here are the files. Thanks for helping!

Addition.txt

AdwCleaner[S00].txt

FRST.txt

malwarebytes.txt

[AdvancedSetup]

Yes, the computer is infected with a rootkit.

Let's see if the following can remove it. Please run the following

 

 

Also, are you programming in Java? You have a bunch of old compromised versions of Java running on the system.

Java 7 Update 67
Java 8 Update 162
Java SE Development Kit 8 Update 162
Java(TM) 6 Update 17

If you're not programming I'd recommend you uninstall all of these versions after we're done cleaning.

Thanks

Ron

 

 

[sgt_flippy]

Malwarebytes Anti-Rootkit wasn't able to find any malware. Here are the log files. I'm pretty sure the rootkit is in the system32/driver folder.

mbar-log-2018-04-13 (00-16-29).txt

system-log.txt

Edited April 13, 2018 by sgt_flippy

[AdvancedSetup]

Farbar Recovery Scan Tool (FRST) - Fix mode
Follow the instructions below to execute a fix on your system using FRST, and provide the log in your next reply.

• Right-click on the FRST executable and select Run as Administrator (for Windows Vista, 7, 8, 8.1 and 10 users)
• Copy/paste the following inside the text area:

  Start::
  CMD: bcdedit.exe /set {bootmgr} displaybootmenu yes
  CMD: bcdedit.exe /set {default} recoveryenabled yes
  End::
  

• Click on the Fix button
  
• On completion, a message will come up saying that the fix has been completed and it'll open a log in Notepad
• Copy and paste its content in your next reply

 

Thanks

Ron

 

[sgt_flippy]

When I click fix, FRST says "no fixlist.txt found"

[AdvancedSetup]

Did you copy and paste into the text box area before clicking FIX?

 

Start::
CMD: bcdedit.exe /set {bootmgr} displaybootmenu yes
CMD: bcdedit.exe /set {default} recoveryenabled yes
End::

 

 

 

Edited April 13, 2018 by AdvancedSetup

[sgt_flippy]

Yes. I started FRST as admin, then copypasted the commands into the text box. After clicking "fix", the error popped up. 

[AdvancedSetup]

Okay, do you have access to a clean computer?

 

[sgt_flippy]

Yes I do

[AdvancedSetup]

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.

 
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.

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

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 D: 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  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.

 

[sgt_flippy]

I do not have an 8 gb USB on hand right now. Should I procure one and follow the steps? That may take some time. 

[AdvancedSetup]

If your computer already has built-in Recovery Environment that you can boot into then you only need a very small USB stick to hold the fixlist text file 

Let me know

 

[sgt_flippy]

It appears the computer cannot access the recovery environment - it needs me to insert windows installation disc. I do not have the disk anymore as it has been many years. 

 

I saw on another thread w/ similar problems that the same FRST commands were entered into command prompt. Is that an option for my case? 

[AdvancedSetup]

The issue is that this rootkit is aware we are trying to remove it so it is monitoring and corrupting content.

Please get the 8GB USB  stick and build it as shown above. 

Thank you

Ron

 

[sgt_flippy]

Alright. I will buy it tomorrow. Will you still be able to help me once I have completed the above step?

[AdvancedSetup]

Yes, we should be able to get it removed using the method above.

I'll check back on you again sometime tomorrow.

Ron