GridinSoft Threat Intelligence

statreport.exe file report

Under review File reputation report
MD5 95fb694b018ca0fe75cf5620756ef73b
Latest seen 2023-11-09 23:10:30 (2 years ago)
First seen 2017-12-12 14:07:37 (8 years ago)
Size 161 KB
Product StatReport App

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-12-12 14:07:37 (8 years ago); latest analysis 2023-11-09 23:10:30 (2 years ago).

Publisher context

Product metadata: StatReport App.

Digital signature

Signed by Shenzhen Enode Technology Co., Ltd.. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

statreport.exe is a Windows file recorded in the ThreatInfo database. It is associated with StatReport App. The current detection status is Undefined, based on the latest analysis from 2023-11-09 23:10:30 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: StatReport App
MD5: 95fb694b018ca0fe75cf5620756ef73b
Size: 161 KB
First Published: 2017-12-12 14:07:37 (8 years ago)
Latest Published: 2023-11-09 23:10:30 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-11-09 23:10:30 (2 years ago)
Signed By: Shenzhen Enode Technology Co., Ltd.
Status: Valid

The signature on statreport.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%\hi\hiplayer

ThreatInfo has observed statreport.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 7 100.0%

The most common operating system signal for statreport.exe is Windows 7 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.

statreport.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 0x00009730
Image base 0x00400000

PE Sections:

Sections 5
Raw data 155648

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

.text 114688 bytes · 73.7% of section data
MD5 b14d5defafdeb14a6d287fd9018d0af1
.rdata 24576 bytes · 15.8% of section data
MD5 3ef54caad59790b3d5311c095c0d6299
.data 8192 bytes · 5.3% of section data
MD5 b00b43cb3afc5820fc53e50543dd3f1a
.tls 4096 bytes · 2.6% of section data
MD5 620f0b67a91f7f74151bc5be745b7110
.rsrc 4096 bytes · 2.6% of section data
MD5 c240507f9fe877fd79324afbbc3c014e

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 95fb694b018ca0fe75cf5620756ef73b.
  • 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.