GridinSoft Threat Intelligence

gchrome.exe file report

Under review File reputation report
MD5 38372aa4cc9fbd0eb7a26fc7b5f24562
Latest seen 2025-03-16 23:03:36 (a year ago)
First seen 2017-06-10 15:10:27 (8 years ago)
Size 923 KB
Publisher Google Inc.
Product Google Chrome
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-06-10 15:10:27 (8 years ago); latest analysis 2025-03-16 23:03:36 (a year ago).

Publisher context

Company metadata: Google Inc.. Product metadata: Google Chrome.

Digital signature

Signed by Google Inc. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

File context

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

File Details

Product Name: Google Chrome
Company Name: Google Inc.
MD5: 38372aa4cc9fbd0eb7a26fc7b5f24562
Size: 923 KB
First Published: 2017-06-10 15:10:27 (8 years ago)
Latest Published: 2025-03-16 23:03:36 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-03-16 23:03:36 (a year ago)

Overview

Signed By: Google Inc
Status: Valid

The signature on gchrome.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%\footper\application
%programfiles%\ballduck\application
%programfiles%\coldmay\application
%programfiles%\cansuck\application
%programfiles%\birdjob\application
%programfiles%\noflat\application
%appdata%\browsers
%programfiles%\hipmy\application
%programfiles%\ballcine\application
%programfiles%\tooltony\application

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

File Names:

4 observed names
chrome.exe chrome.bat.exe chrome1.exe gchrome.exe

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Geographic signal

Observed country distribution

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

Top country Ukraine
Share 25.2%
Low High activity

The strongest geographic signal for this file is Ukraine with 25.2% 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 45.7%
Windows 7 43.4%
Windows 8.1 10.1%
Windows Vista 0.4%
Windows 8 0.4%

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

Analysis

gchrome.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 0x0006c070
Image base 0x00400000

PE Sections:

Sections 7
Raw data 937472

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

.text 578560 bytes · 61.7% of section data
MD5 d8cff1a4a8ea924c0fc322e4ef1a7d5c
.rdata 184320 bytes · 19.7% of section data
MD5 991efd1d6b5f22143f6050855349f045
.data 4096 bytes · 0.4% of section data
MD5 0ad9cee8d701f2679a45116136e27cec
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 cb4287fd8113b70d11433f5eed5b489d
.tls 512 bytes · 0.1% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 144896 bytes · 15.5% of section data
MD5 ba4a7d0532618dc91226252180f81516
.reloc 24576 bytes · 2.6% of section data
MD5 e22e2c5efd6da6d9170380c60ce21d85

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 38372aa4cc9fbd0eb7a26fc7b5f24562.
  • 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.