GridinSoft Threat Intelligence

HouseCallX.exe file report

Clean record File reputation report
MD5 74b3402a7e714091b02ae36161c18f01
Latest seen 2025-11-20 23:01:42 (6 months ago)
First seen 2023-12-01 23:04:36 (2 years ago)
Size 1 MB
Signed by Trend Micro, Inc.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-12-01 23:04:36 (2 years ago); latest analysis 2025-11-20 23:01:42 (6 months ago).

Digital signature

Signed by Trend Micro, Inc.. ThreatInfo marks this publisher as trusted for this record.

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.

File context

HouseCallX.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2025-11-20 23:01:42 (6 months 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.

File Details

MD5: 74b3402a7e714091b02ae36161c18f01
Size: 1 MB
First Published: 2023-12-01 23:04:36 (2 years ago)
Latest Published: 2025-11-20 23:01:42 (6 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-11-20 23:01:42 (6 months ago)

Overview

Signed By: Trend Micro, Inc.
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.

Geographic signal

Observed country distribution

ThreatInfo has seen HouseCallX.exe across 4 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Turkey
Share 25.0%
Low High activity

The strongest geographic signal for this file is Turkey with 25.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 100.0%

The most common operating system signal for HouseCallX.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.

Analysis

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

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x000b5b20
Image base 0x0000000140000000

PE Sections:

Sections 6
Raw data 1159168

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

.text 864768 bytes · 74.6% of section data
MD5 af2ca5013d09e7c57c10b911ccaab33d
.rdata 213504 bytes · 18.4% of section data
MD5 5e269bbf44c38bf9bcb21d8fef94d9d2
.data 14336 bytes · 1.2% of section data
MD5 029da011250c03fe75c30438c2432cdb
.pdata 58368 bytes · 5.0% of section data
MD5 314d9c1990ccfecd3cc3a7477aa00ed2
.rsrc 1536 bytes · 0.1% of section data
MD5 5b6794d38e9b96674370950e32ace048
.reloc 6656 bytes · 0.6% of section data
MD5 df707e4172faf90c987cc9152db55594

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 74b3402a7e714091b02ae36161c18f01.
  • 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.