Did you just stumble upon a file that is digitally signed by Bsecure Technologies? If that's the case, please read on.
You will typically see Bsecure Technologies when clicking to run the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:

You can also view the Bsecure Technologies certificate with the following procedure:
Here's a screenshot of a file that has been signed by Bsecure Technologies:

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 Bsecure Technologies and that the file has not been tampered with.
If you click the View Certificate button shown in the screenshot above, you can see 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 view the address for Bsecure Technologies, 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 Bsecure Technologies certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screengrab above.
These are the Bsecure Technologies files I've gathered, thanks to the FreeFixer users.
| Detection Ratio | File Name |
|---|---|
| 0/39 | BsafeBHO.dll |
| 0/49 | InetCtrl67.dll |
| 0/47 | InetCtrl57.dll |
| 0/50 | InetCtrl67.dll |
The detection percentage is based on the fact that I have collected 185 scan reports for the Bsecure Technologies files. 0 of these scan results came up with some sort of detection. If you like, you can review the full details of the scan results by examining the files listed above.
The analysis is based on certificates with the following serial numbers: