GridinSoft Threat Intelligence

chrome.dll file report

Under review File reputation report
MD5 53cca85a612f958f9ed6272f2505e41a
Latest seen 2024-12-30 23:01:50 (a year ago)
First seen 2017-07-26 04:13:49 (8 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-07-26 04:13:49 (8 years ago); latest analysis 2024-12-30 23:01:50 (a year 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 2024-12-30 23:01:50 (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: UC Browser
Company Name: UCWeb Inc.
MD5: 53cca85a612f958f9ed6272f2505e41a
Size: 37 MB
First Published: 2017-07-26 04:13:49 (8 years ago)
Latest Published: 2024-12-30 23:01:50 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-12-30 23:01:50 (a year 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\6.0.1308.1016
%programfiles%\ucbrowser\application
%sysdrive%\windows.old.000\program files (x86)\ucbrowser\application
%sysdrive%\ucbrowser\application
%sysdrive%\sandbox\mc_donald\defaultbox\drive\c\program files (x86)\ucbrowser\application

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 28 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Indonesia
Share 18.7%
Low High activity

The strongest geographic signal for this file is Indonesia with 18.7% 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 69.4%
Windows 7 22.4%
Windows 8 4.1%
Windows 8.1 2.0%
Windows Vista 1.0%
Windows Embedded 8.1 1.0%

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

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

.text 30571008 bytes · 77.2% of section data
Large raw data
MD5 3f729be211e3f697040c33d1b5aae610
.rdata 7002624 bytes · 17.7% of section data
Large raw data
MD5 3f14e36ab736e8d40d77de90bfeb0abf
.data 451584 bytes · 1.1% of section data
MD5 eda5c2949eee44cf3948761cc00e88c7
.tls 5120 bytes · 0.0% of section data
MD5 4b15e517da8bd74a65f130524b69ffd6
.gfids 1536 bytes · 0.0% of section data
Uncommon name
MD5 772db91453517ba98f40ef19b0a2a43c
_RDATA 4608 bytes · 0.0% of section data
Uncommon name
MD5 04b7076e7e14904422a8df2a5709fc49
.syzygy 1536 bytes · 0.0% of section data
Uncommon name
MD5 4a13b7e10052996e313487fab8b86947
.rsrc 150528 bytes · 0.4% of section data
MD5 b14bcad11c0b909e366e537ce5747cb5
.reloc 1413632 bytes · 3.6% of section data
MD5 4a20d51e04d12f5af4810d64711ff5b9

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 53cca85a612f958f9ed6272f2505e41a.
  • 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.