CrashReportClient.exe threat report
ThreatInfo file report
CrashReportClient.exe
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.
- Detection name
- Trojan.Heur!
- Recommended action
- Scan and remove
- Last analysis
- 2023-11-21 23:06:05 (2 years ago)
- File hash
- 28eb1d817b8d4e7f3ad72747d4d30c15
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Trojan.Heur!.
First seen 2023-11-21 23:06:05 (2 years ago); latest analysis 2023-11-21 23:06:05 (2 years ago).
Company metadata: Epic Games, Inc.. Product metadata: CrashReportClient.
Signed by Embark Studios AB. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
CrashReportClient.exe is a Windows file recorded in the ThreatInfo database. It is associated with CrashReportClient. The reported company name is Epic Games, Inc.. The current detection status is Trojan.Heur!, based on the latest analysis from 2023-11-21 23:06:05 (2 years ago).
If CrashReportClient.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.
File Details
| Product Name: | CrashReportClient |
| Company Name: | Epic Games, Inc. |
| MD5: | 28eb1d817b8d4e7f3ad72747d4d30c15 |
| Size: | 22 MB |
| First Published: | 2023-11-21 23:06:05 (2 years ago) |
| Latest Published: | 2023-11-21 23:06:05 (2 years ago) |
| Status: | Trojan.Heur! (on last analysis) | |
| Analysis Date: | 2023-11-21 23:06:05 (2 years ago) |
Detection screenshot
The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.
Overview
| Signed By: | Embark Studios AB |
| Status: | Valid |
The signature on CrashReportClient.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.
Common Places:
| %programfiles%\steam\steamapps\common\the finals playtest\engine\binaries |
ThreatInfo has observed CrashReportClient.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.
Geography:
| 100.0% |
The strongest geographic signal for this file is Italy with 100.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 CrashReportClient.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
CrashReportClient.exe is identified as pe for 64 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.
| Subsystem: | Windows GUI |
| PE Type: | pe |
| OS Bitness: | 64 |
| Image Base: | 0x0000000140000000 |
| Entry Address: | 0x00e5b038 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 15258624 | 7cb2c67b67ee321f3536f3960950055f |
| .uedbg | 292352 | f211bef28aa106b7e815587d6537d8d6 |
| .rdata | 6291456 | bbf4e058ecd1341a9b65d54f2ce0e185 |
| .data | 708096 | 0f682caf296664761c8392283b7f646b |
| .pdata | 741888 | ebb1451837aa5950f07f4732ceee26b3 |
| .mbrkcf2 | 512 | bf619eac0cdf3f68d496ea9344137e8b |
| _RDATA | 150528 | 02df7da9353eccbe140d6a73d0838671 |
| .rsrc | 27136 | 5913f04aa9207eef0b139ae5a102ef44 |
| .reloc | 125440 | 7d66403eeabc7dcbbb33d73c7b7d9047 |
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.
More information:
