Jump to content
Posted 03 April 2017 - 12:54 PM
Posted 03 April 2017 - 01:54 PM
Another member had the same false positive results from Hitman Pro. Those files are actually Bit Defender files.
That member actually posted the list of files...see...HitmanPro_20170402_1726.log
If those are the same or similar to your log files then Hitman Pro needs to be notified by you of their false positives.
Posted 03 April 2017 - 02:25 PM
This is what I have received 10 minutes ago. Can you confirm these are also false positives?
Posted 03 April 2017 - 02:30 PM
Yes...the same files the other member posted that I linked to. I'll repeat the same as in that link for how to deal with those cookies.
The cookies....Third Party cookies...can easily be blocked from installing in your browsers. Once blocked, use CCleaner to remove
the existing ones. How to disable third-party cookies in all major web browsers
Use CCleaner to remove Temporary files, program caches, cookies, logs, etc. Use the Default settings. No need to use the
Registry Cleaning Tool...risky. Pay close attention while installing and UNcheck offers of toolbars....especially Google.
After install, open CCleaner and run by clicking on the Run Cleaner button in the bottom right corner.
Posted 03 April 2017 - 04:44 PM
I blocked third party cookies as instructed in my Chrome browser. Superantispyware also runs scheduled scans and removes a lot of adware cookies.
I don't have any cookies now when I ran Hitman Pro, but I still got a lot of Trojan.FakeAV. Are those false positives?
Posted 03 April 2017 - 04:51 PM
This is what I got now:
Scan date . . . . . . : 2017-04-03 18:45:00
Posted 03 April 2017 - 05:48 PM
Yes...they are false posititves. You should report this to Hitman Pro.
Posted 03 April 2017 - 09:50 PM
I experienced the same.
Like many of you, I am careful about what I download and install, and I never login as a local administrator. I also scan my system regularly with various security products. Two days ago I noticed that my daily scan with HitmanPro v 3.7.15 revealed an infection with Trojan.FaveAV. Note that full system scans run right after this detection with Zemana, Malwarebytes, EMSisoft, Bitdefender, and Kaspersky didn't discover any threats. This left me perplexed until it dawned on me that HitmanPro started detecting Trojan.FaveAV following Bitdefender installing some component updates and rebooting the system. I examined and launched a few of those "infected" files in a virtual machine, and realized that they were indeed Bitdefender components. For instance, about.exe is actually Bitdefender About Us splash screen info. Today, HitmanPro updated to 3.7.18, and a new scan didn't detect any Trojan.FaveAV. I guess this could be expected behaviors when as many of us do, run multiple security products at the same time, and some of them are bound to clash now and then. This is not the first time something similar has happened.
Edited by pincuz, 03 April 2017 - 09:51 PM.
Posted 03 April 2017 - 10:00 PM
Trojan.FakeAV was not detected by daily scans of Bitdefender Total Security 2017, Malwarebytes 3.0, Superantispyware, Adlice Rogue Killer, Sophos, Emsisoft, Zemana, Webroot and a free total system scan by Panda (which took about 3 hours). Hitman Pro still detected Trojan.FakeAV after their recent update.
Posted 03 April 2017 - 10:07 PM
This is odd. In my case, the detection stopped after the update, and those Bitdefender files that HitmanPro saw as infected before the update are no longer flagged as such. Note that those files are still present -- they weren't deleted by Hitman or by me manually. I probably need to mention that after I updated HitmanPro, I run a scan with it in Safe mode and after that it didn't detect the Trojan.FaveAV present anymore.
Posted 03 April 2017 - 10:23 PM
Latest log 5 minutes ago:
Computer name . . . . : ERNESTO-PC
Posted 04 April 2017 - 12:00 AM
Posted 04 April 2017 - 06:08 AM
Posted 04 April 2017 - 11:56 AM
I received a reply from Hitman Pro. I was asked to run the software in "forced breach" mode which terminates all processes that are not critical for Windows to operate. This was done and the trojan keeps showing up.
0 members, 0 guests, 0 anonymous users