GridinSoft Threat Intelligence

ChromeRecovery.exe file report

Clean record File reputation report
MD5 ec50fc79055a66f5540fa0f8b067eb1f
Latest seen 2025-03-16 23:03:58 (a year ago)
First seen 2018-02-17 16:05:56 (8 years ago)
Size 1 MB
Publisher Google Inc.
Product Google Update
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-02-17 16:05:56 (8 years ago); latest analysis 2025-03-16 23:03:58 (a year ago).

Publisher context

Company metadata: Google Inc.. Product metadata: Google Update.

Digital signature

Signed by Google 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.

File context

ChromeRecovery.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google Update. The reported company name is Google Inc.. The current detection status is Clean, based on the latest analysis from 2025-03-16 23:03:58 (a year 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.

File Details

Product Name: Google Update
Company Name: Google Inc.
MD5: ec50fc79055a66f5540fa0f8b067eb1f
Size: 1 MB
First Published: 2018-02-17 16:05:56 (8 years ago)
Latest Published: 2025-03-16 23:03:58 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-03-16 23:03:58 (a year ago)

Overview

Signed By: Google 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.

Common Places:

%localappdata%\dayglad\user data\recovery
%localappdata%\coccoc\browser\user data\recovery
%localappdata%\doeye\user data\recovery
%localappdata%\ballcine\user data\recovery
%localappdata%\jamper\user data\recovery
%localappdata%\boxbob\user data\recovery
%appdata%\hola\chromium_profile\recovery
%localappdata%\bigbin\user data\recovery
%localappdata%\cupduck\user data\recovery
%localappdata%\elements browser\user data\recovery

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

Geographic signal

Observed country distribution

ThreatInfo has seen ChromeRecovery.exe across 43 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Vietnam
Share 52.9%
Low High activity

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

OS Version:

Windows 7 49.6%
Windows 10 31.4%
Windows 8.1 11.1%
Windows XP 5.6%
Windows 8 2.1%
Windows Server 2012 R2 0.2%

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

ChromeRecovery.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 0x00058be8
Image base 0x00400000

PE Sections:

Sections 6
Raw data 1675776

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

.text 455168 bytes · 27.2% of section data
MD5 f88adc217ad61eaa5ea7cfbc1caf0423
.rdata 120832 bytes · 7.2% of section data
MD5 b163e3e86b187168655cb91bca2cba49
.data 17408 bytes · 1.0% of section data
MD5 695b86026c71f7685084871d6429515d
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 f6a0e125b9139fc9128579c72a376787
.rsrc 1056256 bytes · 63.0% of section data
MD5 eede2463df4700888f696e65db4685d0
.reloc 25600 bytes · 1.5% of section data
MD5 afefcb46b27b9e0fbea10e935e6587c8

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