Did you just run into a download or a file on your computer that has a digital signature from Logixoft? Some of the security products refers to the detected files as MonitoringTool:Win32/RevealerKeylogger and Keylogger.Logixoft. The detection rate for the Logixoft files collected here is 32%. Please read on for more details.
You will probably see Logixoft when clicking to run the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can view the digital signature details for Logixoft with the following steps:
Here is a screenshot of a file signed by Logixoft:
As you can see in the screenshot above, the Windows OS reports that "This digital signature is OK". This means that the file has been published by Logixoft and that no one has tampered with the file.
If you click the View Certificate button shown in the screenshot above, you can view all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, etc. You can also see the address for Logixoft, such as the street name, city and country.
COMODO Code Signing CA 2 and GlobalSign CodeSigning CA - SHA256 - G2 has issued the Logixoft certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screenshot above.
These are the Logixoft files I have gathered, thanks to the FreeFixer users.
Detection Ratio | File Name |
---|---|
8/46 | rvlkl.exe |
19/54 | rvlkl.exe |
23/56 | rvlkl.exe |
11/45 | rvlkl.exe |
10/57 | rkfree_setup.exe |
18/57 | rvlkl.exe |
22/65 | rvlkl.exe |
22/61 | rvlkl.exe |
28/70 | rvlkl.exe |
Here is the detection names for the Logixoft files. I have grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
Scanner | Detection Names |
---|---|
AVG | FileRepMetagen [PUP] |
AVware | Trojan.Win32.Generic!BT |
Ad-Aware | Application.Keylogger.Revealer.B, Gen:Variant.Application.Keylogger.Revealer.2, Application.Generic.1714734, Gen:Variant.Application.Keylogger.Revealer.1 |
AegisLab | Troj.Gen|2|103!c |
Agnitum | Riskware.KeyLogger!rkYruSyBguM, Riskware.RevealKeylogger! |
AhnLab-V3 | Unwanted/Win32.Keylogger |
Antiy-AVL | Trojan/Win32.TSGeneric |
Arcabit | Trojan.Application.Keylogger.Revealer.2, Application.Generic.D1A2A2E, Trojan.Application.Keylogger.Revealer.1 |
Avast | Win32:KeyLogger-BCB [PUP] |
BitDefender | Application.Keylogger.Revealer.B, Gen:Variant.Application.Keylogger.Revealer.2, Application.Generic.1714734, Gen:Variant.Application.Keylogger.Revealer.1 |
Bkav | W64.HfsAdware.6EF2 |
CAT-QuickHeal | Trojan.ZAgent.r6, MonitoringTool.RevealerKeylog.r5 (Not a Virus), Monitoringtool.Revealerkeylogg, Trojan.IGENERIC |
Commtouch | W64/Trojan.AHYA-9280, W32/Trojan.JRNZ-7534 |
Comodo | ApplicUnsaf.Win32.KeyLogger.RevealerKeylogger.~A, UnclassifiedMalware, Malware@#cwtt29m9eetj |
Cybereason | malicious.e30063 |
Cylance | Unsafe |
Cyren | W32/Application.ROVE-2861, W32/Trojan.HHHM-4747, W32/Application.ATQH-9308 |
DrWeb | Tool.Keylog.220 |
ESET-NOD32 | a variant of Win64/KeyLogger.RevealerKeylogger.NAA, a variant of Win32/KeyLogger.RevealerKeylogger.NAA, Win32/KeyLogger.RevealerKeylogger.NAB, a variant of Win64/KeyLogger.RevealerKeylogger.A, a variant of Win32/KeyLogger.RevealerKeylogger.NAC |
Emsisoft | Win64/KeyLogger.RevealerKeylogger.AMN (A), Application.Keylogger.Revealer.B (B), Gen:Variant.Application.Keylogger.Revealer.2 (B), Application.Generic.1714734 (B), Gen:Variant.Application.Keylogger.Revealer.1 (B) |
F-Secure | Application.Keylogger.Revealer, Gen:Variant.Application.Keylogger, Application.Generic.1714734 |
Fortinet | Riskware/RevealerKeylogger |
GData | Application.Keylogger.Revealer.B, Gen:Variant.Application.Keylogger.Revealer.2, Win64.Trojan.Agent.LZLR67, Win32.Application.Agent.6INE39, Application.Generic.1714734, Gen:Variant.Application.Keylogger.Revealer.1 |
Ikarus | MonitoringTool, PUA.KeyLogger.RevealerKeylogger |
Invincea | heuristic |
K7AntiVirus | Trojan ( 004f48bc1 ), Password-Stealer ( 005081181 ) |
K7GW | Trojan ( 004f48bc1 ), Password-Stealer ( 005081181 ) |
Kaspersky | not-a-virus:Monitor.Win32.RevealerKeylogger.t |
Kingsoft | Win32.Troj.Generic.a.(kcloud) |
MAX | malware (ai score=99) |
Malwarebytes | Keylogger.Logixoft, Trojan.LogixoftKeyLogger |
McAfee | RDN/Generic PUP.x!bwd, Artemis!AE543176A07B, Artemis!4EDF4E1749CD, Artemis!048816370922, Artemis!AE0C32FF5DF5, Artemis!92C9701FABCC, Artemis!229A707E3006 |
McAfee-GW-Edition | RDN/Generic PUP.x!bwd, Artemis!PUP, Artemis!4EDF4E1749CD, Artemis |
MicroWorld-eScan | Application.Keylogger.Revealer.B, Gen:Variant.Application.Keylogger.Revealer.2, Application.Generic.1714734, Gen:Variant.Application.Keylogger.Revealer.1 |
Microsoft | MonitoringTool:Win32/RevealerKeylogger |
NANO-Antivirus | Trojan.Win32.XPACK.czfvpv |
Paloalto | generic.ml |
Panda | Suspicious file, PUP/RevealerKeylogger, Trj/CI.A |
Qihoo-360 | Win32/Application.Keylog.f6e, Win32/Application.Keylog.773 |
Rising | Spyware.RevealerKeylogger!8.44C0-JqwXNTuIwqR (cloud), Malware.MonitoringTool!8.653 (cloud:JYoBHXCS5JR), Malware.RevealerKeylogger!8.E946 (CLOUD) |
SUPERAntiSpyware | Trojan.Agent/Gen-Logixoft, Spyware.RevealerKeylogger |
Sophos | Revealer Keylogger Installer, Revealer Keylogger (PUA), Generic PUA GD (PUA), Generic PUA OG (PUA) |
Symantec | WS.Reputation.1, Trojan.Gen.2, Spyware.RevealerKeylog, Trojan.Gen.8!cloud |
Tencent | Win64.Risk.Keylogger.Eom, Win32.Risk.Keylogger.Lmum, Win64.Risk.Keylogger.Htvt, Win32.Risk.Keylogger.Hqby |
TrendMicro | HKTL_KEYLOG |
TrendMicro-HouseCall | TROJ_GEN.F47V0504, HKTL_KEYLOG, TROJ_GEN.F47V0510, Suspicious_GEN.F47V0323 |
VIPRE | Trojan.Win32.Generic!BT |
ViRobot | Trojan.Win32.Z.Revealerkeylogger.492104[h], Adware.Revealerkeylogger.481184 |
Webroot | System.Monitor.Revealer.Keylogg |
Zillya | Backdoor.PePatch.Win32.74777 |
The detection percentage is based on the fact that I have gathered 511 scan reports for the Logixoft files. 161 of these scan results came up with some sort of detection. If you like, you can view the full details of the scan results by examining the files listed above.
The analysis has been done on certificates with the following serial numbers: