GridinSoft Threat Intelligence

chrome_watcher.dll file report

Clean record File reputation report
MD5 e1e49914ac0881f3075e128fec0acaf5
Latest seen 2021-01-13 03:57:59 (5 years ago)
First seen 2017-05-21 14:10:02 (9 years ago)
Size 460 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 14:10:02 (9 years ago); latest analysis 2021-01-13 03:57:59 (5 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.

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_watcher.dll 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 2021-01-13 03:57:59 (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.

File Details

Product Name: Google Chrome
Company Name: Google Inc.
MD5: e1e49914ac0881f3075e128fec0acaf5
Size: 460 KB
First Published: 2017-05-21 14:10:02 (9 years ago)
Latest Published: 2021-01-13 03:57:59 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-13 03:57:59 (5 years ago)

Overview

Signed By: Google Inc
Status: Valid

The signature on chrome_watcher.dll 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%\bigmay\application
%programfiles%\shutness\application
%programfiles%\mapbob\application
%programfiles%\ontoe\application
%programfiles%\zooarm\application
%programfiles%\baghair\application
%programfiles%\bangkiss\application
%programfiles%\bemike\application
%programfiles%\nosekiss\application
%programfiles%\inper\application

ThreatInfo has observed chrome_watcher.dll 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 chrome_watcher.dll across 25 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Vietnam
Share 15.8%
Low High activity

The strongest geographic signal for this file is Vietnam with 15.8% 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 44.1%
Windows 10 28.4%
Windows 8.1 25.5%
Windows 8 1.0%
Windows Server 2012 R2 1.0%

The most common operating system signal for chrome_watcher.dll is Windows 7 with 44.1% 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_watcher.dll 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 0x0003b6a9
Image base 0x10000000

PE Sections:

Sections 7
Raw data 457728

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

.text 360448 bytes · 78.7% of section data
MD5 599abf46d25c4e77e6d0801c656312f5
.rdata 74240 bytes · 16.2% of section data
MD5 8733135b515da161e286863f46c85e44
.data 5120 bytes · 1.1% of section data
MD5 c48f49079d6a695045da15bc7b149475
.gfids 1024 bytes · 0.2% of section data
Uncommon name
MD5 def02a04e114cf9ca823bc3f2de37918
.tls 512 bytes · 0.1% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1536 bytes · 0.3% of section data
MD5 aed5e42f57d986deefc77effda9b0712
.reloc 14848 bytes · 3.2% of section data
MD5 5cbab0b3bd35e416bc3b4f099cf04280

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