GridinSoft Threat Intelligence

Chrome updater.exe file report

Clean record File reputation report
MD5 029ce2e532fe5c70d3342f978f5463d0
Latest seen 2021-03-08 16:33:55 (5 years ago)
First seen 2021-02-12 04:17:27 (5 years ago)
Size 4 MB
Product Google updater
Signed by Kaspersky Lab

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-02-12 04:17:27 (5 years ago); latest analysis 2021-03-08 16:33:55 (5 years ago).

Publisher context

Product metadata: Google updater.

Digital signature

Signed by Kaspersky Lab. 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.

Chrome updater.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google updater. The current detection status is Clean, based on the latest analysis from 2021-03-08 16:33:55 (5 years 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.

Product Name: Google updater
MD5: 029ce2e532fe5c70d3342f978f5463d0
Size: 4 MB
First Published: 2021-02-12 04:17:27 (5 years ago)
Latest Published: 2021-03-08 16:33:55 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-08 16:33:55 (5 years ago)
Signed By: Kaspersky Lab
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.

%startup%
%temp%

ThreatInfo has observed Chrome updater.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 10 91.7%
Windows 7 8.3%

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

Chrome updater.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 0x00628058
Image base 0x00400000

PE Sections:

Sections 7
Raw data 4587520

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

31232 bytes · 0.7% of section data
Uncommon name
MD5 b74163cdb4731ee5db682fe861638065
4608 bytes · 0.1% of section data
Uncommon name
MD5 e36551d99aee4eb0ff5ace4c44d927e8
512 bytes · 0.0% of section data
Uncommon name
MD5 091d54093b5c65594c9f8ad10589b8bc
.idata 512 bytes · 0.0% of section data
MD5 6f3ad0ddde77ee714e12e35ad65fbb51
.rsrc 12288 bytes · 0.3% of section data
MD5 2fb0deab04aa8f01011044c12b79c70a
.themida 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.boot 4538368 bytes · 98.9% of section data
Uncommon name
MD5 78921bd8d22ade61030b9f17aa61400a

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 029ce2e532fe5c70d3342f978f5463d0.
  • 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.