Yes, it’s a false positive. KeePass is safe. Hope they correct it soon.
You can disable WebShield while downloading and installing or, better, wait to install after they correct the false positive detection.
Getting seriously tired of this. This AV has a serious hardon for W32 Trojans - and they’re ALL WRONG. PSPAad, HTTrack, various other open source projects - it spots all of them as Trojans. This is not the first time this nonsense has happened and it’s always with the same malware suspicion. I know they’re wrong because I can scan the same files with other products including Symantec and McAfee 9horrors!) and they come up CLEAN. The mess started with the last set of updates a couple of minutes ago.
I’d suggest the virus string engineers get their act together and test more comprehensively or I’ll be moving to antivir. I’d further suggest that a new crop of definition be releases with 60 minutes to remedy this mess.
wow, I just tried to download the V2 alpha: it’s a no go. Also detected as a virus, and Avast database has been updated after a rather unusual short interval this time, just a couple of minutes before I tried this download (and only 3 hours after the last update on Sunday evening (here in Europe).
for those having the issue, just deactivate Avast during the download of Keepass, install it and reactivate Avast, as it has no issue with the program itself, only with the setup file.
oh I forgot, on Virus Total, PrevX also thinks Keepass 1.10 is a virus. That’s a false positive as well no question about that but there must be something in the structure of that file that bring those alerts, just like the Eicar file does ;D. I read some old versions of Keepass like 1.07 already gave false positive with anti-virus software.
That may work for the installation of Keepass but it won’t work for my library of freeware tools, most of which are open source and defiintely free of virii. Many of these are incorrectly being reported as ridden with w32 trojan. Given that i’ve had this happen before with avast! and with this same torjan alert, I seriously doubt their virus engineers would recognize w32 trojan if it reached up and bit them in the ass.
it’s getting worrying, as files wrongly detected get blocked by Avast, even when you answer “no action”. And deactivating the shield each time those files are needed is no solution.
already the third update in less than 24 hours and Keepass setup file is still considered as a virus. My system is not affected by false positive detection of virii on system files so far.
as long as a couple of setup files are affected, it’s not a problem, but if some system files (like user32.dll) or program files start to be detected as well, then it’s more serious and would require a complete deactivation of Avast AV, at least until the database is good again. It hasn’t happened on my system so far (concerning windows files), but if it did I’d switch immediately to another antivirus.