GridinSoft Threat Intelligence

chrome.dll file report

Clean record File reputation report
MD5 e00de70e27713260b12b67e9bffb78eb
Latest seen 2024-12-19 23:03:22 (a year ago)
First seen 2017-05-21 10:03:24 (8 years ago)
Size 30 MB
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 10:03:24 (8 years ago); latest analysis 2024-12-19 23:03:22 (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.

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.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 2024-12-19 23:03:22 (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.

Product Name: Google Chrome
Company Name: Google Inc.
MD5: e00de70e27713260b12b67e9bffb78eb
Size: 30 MB
First Published: 2017-05-21 10:03:24 (8 years ago)
Latest Published: 2024-12-19 23:03:22 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2024-12-19 23:03:22 (a year ago)
Signed By: Google Inc
Status: Valid

The signature on chrome.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.

%appdata%\chportu\app\chrome-bin\39.0.2171.95
%appdata%\chportu\app\chrome-bin

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

Windows 10 60.8%
Windows 7 30.9%
Windows 8.1 6.9%
Windows 8 1.0%
Windows Vista 0.5%

The most common operating system signal for chrome.dll is Windows 10 with 60.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.

chrome.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 0x000010f0
Image base 0x01c30000

PE Sections:

Sections 9
Raw data 32215040

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

.text 24105984 bytes · 74.8% of section data
Large raw data
MD5 1f9ce8d1d9b0263e9c2a08fddcfbf172
.rdata 6627328 bytes · 20.6% of section data
Large raw data
MD5 436d6408d02b3b6f7728f9cdf6291889
.data 286208 bytes · 0.9% of section data
MD5 cb6290df2187dd9640a3966885faad27
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rodata 4608 bytes · 0.0% of section data
MD5 bd222cfddb36edca11f5262c49f502ad
_RDATA 2560 bytes · 0.0% of section data
Uncommon name
MD5 da55554d0f358304af75f0cd4b819799
.syzygy 1536 bytes · 0.0% of section data
Uncommon name
MD5 dd23c54ee5dcbab14599d96b7c9152e8
.rsrc 176128 bytes · 0.5% of section data
MD5 06ccb521715f829454ba0aed2b2ebaa7
.reloc 1010176 bytes · 3.1% of section data
MD5 632b1fc77a8803f4e6bcaa9ddea90236

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