Jump to content

Keepass As W32.crypt


dgcombs

Recommended Posts

Hi,

recently updated my keepass to version 1.19b on Windows-7 (64bit). Immunet barked at me and immediately quarantined the file keepass.exe claiming it was identified as W32.Crypt. I have checked the same file with Avast and it doesn't get excited. I also downloaded the 1.18 version of Keepass and it comes away with a clean bill of health.

 

False Positive? Or should someone warn the good folks at Sourceforge/Keepass?

Dan

Link to comment
Share on other sites

Guest Orlando

Hi,

 

I downloaded the KeePass 1.19b by here and do a scan with the Free version and it isn't detected, have you got the Plus version?

 

Can you post here the link of your download link?

 

Orlando

Link to comment
Share on other sites

I downloaded the KeePass 1.19b by here and do a scan with the Free version and it isn't detected, have you got the Plus version?

 

Can you post here the link of your download link?

 

Interesting. I downloaded from that same link. I tested using the ZIP file from that link as well. My Immunet is the free version 3.0.1.6112.

Link to comment
Share on other sites

Guest Orlando

You should clean you History, please use Immunet Protect Fix Tool to fix it or do it manually.

 

Manually:

 

Start CMD as Administrator and type:

 

1) net stop immunetprotect

2) del ...\Immunet\history.db

3) del ...\Immunet\historyex.db

4) del ...\Immunet\cache.db

5) net start immunetprotect

 

Orlando

Link to comment
Share on other sites

You should clean you History, please use Immunet Protect Fix Tool to fix it or do it manually.

 

Manually:

 

Start CMD as Administrator and type:

 

1) net stop immunetprotect

2) del ...\Immunet\history.db

3) del ...\Immunet\historyex.db

4) del ...\Immunet\cache.db

5) net start immunetprotect

 

This is getting very interesting. I did as you suggested and removed the History information. I then started Immunet and rescanned the downloaded ZIP file. The scanner popped back with a clean bill of health. But the on-access portion popped up and announced (again) W32.Crypt in inside the ZIP file and quarantined the zip file.

 

I think I'll stay at version 1.18 for the time being.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...