You could download this as well and check to see if all the code was verify Image Signatures by microsoft, nasty code offten isn't.
A malware author who takes the trouble can easily add the name of a legitimate company, like Microsoft, to the Company field of an executable file. To provide assurance that their products are genuine, therefore, legitimate software vendors digitally sign most of the program files they publish. A digital signature can be used to verify that a file has been signed by the vendor using a private key and that the file has not been modified since being signed.
Process Explorer allows you to automatically verify the signature of a signed executable or DLL file. By default, verification is performed only on demand, and can be performed for individual files or for all running processes. In the Properties dialog for both processes and DLLs, the Image tab contains a Verify button that can be used to verify the digital signature for the associated file. Clicking the button causes Process Explorer to check the Certificate Revocation List (CRL) for the certificate to ensure that it is valid, and to check the cryptographic hash of the file to verify that it has not been tampered with since being signed.
To configure Process Explorer to automatically verify the signatures for all running processes and files, click the Options menu, and then click Verify Image Signatures.
The Verified Signer field, which displays next to the file icon in the Properties dialog and as a column that can be shown in the process list and DLL View, indicates the status of any signature check that has been performed. If Process Explorer is able to verify the signature, the field displays â€œ(Verified)â€, followed by the subject name from the certificate. (Note that the name on the signing certificate might not be the same as the name in the Company Name field. For example, most executable files that ship as part of Windows have â€œMicrosoft Corporationâ€ as the company name but are signed with a â€œMicrosoft Windowsâ€ certificate.)
If signature verification has not been attempted, or if the selected file is not an executable file type, the field is blank or displays â€œ(Not verified)â€ followed by the company name from the fileâ€™s version resource. â€œ(Unable to verify)â€ followed by the company name indicates that the file is not signed or that a signature check has failed.
This is good too but it dousen't verify things the same way.