MBAM detected PUP WhiteSmoke.A

Viruses and worms
1

Hello. Last night MBAM detected WhiteSmoke.A. I think it was associated with Chrome (I never use Chrome, normally just Firefox, this must have been here for a while).
I let MBAM clean what it found (and apparently the log got deleted by CCleaner right afterwards)
I uninstalled WhiteSmoke.B from Chrome and then uninstalled Chrome.
Subsequent MBAM runs were all clean
I initiated aswMBR and it found nothing wrong with the MBR, so I quit it
I ran AdwCleaner (logs attached)
I just ran OTL, logs attached

I did a avast! IS boot scan this weekend, and it was clean. I am going to run SpyBot and then another bootscan

Am I clean, or is there anything else I should do. Thanks!

2

I’m on it.
May you attach aswMBR log as well please?

3

I did not do the whole, thing I shut it down as soon as I saw it had a clean MBR.

4

Here is the MBR scan. It is clean.

5

@leftisthominid

Last night MBAM detected WhiteSmoke.A. I think it was associated with Chrome (I never use Chrome, normally just Firefox, this must have been here for a while). I let MBAM clean what it found (and apparently the log got deleted by CCleaner right afterwards) I uninstalled WhiteSmoke.B from Chrome and then uninstalled Chrome. Subsequent MBAM runs were all clean

You done it right. Good job. Posted OTL log looks good, nothing to fix. You are good to go. :wink:
The only thing I see in the logs are temp files. There is nothing wrong with that but we shall clean temp from all files with OTL when you’re here.
P.S: You might wanna disable Malwarebytes as it may know to mess with OTL while trying to clean temp.

Re-run OTL.exe.

[*]Copy and paste the following text written inside of the quote box into the Custom Scans/Fixes box.

:COMMANDS
[EMPTYTEMP]

[*]Then click the Run Fix button at the top.
[*]Let the program run unhindered; it will reboot the system when it is done and open notepad with logreport. Attach here that logreport.

And that’s it.

I did not do the whole, thing I shut it down as soon as I saw it had a clean MBR.

There is always a reason why we ask our logs, it’s not because of our caprice.

aswMBR not only read the MBR but it carried out a lot more as it scan partitions, check partitions type,
it call some modules and displays them, scan services & drivers by himself + later on it use avast engine to scan the same and finally it create MBR dump for possible examining.

aswMBR is an Anti Rootkit based tool, what purpose tool would have if only try to read MBR? :slight_smile:

Cheers. :slight_smile:

6

Here is the log, looks clean

Thanks for all the help!