Did you just find a download or a file on your computer that is digitally signed by Microsoft Windows? If that's the case, please read on.
You will typically see Microsoft Windows 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 Microsoft Windows digital signature with the following steps:
Here's a screenshot of a file that has been digitally signed by Microsoft Windows:
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 Microsoft Windows and that no one has tampered with the file.
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 see the address for Microsoft Windows, such as the street name, city and country.
Microsoft Windows Verification PCA, Microsoft Windows Production PCA 2011 and Microsoft Development PCA 2014 has issued the Microsoft Windows certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screengrab above.
The following are the Microsoft Windows files I've gathered, thanks to the FreeFixer users.
The FreeFixer tool treats files from Microsoft Windows as trusted, which means that the Microsoft Windows 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 Microsoft Windows file(s). My guess is that those detections are false positives and that the files are safe. It is unlikely that Microsoft Windows would ship a malware file.
Here's the detection names for the Microsoft Windows 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 Microsoft Windows would ship a malware file.
Scanner | Detection Names |
---|---|
APEX | Malicious |
AegisLab | W32.Virut |
Alibaba | Heur.Win.Harmlet.247 |
Avast | Win64:Dropper-gen [Drp] |
Baidu | Win32.Trojan.WisdomEyes.16070401.9500.9563 |
Bkav | HW32.Nonim.owme, W32.HfsAutoA.C021, W32.AIDetect.malware1, HW32.Nonim.psyk, W32.HfsAutoA.7bbe, HW64.packed.3B1A, W64.HfsAutoB., W32.HfsAutoB. |
ByteHero | Trojan.Malware.Obscu.Gen.002 |
ClamAV | Win.Trojan.Agent-7029285-0 |
Cylance | Unsafe |
Emsisoft | JS:Exploit.BlackHole.OP (B) |
Jiangmin | Win32/Virut.bn |
McAfee-GW-Edition | - |
Microsoft | Backdoor:MSIL/Bladabindi.AA |
Paloalto | generic.ml |
Rising | PE:PUF.Injector!1.9F0F |
TheHacker | Trojan/Injector.aoc, Trojan/Downloader.Banload.vpq |
Trapmine | malicious.moderate.ml.score |
eGambit | Unsafe.AI_Score_98%, Unsafe.AI_Score_99% |
The detection percentage is based on the fact that I have gathered 281548 scan reports for the Microsoft Windows files. 43 of these scan reports came up with some sort of detection. If you like, 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: