Did you just stumble upon a file that is digitally signed by Autonomy? If so, please read on.
You will probably notice Autonomy 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 Autonomy digital signature with the following procedure:
Here's a screengrab of a file that has been signed by Autonomy:
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 Autonomy and that no one has tampered with the file.
If you click the View Certificate button shown in the screencap 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 Autonomy, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA and VeriSign Class 3 Code Signing 2009-2 CA has issued the Autonomy certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screencap above.
The following are the Autonomy files I've collected, thanks to the FreeFixer users.
Detection Ratio | File Name |
---|---|
1/57 | Agent.exe |
0/49 | lv_trackerx64.sys |
0/43 | ConnectedRegistration.exe |
Here is the detection names for the Autonomy files. I have grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
Scanner | Detection Names |
---|---|
VBA32 | Downloader.Agent |
The detection percentage is based on the fact that I have gathered 149 scan results for the Autonomy files. 1 of these scan results came up with some sort of detection. You can view the full details of the scan reports by examining the files listed above.
The analysis has been done on certificates with the following serial numbers: