Jump to content

Will not remove malware, Win Defender won't start, and more - FuzzMunky


Recommended Posts

I have an almost identical infection. Except the randomly generated .exe names are cokplvg.exe and vdawnke.exe. They are situation instead in AppData.

I have a dual boot hackintosh mac, so I was able to remove the items using an NTFS driver from the macOS boot. However, they soon returned the next time I logged into windows. So this isn't the root of it, that is for sure. Incidentally, the processes completely block my computer and block malwarebytes from updating. It also completely scrambled my Catalog B-tree for my Mac partitions a number of times and I had to use DiskWarrior to recover them before I could do the dual boot. 

I am yet to try the Windows Install disc repair. But I shall report back here the success if any as I'm sure this is a very very similar pathology.

 

Link to post
Share on other sites

Hi FuzzMunky :)

My name is Aura and I'll be assisting you with your malware issue. Since we'll be working together, you can call me Aura or Yoan, which is my real name, it's up to you! Now that we've broke the ice, I'll just ask you a few things during the time we'll be working together to clean your system and get it back to an operational state.

  • As you'll notice, the logs we are asking for here are quite lenghty, so it's normal for me to not reply exactly after you post them. This is because I need some time to analyse them and then act accordingly. However, I'll always reply within 24 hours, 48 hours at most if something unexpected happens
  • As long as I'm assisting you on Malwarebytes Forums, in this thread, I'll ask you to not seek assistance anywhere else for any issue related to the system we are working on. If you have an issue, question, etc. about your computer, please ask it in this thread and I'll assist you
  • The same principle applies to any modifications you make to your system, I would like you to ask me before you do any manipulations that aren't in the instructions I posted. This is to ensure that we are operating in sync and I know exactly what's happening on your system
  • If you aren't sure about an instruction I'm giving you, ask me about it. This is to ensure that the clean-up process goes without any issue. I'll answer you and even give you more precise instructions/explanations if you need. There's no shame in asking questions here, better be safe than sorry!
  • If you don't reply to your thread within 3 days, I'll bump this thread to let you know that I'm waiting for you. If you don't reply after 5 days, it'll be closed. If you return after that period, you can send me a PM to get it unlocked and we'll continue where we left off;
  • Since malware can work quickly, we want to get rid of them as fast as we can, before they make unknown changes to the system. This being said, I would appreciate if you could reply to this thread within 24 hours of me posting. This way, we'll have a good clean-up rhythm and the chances of complications will be reduced
  • I'm against any form of pirated, illegal and counterfeit software and material. So if you have any installed on your system, I'll ask you to uninstall them right now. You don't have to tell me if you indeed had some or not, I'll give you the benefit of the doubt. Plus, this would be against Malwarebytes Forums's rules
  • In the end, you are the one asking for assistance here. So if you wish to go a different way during the clean-up, like format and reinstall Windows, you are free to do so. I would appreciate you to let me know about it first, and if you need, I can also assist you in the process
  • I would appreciate if you were to stay with me until the end, which means, until I declare your system clean. Just because your system isn't behaving weirdly anymore, or is running better than before, it doesn't mean that the infection is completely gone
    This being said, I have a full time job so sometimes it'll take longer for me to reply to you. Don't worry, you'll be my first priority as soon as I get home and have time to look at your thread


This being said, it's time to clean-up some malware, so let's get started, shall we? :)

Follow the instructions in the thread below, and provide me both FRST logs (FRST.txt and Addition.txt). You can attach them in your next post, or copy/paste their content.

https://forums.malwarebytes.com/topic/9573-im-infected-what-do-i-do-now/

Link to post
Share on other sites

Here is the FRST.txt   

I do not have an Addition.txt

I can also no longer boot into the windows volume, I get a :'( emoticon symbol on a blue screen. I have tried sfc from the Windows install, and I have tried chdsk f from the Windows install. Errors are shown, but it fails at something or other. Any further hints?

Link to post
Share on other sites

Well, I can tell you that FRST took care of the infection:

"HKLM\System\ControlSet001\Services\vtzmuae" => removed successfully
C:\Windows\System32\drivers\lsbbeilo.sys => moved successfully
C:\Users\username\AppData\Local\cokplvg\corxamu.exe => moved successfully
C:\Users\username\AppData\Local\exdapto\exdapto.exe => moved successfully
C:\Users\username\AppData\Local\exdapto\vdawnke.exe => moved successfully
C:\Users\username\AppData\Local\Temp\AnonymizerGadgetSetup.1.000.1680.exe => moved successfully
C:\Users\username\AppData\Local\Temp\ing.exe => moved successfully
C:\Users\username\AppData\Local\Temp\pi.exe => moved successfully
C:\Users\username\AppData\Local\WhatsApp\Update.exe => moved successfully

As for the BSOD, were you able to boot normally before running the scan with FRST?

Link to post
Share on other sites

The very most recent time previous to doing FRST had the same BSOD, so I am not thinking FRST had anything to do with it. However previously to that it was booting fine. I deliberately asked it to go to Recovery Mode though by tapping F8. This is when the boot trouble started. I can no longer get beyond the BSOD. Frustrating.

I

Link to post
Share on other sites

Let's see if we can clean up your system a bit and see if that helps. Download the attached fixlist.txt and move it on your USB where FRST is. Then go back in the Windows RE, open the command prompt and launch FRST. This time though, click on the Fix button. Afterwards, a file called fixlog.txt will be on your USB. Attach it here.

 

fixlist.txt

Link to post
Share on other sites

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.
  • 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.