IBM - 0.201% Detection Rate *
Did you just stumble upon a file that has a digital signature from IBM? If that's the case, please read on.
You'll typically see IBM when running the file. The publisher name is then displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can view additional details from the IBM certificate with the following steps:
- Open up Windows Explorer and locate the IBM file
- Right-click on the file and select Properties
- Click the Digital Signatures tab
- Click the View Certificate button
Here is a screenshot of a file signed by IBM:
As you can see in the screenshot above, the Windows OS reports that "This digital signature is OK". This implies that the file has been published by IBM and that no one has tampered with the file.
If you click the View Certificate button shown in the screengrab 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, and so on. You can also view the address for IBM, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA and Symantec Class 3 SHA256 Code Signing CA has issued the IBM certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screenshot above.
IBM Files
These are the IBM files I have collected, thanks to the FreeFixer users.
The FreeFixer tool treats files from IBM as trusted, which means that the IBM 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 IBM file(s). My guess is that those detections are incorrect and that the files are safe. It is unlikely that IBM would ship a malware file.
| Detection Ratio | File Name |
|---|---|
| 1/50 | RapportMgmtService.exe |
| 1/56 | rooksbas_x64.dll |
| 1/54 | RapportService.exe |
| 1/57 | RapportService.exe |
| 1/56 | rooksdol.dll |
| 1/57 | trf_x64.dll |
| 1/47 | RapportTanzanEx410.DLL |
| 1/54 | rooksdol.dll |
| 1/65 | RapportService.exe |
| 1/64 | RapportMgmtService.exe |
| 1/65 | $RRGGLXZ.exe |
| 1/65 | RapportMgmtService.exe |
| 1/68 | rapportmgmtservice.exe |
| 1/68 | RapportSetup.exe |
| 0/59 | rapportaegle64.sys |
| 0/65 | rapportcerberus64_1908115.sys |
| 0/67 | rapportcerberus64_2104058.sys |
| 0/57 | RapportMgmtService.exe |
| 0/57 | rapportcerberus64_1609053.sys |
| 0/62 | RapportMgmtService.exe |
| 0/57 | rapportcerberus64_1609035.sys |
| 0/57 | RapportMgmtService.exe |
Scanner and Detection Names
Here is the detection names for the IBM 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 false positives since it is very unlikely that IBM would ship a malware file.
| Scanner | Detection Names |
|---|---|
| Baidu | Win32.Trojan.WisdomEyes.16070401.9500.9756 |
| Bkav | HW32.Packed.149F, HW64.packed.80FB, HW32.Packed.14E3, HW32.Packed.3B1D, HW32.Packed.B177, HW64.packed.ACAF, HW32.Packed.234D, HW32.Packed.603D |
| Cylance | Unsafe |
* How the Detection Percentage is Calculated
The detection percentage is based on the fact that I have collected 6958 scan reports for the IBM files. 14 of these scan results came up with some sort of detection. If you like, you can view the full details of the scan results by examining the files listed above.
Analysis Details
The analysis is based on certificates with the following serial numbers:
- 3ad9de84c34746c833064e93d821e11e
- 4db9190cea30ece66c56a1b121c1c24c
- 3a56c5f37635265bc45a69db6d4f50bb
- 7b79a671bcdbcb575578952c856b8f09