False Positive

Threat description

Details

CATEGORYMalware
TYPEOther

Summary

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 update that contain fixes for the latest known False Positives are listed below.

Removal

False Positive Fix

In most cases, a False Positive 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?

Exclusion

If you are certain that the file detected is a legitimate application or file, you may choose to exclude it from further scanning by the F-Secure security product.

More scanning & removal options

More information on the 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.

Technical Details

False Positives sometimes occur if a program or file contains code or behavior that is similar to known harmful files. This is especially likely if the program or file uses compression or protection techniques, or is spread using a distribution method, that are commonly used by harmful files.

Latest False Positive Notices
  • Gen:Variant.Symmi.79796: (15 November 2017) This detection unintentionally triggered on game-related files. This issue was resolved with the 2017-11-14_12 database update released at 2116hrs UTC on 14th November 2017.
  • Gen:Trojan.Heur.LP.Gu4@au!GKwg: (11 November 2017) This detection unintentionally triggered on temp files related to a popular multiplayer game. This issue was resolved with the 2017-11-07_01 database update released at 0056hrs UTC on 11 November 2017.
  • JS:Trojan.JS.ExploitKit.A: (2 Nov 2017) This detection unintentionally triggered on a JavaScript file. This issue was resolved with the 2017-11-01_03 database update released at 1142hrs UTC on 1st November 2017.
  • Gen:Trojan.Heur.LP.Gu4@aepARUh: (19 Oct 2017) This detection unintentionally triggered on game-related files. This issue was resolved with the 2017-10-19_04 database update released at 0748 UTC on 19 Oct 2017.
  • Gen:Variant.Johnnie.27178: (17 July 2017) This detection unintentionally triggered on game-related files. This issue was resolved with the 2017-07-16_18 database update released at 2309hrs UTC on 16th July 2017.

Submit a Sample

Suspect a file or URL was wrongly detected?
Send it to our Labs for further analysis

Submit a Sample

Give And Get Advice

Give advice. Get advice. Share the knowledge on our free discussion forum.

More Info