Did you just download a file that is digitally signed by LogMeIn, Inc. and wonder if the file is safe? If that's the case, please read on.
You will typically see LogMeIn, Inc. when running the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screencap shows:
You can view additional details from the LogMeIn, Inc. certificate with the following steps:
Here's a screengrab of a file digitally signed by LogMeIn, Inc.:
As you can see in the screenshot above, Windows reports that "This digital signature is OK". This means that the file has been published by LogMeIn, Inc. and that the file has not been tampered with.
If you click the View Certificate button shown in the screenshot above, you can examine 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 examine the address for LogMeIn, Inc., such as the street name, city and country.
VeriSign Class 3 Code Signing 2009-2 CA, VeriSign Class 3 Code Signing 2004 CA, VeriSign Class 3 Code Signing 2010 CA, DigiCert SHA2 Assured ID Code Signing CA, DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 and Symantec Class 3 SHA256 Code Signing CA has issued the LogMeIn, Inc. certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screenshot above.
The following are the LogMeIn, Inc. files I've collected, thanks to the FreeFixer users.
The FreeFixer tool treats files from LogMeIn, Inc. as trusted, which means that the LogMeIn, Inc. files will appear with a green background and that there is no removal checkbox for the file. However, as you can see in the scan results below, a few of the anti-virus scanners detects the LogMeIn, Inc. file(s). My guess is that those detections are false positives and that the files are safe. It's unlikely that LogMeIn, Inc. would ship a malware file.
Detection Ratio | File Name |
---|---|
1/48 | LMIinit.dll |
4/41 | RAinit.dll |
1/57 | lmi_rescue_srv.exe |
1/65 | g2mupdate.exe |
1/47 | unattended_srv.exe |
1/70 | g2mupdate.exe |
2/69 | g2mupdate.exe |
1/70 | g2svc.exe |
0/45 | LMIinit.dll |
0/48 | LMIinit.dll |
0/48 | LMIinit.dll |
0/47 | LMIinit.dll |
0/46 | lmirfsdriver.sys |
0/46 | Support-LogMeInRescue.exe |
0/51 | lmiguardiansvc.exe |
0/47 | LMIinit.dll |
0/47 | LMIinit.dll |
0/48 | LMIinit.dll |
Here is the detection names for the LogMeIn, Inc. files. I've grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
As mentioned above, I think these detections are false positives since it is very unlikely that LogMeIn, Inc. would ship a malware file.
Scanner | Detection Names |
---|---|
Antiy-AVL | Trojan/Win32.SGeneric, Trojan/Win32.Rozena, GrayWare/Win32.Presenoker, Trojan/Generic.ASMalwS.35468EA |
Bkav | HW32.Laneul.xiys |
ClamAV | Win.Worm.Agent-9246 |
Comodo | UnclassifiedMalware |
Cylance | Unsafe |
Fortinet | RAT/RemotelyAnywh |
MaxSecure | Spy.W32.VB.alp |
McAfee | Artemis!C0E35EB02EDA |
McAfee-GW-Edition | Artemis!C0E35EB02EDA |
The detection percentage is based on the fact that I've gathered 8248 scan reports for the LogMeIn, Inc. files. 12 of these scan reports 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 is done on certificates with the following serial numbers: