Did you just find a file that has been digitally signed by Power Software Limited? If that's the case, please read on.
You will typically see Power Software Limited 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 digital signature details for Power Software Limited with the following steps:
Here's a screenshot of a file digitally signed by Power Software Limited:
As you can see in the screenshot above, Windows states that "This digital signature is OK". This means that the file has been published by Power Software Limited 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 view the address for Power Software Limited, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA and Symantec Class 3 SHA256 Code Signing CA has issued the Power Software Limited certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screenshot above.
These are the Power Software Limited files I've gathered, thanks to the FreeFixer users.
Detection Ratio | File Name |
---|---|
1/57 | PWRISOVM.EXE |
1/54 | PWRISOVM.EXE |
1/55 | PWRISOVM.EXE |
1/55 | PWRISOVM.EXE |
1/67 | WASHELL.DLL |
1/56 | PWRISOVM.EXE |
1/57 | PWRISOVM.EXE |
1/55 | PWRISOSH.DLL |
1/57 | PWRISOSH.DLL |
1/54 | PWRISOSH.DLL |
1/67 | PWRISOSH.DLL |
1/65 | scdemu.sys |
2/70 | PWRISOSH.DLL |
1/56 | PowerISO.exe |
1/55 | PWRISOSH.DLL |
6/54 | PowerISO6-x64(1).exe |
1/57 | PWRISOVM.EXE |
1/57 | PWRISOVM.EXE |
1/56 | PWRISOSH.DLL |
1/56 | PWRISOVM.EXE |
1/59 | waemu.sys |
1/61 | PWRISOSH.DLL |
2/65 | PWRISOVM.EXE |
1/66 | PWRISOSH.DLL |
2/69 | PWRISOSH.DLL |
1/56 | PWRISOVM.EXE |
1/57 | waemu.sys |
2/55 | PWRISOVM.EXE |
1/52 | anyburn_setup_x64.exe |
1/55 | WAHELPER.EXE |
1/53 | PWRISOVM.EXE |
1/56 | scdemu.sys |
1/57 | PWRISOVM.EXE |
1/57 | PWRISOVM.EXE |
1/53 | PWRISOSH.DLL |
1/55 | PWRISOVM.EXE |
1/53 | PWRISOSH.DLL |
2/58 | gburner4-x64.exe |
1/54 | WASHELL.DLL |
1/54 | WAHELPER.EXE |
1/59 | PWRISOVM.EXE |
1/67 | PWRISOSH.DLL |
1/67 | PWRISOVM.EXE |
2/67 | PWRISOVM.EXE |
2/71 | GCDTRAY.EXE |
2/68 | PWRISOSH.DLL |
1/64 | PWRISOVM.EXE |
0/56 | PWRISOVM.EXE |
0/56 | PWRISOSH.DLL |
0/53 | PWRISOSH.DLL |
0/57 | PWRISOVM.EXE |
0/55 | PWRISOVM.EXE |
0/54 | PWRISOSH.DLL |
Here's the detection names for the Power Software Limited files. I've grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
Scanner | Detection Names |
---|---|
Baidu-International | PUA.Win32.FusionCore.D, Adware.Win64.Conduit.80 |
Bkav | W64.HfsAdware.D281, W32.HfsAdware.D281 |
ESET-NOD32 | a variant of Win32/FusionCore.D potentially unwanted |
GData | Win32.Application.SearchProtect.AO |
McAfee-GW-Edition | BehavesLike.Win32.Tool.tc, BehavesLike.Win32.Tool.vc |
Microsoft | PUA:Win32/InstallCore, PUA:Win32/FusionCore |
Rising | PE:Malware.Generic/QRS!1.9E2D [F], PUA.InstallCore!8.8B (CLOUD) |
VBA32 | SigAdware.PowerSoftwareLimited |
Zillya | Dropper.Injector.Win32.73063 |
The detection percentage is based on the fact that I've collected 4962 scan reports for the Power Software Limited files. 60 of these scan results came up with some sort of detection. You can review the full details of the scan results by examining the files listed above.
The analysis is done on certificates with the following serial numbers: