Malwarebytes Acquires AdwCleaner  

New Version of AdwCleaner out
Version: v6.041 - 16/12/16
See first post for changelog

Thanks Cliff, just got it :)

DooGie said:

Thanks Cliff, just got it :)

You're welcome:)

Cliff, I know this is your announcement thread, please pardon, but I just DL'd the new one and ran. Analyzed only because what it found (other than the normal aol and ask garbage), looked suspect to me. It's now flagging Auslogics? And what appears to be part of Patch Tuesday (because of date) or that last Cumulative last week? Have not deleted anything, yet. Need some opinions, please. TC

For Auslogics I found: AdwCleaner FP with Auslogics Disk Defrag - Malwarebytes AdwCleaner - Malwarebytes Forums

Cliff S said:

For Auslogics I found: AdwCleaner FP with Auslogics Disk Defrag - Malwarebytes AdwCleaner - Malwarebytes Forums

Thanks, Cliff. MB3 started doing a PUP on it, so I guess it follows ADW would, too. Seems some of the criteria for PUPs is 2nd and 3rd party "requests". Not all PUPs are PUPs, hence the word "potentially".

Just run a scan with it and it found C: /Program files/Windows Security folder and flagged 13 Registry entries associated with it.
Folder has 2 files:
BrowserCore.exe
manifest.json
Quick search thru registry showed it was associated with some children oriented site that was accessed few month ago by some friend's kids visiting few month ago. Earlier versions didn't flag it.
Internet search showed "manifest.json" to be part of FF up to version 48.0.
Cleaned successfully.

CountMike said:

Just run a scan with it and it found C: /Program files/Windows Security folder and flagged 13 Registry entries associated with it.
Folder has 2 files:
BrowserCore.exe
manifest.json
Quick search thru registry showed it was associated with some children oriented site that was accessed few month ago by some friend's kids visiting few month ago. Earlier versions didn't flag it.
Internet search showed "manifest.json" to be part of FF up to version 48.0.
Cleaned successfully.

Thank you, Count! My results were the same. Thanks for the research, now I will clean! :)

The usual Chrome intrusions.....