GridinSoft Threat Intelligence

chrome.dll file report

Under review File reputation report
MD5 eedac8d5d291ec01f6080870ae4d68c3
Latest seen 2023-01-11 23:01:33 (3 years ago)
First seen 2017-05-25 06:06:07 (9 years ago)
Size 37 MB
Publisher UCWeb Inc.
Product UC Browser
Signed by TAOBAO (CHINA) SOFTWARE CO.,LTD.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-25 06:06:07 (9 years ago); latest analysis 2023-01-11 23:01:33 (3 years ago).

Publisher context

Company metadata: UCWeb Inc.. Product metadata: UC Browser.

Digital signature

Signed by TAOBAO (CHINA) SOFTWARE CO.,LTD.. 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. 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

chrome.dll is a Windows file recorded in the ThreatInfo database. It is associated with UC Browser. The reported company name is UCWeb Inc.. The current detection status is Undefined, based on the latest analysis from 2023-01-11 23:01:33 (3 years 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: UC Browser
Company Name: UCWeb Inc.
MD5: eedac8d5d291ec01f6080870ae4d68c3
Size: 37 MB
First Published: 2017-05-25 06:06:07 (9 years ago)
Latest Published: 2023-01-11 23:01:33 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-01-11 23:01:33 (3 years ago)

Overview

Signed By: TAOBAO (CHINA) SOFTWARE CO.,LTD.
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.

Common Places:

%programfiles%\ucbrowser\application\5.7.16281.1003
%programfiles%\ucbrowser\application
%sysdrive%\system volume information\_restore{6b55c65a-c839-44c2-b549-64136334187b}

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.

Geographic signal

Observed country distribution

ThreatInfo has seen chrome.dll across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Indonesia
Share 80.0%
Low High activity

The strongest geographic signal for this file is Indonesia with 80.0% 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 80.0%
Windows 8 20.0%

The most common operating system signal for chrome.dll is Windows 7 with 80.0% 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.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 0x0000115f
Image base 0x01c30000

PE Sections:

Sections 9
Raw data 39343104

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

.text 30395392 bytes · 77.3% of section data
Large raw data
MD5 71c4caeadad7621aaf18376edb0c5f71
.rdata 6956032 bytes · 17.7% of section data
Large raw data
MD5 f0b70307cf77073327c3407e7444298a
.data 430080 bytes · 1.1% of section data
MD5 1a494611fc04baec2b2012cbcc0a36e8
.tls 5120 bytes · 0.0% of section data
MD5 4b15e517da8bd74a65f130524b69ffd6
.gfids 1536 bytes · 0.0% of section data
Uncommon name
MD5 79bc63d625593c62638de74bc544c23a
_RDATA 4608 bytes · 0.0% of section data
Uncommon name
MD5 04b7076e7e14904422a8df2a5709fc49
.syzygy 1536 bytes · 0.0% of section data
Uncommon name
MD5 94c1b70683961a11eb05914b10961ae4
.rsrc 150528 bytes · 0.4% of section data
MD5 a2b836099fab1be43b4982f2f403543a
.reloc 1398272 bytes · 3.6% of section data
MD5 893b072000c13fd7c629fd6e1cf8cd23

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