crashreporter64.exe file report

MD5 679e505358122b4bd6b4c3683a661bf5
Latest seen 2022-12-29 23:43:53 (3 years ago)
First seen 2019-11-14 05:47:48 (6 years ago)
Size 1 MB
Publisher Yandex LLC
Product Voice assistant
Signed by YANDEX LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-11-14 05:47:48 (6 years ago); latest analysis 2022-12-29 23:43:53 (3 years ago).

Publisher context

Company metadata: Yandex LLC. Product metadata: Voice assistant.

Digital signature

Signed by YANDEX LLC. 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.

crashreporter64.exe is a Windows file recorded in the ThreatInfo database. It is associated with Voice assistant. The reported company name is Yandex LLC. The current detection status is Undefined, based on the latest analysis from 2022-12-29 23:43:53 (3 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: Voice assistant
Company Name: Yandex LLC
MD5: 679e505358122b4bd6b4c3683a661bf5
Size: 1 MB
First Published: 2019-11-14 05:47:48 (6 years ago)
Latest Published: 2022-12-29 23:43:53 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-12-29 23:43:53 (3 years ago)
Signed By: YANDEX LLC
Status: Valid

The signature on crashreporter64.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.

%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application
%localappdata%\yandex\searchband\application

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

73.2%
12.5%
3.6%
3.6%
1.8%
1.8%
1.8%
1.8%

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

Windows 10 55.4%
Windows 7 23.2%
Windows 8.1 16.1%
Windows 8 5.4%

The most common operating system signal for crashreporter64.exe is Windows 10 with 55.4% 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.

crashreporter64.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: 0x000aadfc

PE Sections:

Name Size of data MD5
.text 861184 d0e90a9348882313ef9b4eac1de300b1
.rdata 243200 7f6f5fdfe339a9ca9494ba92e6579798
.data 29696 def357da46cc24f4653959b8d7f61f3c
.pdata 34304 17a42b154d061dcfc46cde52404f46e8
.rsrc 144384 83c97436846bfdc7a0e6898b71728c5f
.reloc 9728 76fe2d88094e62b4c190906b604fd3ae

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: