HiBase Group Publisher Information

Did you just download a file that has been digitally signed by HiBase Group and wonder if the file is safe? If so, please read on.

You will typically see HiBase Group when double-clicking to run the file. The publisher name is then displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:

Screenshot where HiBase Group appears as the verified publisher in the UAC dialog

You can also view the HiBase Group certificate with the following procedure:

  1. Open Windows Explorer and locate the HiBase Group file
  2. Right-click the file and select Properties
  3. Click the Digital Signatures tab
  4. Click the View Certificate button

Here is a screenshot of a file signed by HiBase Group:

Screenshot of the HiBase Group certificate

As you can see in the screenshot above, the Windows OS reports that "This digital signature is OK". This means that the file has been published by HiBase Group 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, etc. You can also see the address for HiBase Group, such as the street name, city and country.

UTN-USERFirst-Object and Symantec Class 3 SHA256 Code Signing CA has issued the HiBase Group certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screenshot above.

HiBase Group Files

These are the HiBase Group files I have collected, thanks to the FreeFixer users.At the moment there's no scan result available for any of the HiBase Group files, but they have been queued for scanning. Please reload this page in 5-10 minutes to check if the scan result is available.

Detection RatioFile Name
Queued for scan..pxcnv.exe
Not availabledbfview.exe

Analysis Details

The analysis is based on certificates with the following serial numbers:

Comments

No comments posted yet.

Leave a reply