Jump to content
wep

MB endpoint is detecting Trojan.0Access

Recommended Posts

MB was detecting Trojan.0Access and Trojan.Poweliks.B but wont quarantine. I manually deleted Trojan.Powliks.B and it is not showing up on scan anymore. Trojan.0Access is still being detected. I saw some posts about this nut hey are from a few years ago. Is there a more up to date way to remove it? Thanks for any help.

Share this post


Link to post
Share on other sites

Hello, Welcome to Malwarebytes.
I'm nasdaq and will be helping you.

If you can please print this topic it will make it easier for you to follow the instructions and complete all of the necessary steps in the order listed.
===

Download the Farbar Recovery Scan Tool (FRST).
Choose the 32 or 64 bit version for your system.
and save it to a folder on your computer's Desktop.
Double-click to run it. When the tool opens click Yes to disclaimer.
Press Scan button.
It will make a log (FRST.txt) in the same directory the tool is run. Please copy and paste it to your reply.
The first time the tool is run, it makes also another log (Addition.txt). Please attach it to your reply.

How to attach a file:
In the Reply section in the bottom of the topic Select Click the Choose a File.
Navigate to the location of the File.
Click the file. It will appear in section.
Click the Saving button.

Please post the logs for my review.

Wait for further instructions
====

Share this post


Link to post
Share on other sites

Thanks for the help. I was not on site yesterday. My co-workers decided to reformat the hard drive before I could run the FRST. 

Share this post


Link to post
Share on other sites

Hi,

Thanks for the information.

The topic will be closed.

Share this post


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.

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