GridinSoft Threat Intelligence

CrashReport.exe file report

Under review File reputation report
MD5 faf3a34e2ec90f2ffda12d074e809051
Latest seen 2025-04-12 23:02:10 (a year ago)
First seen 2025-04-12 23:01:58 (a year ago)
Size 593 KB
Publisher 爱奇艺
Product 崩溃上传

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-04-12 23:01:58 (a year ago); latest analysis 2025-04-12 23:02:10 (a year ago).

Publisher context

Company metadata: 爱奇艺. Product metadata: 崩溃上传.

Digital signature

Signed by BeiJing IQIYI Science & Techonology 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.

CrashReport.exe is a Windows file recorded in the ThreatInfo database. It is associated with 崩溃上传. The reported company name is 爱奇艺. The current detection status is Undefined, based on the latest analysis from 2025-04-12 23:02:10 (a year 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: 崩溃上传
Company Name: 爱奇艺
MD5: faf3a34e2ec90f2ffda12d074e809051
Size: 593 KB
First Published: 2025-04-12 23:01:58 (a year ago)
Latest Published: 2025-04-12 23:02:10 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-04-12 23:02:10 (a year ago)

The signature on CrashReport.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%\iqiyi video\lstyle\13.3.5.9162\qyappplugin

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

CrashReport.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 0x000177a1
Image base 0x00400000

PE Sections:

Sections 5
Raw data 596480

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

.text 98304 bytes · 16.5% of section data
MD5 d21246b7e9d886a221e7559db28bfab7
.rdata 37376 bytes · 6.3% of section data
MD5 f4e95b64aa97f7c4844226bde6ffaa15
.data 1024 bytes · 0.2% of section data
MD5 a4226b06f47693157b8d7454a4f6bd35
.rsrc 455680 bytes · 76.4% of section data
MD5 f59cd090116b202323501e7f1e21b45c
.reloc 4096 bytes · 0.7% of section data
MD5 e96464da31f87e295e8f6bff2ee9c6a2

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 faf3a34e2ec90f2ffda12d074e809051.
  • 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.