Home > Threat descriptions >

False Positive

Classification

Category: Malware

Type: Other

Aliases: False Positive (FP), False Alarm (FA)

Summary


Security programs will sometimes unintentionally identify a program or file as harmful if it has code or behavior that resembles known harmful programs. This is known as a False Positive.

See the Technical Details section for a list of the latest known False Positives, and the relevant remedial database updates.

Removal


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. You can take the following actions to handle a False Positive:

  • Check for a fix

    To check if your F-Secure security program is using the latest database update, see: Community: How do I know that I have the latest updates?

  • Submit a sample

    After checking, if you still believe the file is incorrectly detected, you can submit a sample of it to F-Secure Labs for re-analysis.

    NOTE If the file was moved to quarantine, you will need to first collect the file from quarantine before you can submit it.

  • Exclusion

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

Knowledge Base

Find the latest advice in our Community Knowledge Base.

About the product

See the manual for your F-Secure product on the Help Center.

Contact Support

Chat with or call an expert for help.

Submit a sample

Submit a file or URL for further analysis.

Technical Details


False Positives sometimes occur if a program or file contains code or behavior that is similar to known harmful programs. 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 programs.

Latest False Positive Notices
  • Trojan.GenericKD.40929615
    (10 Jan 2019) This detection unintentionally triggered on a Windows Update file. This issue was resolved with the 2019-01-10_08 database update released at 1922hrs UTC on 10th January 2019.
  • Trojan.Agent.DNAY:
    (9 Jan 2019) This detection unintentionally triggered on a Windows Update file. This issue was resolved with the 2019-01-09_01 database update released at 0403hrs UTC on 9th January 2019.
  • Trojan:W32/GenericSuspExecution.A!DeepGuard:
    (8 Jan 2019) This detection unintentionally triggered on the cmd.exe file. This issue was resolved with the 2019-01-08_01 database update released on 8th January 2019.
  • Gen:Variant.Symmi.83823:
    (21 Dec 2018) This detection unintentionally triggered on a DLL file associated with the Cisco Jabber program. This issue was resolved with the 2018-12-20_13 database update released at 2200hrs UTC on 20th December 2018.
  • Trojan.Agent.DHKL:
    (25 October 2018) This detection unintentionally triggered on a Chrome browser extension that makes changes to the browser homepage. This issue was resolved with the 2018-10-25_06 database update released at 1113hrs UTC on 25th October 2018.

Date Created: -

Date Last Modified: -