Did you just run into a file that is digitally signed by Trusteer? If so, please read on.
You will typically see Trusteer when running the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can view the additional details from the Trusteer digital signature with the following procedure:
Here is a screenshot of a file that has been signed by Trusteer:
As you can see in the screencap above, the Windows OS reports that "This digital signature is OK". This implies that the file has been published by Trusteer 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, and so on. You can also see the address for Trusteer, such as the street name, city and country.
VeriSign Class 3 Code Signing 2004 CA and VeriSign Class 3 Code Signing 2010 CA has issued the Trusteer certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screenshot above.
These are the Trusteer files I've gathered, thanks to the FreeFixer users.
The FreeFixer tool treats files from Trusteer as trusted, which means that the Trusteer files will appear with a green background and that there is 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 Trusteer file(s). I'm pretty sure those detections are incorrect and that the files are safe. It is unlikely that Trusteer would ship a malware file.
Detection Ratio | File Name |
---|---|
1/41 | RapportMgmtService.exe |
1/42 | RapportMgmtService.exe |
1/44 | rooksdol.dll |
1/57 | RapportMgmtService.exe |
1/47 | trf.dll |
1/56 | RapportMgmtService.exe |
1/43 | RapportMgmtService.exe |
2/44 | RapportMgmtService.exe |
1/48 | rapportmgmtservice.exe |
1/57 | RapportService.exe |
1/41 | RapportMgmtService.exe |
1/43 | rapportmgmtservice.exe |
1/48 | RapportService.exe |
1/48 | rapportei.sys |
1/56 | rookscom.dll |
1/67 | rooksdol.dll |
0/56 | rapportcerberus64_80120.sys |
0/42 | RapportIaso.sys |
0/46 | RapportSetup.exe |
0/56 | rapporthades.sys |
0/56 | rapporthades64.sys |
0/57 | rapportcerberus64_80128.sys |
0/48 | RapportSafeUninstall (1).exe |
0/54 | rooksbas.dll |
0/42 | rapportke64.sys |
0/57 | rooksbas_x64.dll |
Here's the detection names for the Trusteer files. I have 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 Trusteer would ship a malware file.
Scanner | Detection Names |
---|---|
Bkav | HW32.CDB.6c91, HW32.CDB.Edcb, HW32.CDB.3653, HW32.Nonim.fyiu |
ByteHero | Trojan.Win32.Heur.Gen |
CAT-QuickHeal | (Suspicious) - DNAScan |
Ikarus | Virus.Win32.Bubak |
Tencent | Trojan.Win32.YY.Gen.6, Trojan.Win32.YY.Gen.0, Trojan.Win32.YY.Gen.10 |
Zillya | Dropper.ZAccessCRTD.Win32.9905 |
The detection percentage is based on that I've gathered 17970 scan reports for the Trusteer files. 17 of these scan reports came up with some sort of detection. You can review the full details of the scan reports by examining the files listed above.
The analysis is based on certificates with the following serial numbers: