OpenCandy (Verified Application Company) - 36% Detection Rate *
Did you just stumble upon a download or a file on your computer that has a digital signature from OpenCandy (Verified Application Company)? Some of the security products refers to the detected files as OpenCandy (PUA) (not malicious) and PUP.Optional.OpenCandy. The detection rate for the OpenCandy (Verified Application Company) files collected here is 36%. Please read on for more details.
You will typically see OpenCandy (Verified Application Company) when double-clicking to run the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:
.png)
You can view the digital signature details for OpenCandy (Verified Application Company) with the following steps:
- Open Windows Explorer and locate the OpenCandy (Verified Application Company) file
- Right-click the file and select Properties
- Click on the Digital Signatures tab
- Click the View Certificate button
Here's a screenshot of a file signed by OpenCandy (Verified Application Company):
-certificate.png)
As you can see in the screencap above, Windows reports that "This digital signature is OK". This implies that the file has been published by OpenCandy (Verified Application Company) and that no one has tampered with the file.
If you click the View Certificate button shown in the screengrab above, you can see 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 OpenCandy (Verified Application Company), such as the street name, city and country.
COMODO RSA Code Signing CA has issued the OpenCandy (Verified Application Company) certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screenshot above.
OpenCandy (Verified Application Company) Files
The following are the OpenCandy (Verified Application Company) files I have gathered, thanks to the FreeFixer users.
| Detection Ratio | File Name |
|---|---|
| 27/56 | OCSetupHlp.dll |
| 10/56 | dhk327.exe |
| 14/55 | dhj553.exe |
| 18/56 | dha362.exe |
| 22/55 | dhg673.exe |
| 19/56 | dhj701.exe |
| 20/56 | dhk704.exe |
| 26/53 | dhj722.exe |
| 26/57 | OCSetupHlp.dll |
Scanner and Detection Names
Here's the detection names for the OpenCandy (Verified Application Company) files. I've grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
| Scanner | Detection Names |
|---|---|
| AVG | OpenCandy.086, OpenCandy.BD0, Generic.729, OpenCandy.70C, OpenCandy.020, OpenCandy.864 |
| AVware | OpenCandy (PUA) |
| AegisLab | AdWare.W32.OpenCandy, W32.Application.Opencandy!c |
| Agnitum | Riskware.Agent! |
| AhnLab-V3 | PUP/Win32.OpenCandy |
| Antiy-AVL | GrayWare[AdWare]/Win32.OpenCandy.ak, GrayWare[Adware]/Win32.OpenCandy.heur |
| Arcabit | PUP.Adware.OpenCandy |
| Avast | Win32:Adware-gen [Adw], Win32:OpenCandy-D [PUP] |
| Avira | PUA/OpenCandy.Gen |
| Baidu-International | Adware.Win32.OpenCandy.E, Adware.Win32.OpenCandy.A |
| Bkav | W32.HfsAdware.FF9C |
| Comodo | Application.Win32.OpenCandy.~AE |
| DrWeb | Adware.OpenCandy.182, Adware.OpenCandy.183 |
| ESET-NOD32 | a variant of Win32/OpenCandy.A potentially unsafe, a variant of Win32/OpenCandy.E potentially unsafe |
| Fortinet | Adware/OpenCandy, Riskware/OpenCandy |
| GData | Win32.Application.OpenCandy.O |
| Ikarus | not-a-virus:AdWare.OpenCandy |
| Jiangmin | AdWare.OpenCandy.g, AdWare/OpenCandy.ap, AdWare/OpenCandy.aw, AdWare.OpenCandy.q |
| K7AntiVirus | Unwanted-Program ( 004b90b11 ), Unwanted-Program ( 004cf2841 ), Unwanted-Program ( 004ccff81 ), Unwanted-Program ( 004bc9351 ) |
| K7GW | Unwanted-Program ( 004b90b11 ), Hacktool ( 655367771 ), Unwanted-Program ( 004bc9351 ) |
| Malwarebytes | PUP.Optional.OpenCandy |
| McAfee | Artemis!1952DEE28EDC, Artemis!0349886FA370, Artemis!5373FFC228C6 |
| McAfee-GW-Edition | Artemis!PUP, BehavesLike.Win32.LiveSoftAction.cc, BehavesLike.Win32.ZvuZona.cc |
| NANO-Antivirus | Riskware.Win32.OpenCandy.eamjqz, Riskware.Win32.OpenCandy.dyxque |
| Panda | PUP/OpenCandy, Trj/GdSda.A |
| Qihoo-360 | HEUR/QVM11.1.Malware.Gen, QVM11.1.Malware.Gen |
| SUPERAntiSpyware | PUP.OpenCandy/Variant |
| Sophos | Generic PUA DN (PUA) |
| Symantec | Trojan.Gen.2, Suspicious.Cloud.2, PUA.OpenCandy |
| Tencent | Win32.Adware.Opencandy.Eibh |
| TrendMicro | TROJ_GEN.R00XC0OBI16, TROJ_GEN.R0EBC0OL615 |
| VBA32 | AdWare.OpenCandy |
| VIPRE | OpenCandy (PUA) (not malicious) |
| ViRobot | Adware.Opencandy.855192[h], Adware.Opencandy.934040[h] |
| Yandex | Riskware.Agent! |
| Zillya | Adware.OpenCandy.Win32.764, Downloader.Upatre.Win32.57580, Dropper.Agent.Win32.220440, Trojan.Yakes.Win32.41253, Adware.OpenCandy.Win32.2169 |
* How the Detection Percentage is Calculated
The detection percentage is based on that I have collected 500 scan results for the OpenCandy (Verified Application Company) files. 182 of these scan results came up with some sort of detection. You can review the full details of the scan reports by examining the files listed above.
Analysis Details
In the analysis on this page I grouped all certificates where the signer name is set to upper and lower case variants of OpenCandy (Verified Application Company). These are the signer names:
- OpenCandy (Verified Application Company)
- OPENCANDY (Verified Application Company)
The analysis is based on certificates with the following serial numbers:
- 0af6675f945d41c23ead08c4462d3061
- 54359cd9dcb656df52e1f48258622521
- 4a1c72ed869698b1d118ca20c86ef4f9
- 00aff065026d320c3725abdf33b2e73eb5
- 0a5069c0ad472301fb782c5176429e39
- 61f716e4410768da5306101e504debaa
- 77af0d4aec64bdb42e2431df438866ee