GridinSoft Threat Intelligence

chrome.bat.exe file report

Clean record File reputation report
MD5 637657735864768eb5378b5aa51919a2
Latest seen 2022-02-05 21:12:34 (4 years ago)
First seen 2017-05-21 12:06:14 (8 years ago)
Size 953 KB
Publisher Google Inc.
Product Google Chrome
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 12:06:14 (8 years ago); latest analysis 2022-02-05 21:12:34 (4 years 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. 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

chrome.bat.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 Clean, based on the latest analysis from 2022-02-05 21:12:34 (4 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.

File Details

Product Name: Google Chrome
Company Name: Google Inc.
MD5: 637657735864768eb5378b5aa51919a2
Size: 953 KB
First Published: 2017-05-21 12:06:14 (8 years ago)
Latest Published: 2022-02-05 21:12:34 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-02-05 21:12:34 (4 years ago)

Overview

Signed By: Google Inc
Status: Valid

The signature on chrome.bat.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%\google\chrome\application
%localappdata%\google\chrome\application
%appdata%\browsers
%programfiles%\fanlook\application
%programfiles%\lll\chrome\application
%programfiles%\applemy\application
%programfiles%\fanlook
%programfiles%\applemy
%appdata%
%programfiles%\google\chrome

ThreatInfo has observed chrome.bat.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:

2 observed names
chrome.exe chrome.bat.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 chrome.bat.exe across 46 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Indonesia
Share 24.2%
Low High activity

The strongest geographic signal for this file is Indonesia with 24.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 7 59.8%
Windows 10 21.3%
Windows 8.1 16.9%
Windows 8 1.7%
Windows Vista 0.3%

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

chrome.bat.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 0x00070a70
Image base 0x00400000

PE Sections:

Sections 7
Raw data 968192

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

.text 599552 bytes · 61.9% of section data
MD5 76b24afee77ba2a66b0b997da6c8edcc
.rdata 193536 bytes · 20.0% of section data
MD5 072fc7a44fd1fc302b7c19a9b8167597
.data 4096 bytes · 0.4% of section data
MD5 62bf83fdbf5add25dac704713a548882
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 8e72c80aa9b34b34fbf5af76ea5521cf
.tls 512 bytes · 0.1% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 144896 bytes · 15.0% of section data
MD5 dac5112464aaee3aac4fdcf38e794152
.reloc 25088 bytes · 2.6% of section data
MD5 7ce40bbfd223e9a15cc3c43280f2d69a

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 637657735864768eb5378b5aa51919a2.
  • 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.