GridinSoft Threat Intelligence

hcpackage64.exe file report

Clean record File reputation report
MD5 59999624c41b5acd7b6139f24bb57fb1
Latest seen 2023-01-11 23:10:20 (3 years ago)
First seen 2022-08-20 23:10:56 (3 years ago)
Size 18 MB
Publisher trend_company_name
Signed by Trend Micro, Inc.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-08-20 23:10:56 (3 years ago); latest analysis 2023-01-11 23:10:20 (3 years ago).

Publisher context

Company metadata: trend_company_name. Product metadata: trend_product_name.

Digital signature

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

hcpackage64.exe is a Windows file recorded in the ThreatInfo database. It is associated with trend_product_name. The reported company name is trend_company_name. The current detection status is Clean, based on the latest analysis from 2023-01-11 23:10:20 (3 years 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: trend_product_name
Company Name: trend_company_name
MD5: 59999624c41b5acd7b6139f24bb57fb1
Size: 18 MB
First Published: 2022-08-20 23:10:56 (3 years ago)
Latest Published: 2023-01-11 23:10:20 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-01-11 23:10:20 (3 years ago)
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.

%programfiles%\trend micro

ThreatInfo has observed hcpackage64.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 hcpackage64.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.

hcpackage64.exe is identified as pe for 32-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 32-bit
Subsystem Windows CUI
Entry point 0x0002dcd0
Image base 0x00400000

PE Sections:

Sections 5
Raw data 577024

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

.text 465408 bytes · 80.7% of section data
MD5 4ae5e0f49e90da6c9f5798b37b851391
.rdata 80896 bytes · 14.0% of section data
MD5 2151fcd12c7a4e5d6170a8fce0b9fe9c
.data 6656 bytes · 1.2% of section data
MD5 d172847e475161f9ce98ede67f659618
.rsrc 3072 bytes · 0.5% of section data
MD5 8bb6be17011ff98fe579a3dea7a0f678
.reloc 20992 bytes · 3.6% of section data
MD5 627f5c33096b2d7d16bb3e7f6fd10288

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 59999624c41b5acd7b6139f24bb57fb1.
  • 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.