A legitimate file was inadvertently detected as 'infected', 'malicious' or 'suspicious' (also known as a False Positive or a False Alarm). Details of the database updates that contain fixes for the latest known False Positives are listed below.
False Positive Fix
In most cases, a False Positive issue is fixed in a subsequent database update; updating your F-Secure security program to use the latest database is enough to resolve the issue. Details of the update containing fixes for the latest known False Positives are listed below.
Instructions on how to check if your F-Secure security program is using the latest database update are available in Community: How do I know that I have the latest updates?
If you are certain that the file detected is a legitimate application file, you may alternatively choose to exclude it from future scans by the F-Secure security product.
More scanning & removal options
More information on scanning and removal options available in your F-Secure product can be found in the Help Center.
You may also refer to the Knowledge Base on the F-Secure Community site for further assistance.
False Positives sometimes occur if a program contains code or behavioral routines sufficiently similar to known malware to be deemed a security risk, particularly if the program uses file compression or protection utilities known to be associated with malware, or is spread through a site or distribution mechanism known to be associated with malware.
Latest False Positive Notices
- Gen:variant.jaik.11826: (20 May 2016) This detection unintentionally triggered on circuit board creation software. This issue was resolved with the 2016-05-19_09 database update released at 1313hrs UTC on 19th May 2016.
- Gen:variant.symmi.64368: (18 May 2016) This detection unintentionally triggered on a clean file. This issue was resolved with the 2016-05-17_06 database update released at 2310hrs UTC on 17th May 2016.
- Gen:variant.symmi.63701: (10 May 2016) This detection unintentionally triggered on a file related to an enterprise performance analysis suite. This issue was resolved with the 2016-05-09_09 database update released at 2258hrs UTC on 9 May 2016.
- Gen:heur.fkp.5: (updated 22 April 2016) This detection unintentionally triggered on a file related to the Steam app. This issue was resolved with the 2016-04-21_14 database update released at 0001hrs UTC on 22nd April 2016.
- Trojan.teslacrypt.gen.4: (21 April 2016) This detection unintentionally triggered on a component of the CST Studio Suite software. This issue was resolved with the 2016-04-21_09 database update released at 1040hrs UTC on 21st April 2016.