GridinSoft Threat Intelligence

BHome.exe file report

Clean record File reputation report
MD5 0c6978591a5f3cda55f0da83febbd2f4
Latest seen 2025-02-19 23:00:39 (a year ago)
First seen 2025-02-19 23:00:39 (a year ago)
Size 21 MB
Publisher Bkav Corporation
Product Bkav Home 2018
Signed by Bkav Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2025-02-19 23:00:39 (a year ago); latest analysis 2025-02-19 23:00:39 (a year ago).

Publisher context

Company metadata: Bkav Corporation. Product metadata: Bkav Home 2018.

Digital signature

Signed by Bkav Corporation. ThreatInfo marks this publisher as trusted for this record.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

BHome.exe is a Windows file recorded in the ThreatInfo database. It is associated with Bkav Home 2018. The reported company name is Bkav Corporation. The current detection status is Clean, based on the latest analysis from 2025-02-19 23:00:39 (a year ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Bkav Home 2018
Company Name: Bkav Corporation
MD5: 0c6978591a5f3cda55f0da83febbd2f4
Size: 21 MB
First Published: 2025-02-19 23:00:39 (a year ago)
Latest Published: 2025-02-19 23:00:39 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-02-19 23:00:39 (a year ago)
Signed By: Bkav Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%profile%

ThreatInfo has observed BHome.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 10 100.0%

The most common operating system signal for BHome.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

BHome.exe is identified as pe for 32-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x000f6ff5
Image base 0x00400000

PE Sections:

Sections 5
Raw data 1708032

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 1170944 bytes · 68.6% of section data
MD5 169e1944c4a79857845d32c89cd1476f
.rdata 271872 bytes · 15.9% of section data
MD5 f1f6df1593b7af62c1d83c685979e680
.data 23040 bytes · 1.3% of section data
MD5 1d8f16ec3f0074ffcb4ab6f8c317c4c1
.rsrc 101888 bytes · 6.0% of section data
MD5 34f0b855dd7e420b20975306e804a35d
.reloc 140288 bytes · 8.2% of section data
MD5 04fe98193b6b827f5c8fbe3ec85dfe6b

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 0c6978591a5f3cda55f0da83febbd2f4.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.