Did you just run into a file that has been digitally signed by Samsung Electronics CO., LTD.? If so, please read on.
You will probably see Samsung Electronics CO., LTD. when running the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can view the additional details from the Samsung Electronics CO., LTD. digital signature with the following steps:
Here's a screenshot of a file signed by Samsung Electronics CO., LTD.:
As you can see in the screenshot above, the Windows OS states that "This digital signature is OK". This means that the file has been published by Samsung Electronics CO., LTD. and that no one has tampered with the file.
If you click the View Certificate button shown in the screencap 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 view the address for Samsung Electronics CO., LTD., such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA, Symantec Class 3 Extended Validation Code Signing CA - G2 and VeriSign Class 3 Code Signing 2004 CA has issued the Samsung Electronics CO., LTD. certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screenshot above.
These are the Samsung Electronics CO., LTD. files I have collected, thanks to the FreeFixer users.
The FreeFixer tool treats files from Samsung Electronics CO., LTD. as safe, which means that the Samsung Electronics CO., LTD. files will appear with a green background and that there's 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 Samsung Electronics CO., LTD. file(s). I'm pretty sure those detections are incorrect and that the files are safe. It is unlikely that Samsung Electronics CO., LTD. would ship a malware file.
Detection Ratio | File Name |
---|---|
1/49 | CDASrv.exe |
1/70 | ss_conn_service2.exe |
1/42 | SUAComnCtrl.dll |
1/43 | UTILIT~1.EXE |
2/42 | UTEngine.dll |
2/46 | CommunicationManager.exe |
1/61 | Setup.exe |
4/42 | ToolLauncher.exe |
1/47 | FileAndProcessModule.dll |
1/57 | SCP_Svc.exe |
2/51 | FsUsbExService.Exe |
1/44 | VZWSUAM.exe |
1/56 | SWMAgent.exe |
0/51 | ssport.sys |
0/47 | ssudbus.sys |
0/50 | UA.exe |
0/44 | CommonAgent.exe |
0/46 | ssudmdm.sys |
0/50 | CDASrv.exe |
0/55 | CDASrv.exe |
0/48 | iLinker.exe |
0/45 | MetaExtractor.exe |
0/46 | VendorAPIRun64.exe |
Here is the detection names for the Samsung Electronics CO., LTD. files. I have 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 Samsung Electronics CO., LTD. would ship a malware file.
Scanner | Detection Names |
---|---|
AegisLab | HackTool.W32.PassDic |
BitDefender | Gen:Trojan.Heur.JP.9y1aaCKeKtjO |
Bkav | W32.Clod712.Trojan.3b35, W32.HfsAutoB.FB55 |
CAT-QuickHeal | (Suspicious) - DNAScan |
Comodo | UnclassifiedMalware |
Emsisoft | Android.Adware.Plankton.A (B), Trojan.Generic.9626251 (B) |
GData | Gen:Trojan.Heur.JP.9y1aaCKeKtjO |
Ikarus | Trojan.Win32.Fibedol |
Jiangmin | TrojanSpy.SpyEyes.pbn, Trojan/Keylogger.du, Trojan.Generic.aljeo |
VBA32 | AdWare.iBryte |
Zillya | Worm.NetSky.Win32.1961 |
eSafe | Win32.Trojan |
The detection percentage is based on the fact that I have collected 27882 scan results for the Samsung Electronics CO., LTD. files. 19 of these scan results came up with some sort of detection. If you like, you can view the full details of the scan reports by examining the files listed above.
In the analysis on this page I grouped all certificates where the signer name is set to upper and lower case variants of Samsung Electronics CO., LTD.. These are the signer names:
The analysis has been done on certificates with the following serial numbers: