Did you just stumble upon a file that has a digital signature from Microsoft Corporation? If so, please read on.
You will probably notice Microsoft Corporation when running the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screencap shows:
You can also view the Microsoft Corporation certificate with the following procedure:
Here's a screenshot of a file that has been signed by Microsoft Corporation:
As you can see in the screengrab above, Windows states that "This digital signature is OK". This implies that the file has been published by Microsoft Corporation and that no one has tampered with the file.
If you click the View Certificate button shown in the screenshot above, you can view 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 Corporation, such as the street name, city and country.
Microsoft Code Signing PCA, Microsoft Code Signing PCA 2010 and Microsoft Code Signing PCA 2011 has issued the Microsoft Corporation 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 Microsoft Corporation files I have collected, thanks to the FreeFixer users.
The FreeFixer tool treats files from Microsoft Corporation as safe, which means that the Microsoft Corporation 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 Corporation file(s). I'm pretty sure those detections are incorrect and that the files are safe. It's unlikely that Microsoft Corporation would ship a malware file.
Here's the detection names for the Microsoft Corporation 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 incorrect since it is very unlikely that Microsoft Corporation would ship a malware file.
Scanner | Detection Names |
---|---|
AegisLab | Troj.W32.Pakes.lJSc |
Antiy-AVL | Riskware/Win32.Krap.ii, GrayWare[AdWare]/Win32.FileFinder.h, Worm/Win32.Runouce.gen, Trojan/Win32.Bitrep, Trojan/Win32.Agent2, Trojan[Backdoor]/Win32.Unomois, Trojan/Win32.Generic.gen, Trojan/Generic.ASMalwS.35009C2, Trojan/Win32.Wacatac |
Bkav | W32.HfsAdware.E4C7, HW32.Stranfom.weui, W32.Clod0c4.Trojan.9774, HW32.Laneul.qioy, HW32.Laneul.mgcs, HW64.packed.9C2A, HW64.packed.717B, HW32.Packed.9F75, HW64.packed.DDA7, HW64.packed.B164, HW64.packed.D545, HW64.packed.EE6F, HW64.packed.1BDD, W32.Clod21a.Trojan.53d2, W64.HfsAdware.E4C7, HW32.Packed.D5CC, HW32.Packed.8896, HW32.Packed.7C1E, HW64.packed.76E9, HW64.packed.8CD2, HW64.packed.F9C3, HW64.packed.A013, HW64.packed.55A4, HW64.packed.8C7F, HW64.packed.9439, HW64.packed.3954, HW64.packed.64D9, HW64.packed.B6F2, HW64.packed.A74E, HW64.packed.D4DF, HW64.packed.AB58, HW64.packed.4AF9, HW64.packed.2B6B, HW64.packed.AA6C, HW64.packed.45B2, HW64.packed.D5F5, HW64.packed.DFCE, HW64.packed.8168, HW64.packed.70E2, HW64.packed.8096, HW64.packed.1442 |
ByteHero | Trojan.Malware.Win32.xPack.i, Trojan.Win32.Heur.098 |
CMC | Trojan-Dropper.Win32.Decay!O, Trojan-Clicker.Win32.VB!O, Trojan-Downloader.Win32.Agent!O, Packed.Win32.Hrup.1!O |
ClamAV | W32.Virut.Gen.D-165, W32.Virut.Gen.D-159, Win.Trojan.Bancos-2115, Win.Trojan.Agent-940175 |
Comodo | TrojWare.Win64.Agent.ist, Heur.Suspicious |
CrowdStrike | win/malicious_confidence_80% (D) |
Emsisoft | Gen:Variant.Graftor.129163 (B), Android.Adware.Dowgin.AQ (B), Adware.InstallIQ.G (B), Android.Exploit.RATC.A (B), Gen:Variant.Symmi.37330 (B), DeepScan:Generic.Lineage.BEDD0A3E (B), Trojan.Generic.8932796 (B), Win32.Expiro.BV (B) |
Ikarus | Virus.Win32.Pioneer |
Jiangmin | Win32/Virut.bn, Trojan.Generic.arrjn, Trojan.Kryplod.hb |
McAfee-GW-Edition | Heuristic.LooksLike.Win32.Suspicious.E, Heuristic.LooksLike.Win32.Suspicious.M, Heuristic.LooksLike.Win32.Winwebsec.B, Heuristic.LooksLike.Win32.Suspicious.B, Heuristic.LooksLike.Win32.Suspicious.Q, Heuristic.LooksLike.Trojan.Dropper.B |
NANO-Antivirus | Trojan.Win32.HLLP.csxpnw, Trojan.Win32.Patched.crlmqj |
Prevx | High Risk Cloaked Malware |
Rising | PE:Malware.XPACK/RDM!5.1, Malware.Generic.5!tfe (cloud:NHPgnqT0W7I) |
Sophos | PsExec (PUA) |
Sunbelt | Bulk Trojan |
Symantec | Suspicious.Insight, Suspicious.Cloud.5 |
TACHYON | Trojan/W32.Cometer.2459936 |
Tencent | Trojan.Win32.YY.Gen.1, Trojan.Win32.YY.Gen.2 |
TheHacker | Trojan/Katusha.m, Trojan/Kryptik.fjm |
Yandex | Trojan.Agent!Jw1HBQ70C5A |
Zillya | Trojan.Generic.Win32.964140, Worm.WhiteIce.Win32.2147, Dropper.Injector.Win32.85306, Trojan.Shelma.Win32.9084, Worm.Runouce.Win32.4533, Trojan.GenericKD.Win32.135191 |
eGambit | Unsafe.AI_Score_99%, Unsafe.AI_Score_74% |
The detection percentage is based on the fact that I have gathered 374646 scan results for the Microsoft Corporation files. 205 of these scan reports 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:
pcของฉันมีตัวติดตามและไม่ค่อยจะปลอดภัยสัญญานไวไฟของฉันก็เช่นกัน
# 19 Feb 2022, 4:48
ryder writes