False Positive

Classification

Malware

Other

W32

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

A False Positive will usually be fixed in a subsequent database update without any action needed on your part. If you wish, you may also:

  • Check for the latest database updates

    First check if your F-Secure security program is using the latest detection database updates, then try scanning the file again.

  • 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 need to collect the file from quarantine before you can submit it.

  • Exclude a file from further scanning

    If you are certain that the file is safe and want to continue using it, you can exclude it from further scanning by the F-Secure security product.

Find out more
Knowledge Base

Find the latest advice in our Community Knowledge Base.

Product Manual

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: -