Trojan:W32/VBKrypt, Trojan:W32/VBKrypt, Gen:variant.vbkrypt.39 Gen:variant.vbkrypt.1 Trojan.Win32.VBKrypt


Trojan:W32/VBKrypt is a large family of trojans written in Visual Basic.

Automatic action

Based on the settings of your F-Secure security product, it will either move the file to the quarantine where it cannot spread or cause harm, or remove it.

Suspect a file is incorrectly detected (a False Positive)?

A False Positive is when a file is incorrectly detected as harmful, usually because its code or behavior resembles known harmful programs. 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 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.

    Note You need administrative rights to change the settings.

For more Support

Knowledge Base

Find the latest advice in our Community Knowledge Base.

User Guide

See the user guide for your 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

Based on the specific variant, the trojan may drop files, write to the registry and perform other unauthorized actions on the affected computer system.


the Generic DetectionsGen:variant.vbkrypt.39 and Gen:variant.vbkrypt.1 identify suspect files which appear to share the same characteristics or behaviors as a malicious Trojan:W32/VBKrypt file.

If you believe a file which has triggered one of these detections is in fact clean - i.e., that it is a False Positive - please submit a sample of the suspect file to our Submit A Sample (SAS) page for analysis.

Please specifying that you are submitting a false positive. Any additional information such as the origin of the file, scanning report file, and false positive detection name will help to resolve the issue more quickly.