GridinSoft Threat Intelligence

chrome_child.dll file report

Under review File reputation report
MD5 d6598018b3ab671d65cb6a3d67fe8c19
Latest seen 2024-12-30 23:01:48 (a year ago)
First seen 2017-07-26 04:13:49 (8 years ago)
Size 43 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:48 (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_child.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:48 (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: d6598018b3ab671d65cb6a3d67fe8c19
Size: 43 MB
First Published: 2017-07-26 04:13:49 (8 years ago)
Latest Published: 2024-12-30 23:01:48 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-12-30 23:01:48 (a year ago)

Overview

Signed By: TAOBAO (CHINA) SOFTWARE CO.,LTD.
Status: Valid

The signature on chrome_child.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_child.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_child.dll across 27 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Indonesia
Share 19.3%
Low High activity

The strongest geographic signal for this file is Indonesia with 19.3% 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.5%
Windows 7 22.1%
Windows 8 4.2%
Windows 8.1 2.1%
Windows Vista 1.1%
Windows Embedded 8.1 1.1%

The most common operating system signal for chrome_child.dll is Windows 10 with 69.5% 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_child.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x00001155
Image base 0x10000000

PE Sections:

Sections 10
Raw data 45962752

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

.text 34652160 bytes · 75.4% of section data
Large raw data
MD5 2f5b092f1eb460599c36c4a4c0a2965e
.rdata 9283584 bytes · 20.2% of section data
Large raw data
MD5 3d32f7de72b583ddc7670f15669404b8
.data 669184 bytes · 1.5% of section data
MD5 ad172e2b94a30a949b06f004bbcdeaca
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rodata 18432 bytes · 0.0% of section data
MD5 4baade15bdf2e515b7383bccdb223119
.gfids 1024 bytes · 0.0% of section data
Uncommon name
MD5 c8fd0670c6442ccb766205ccaf9145b7
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 541ae312af8f5981a726b33a1eae1f6e
.syzygy 1536 bytes · 0.0% of section data
Uncommon name
MD5 48e9bb77e23d8c743490acf31a98bfa7
.rsrc 2048 bytes · 0.0% of section data
MD5 dec90682c8156155b3bf49ff851eff5f
.reloc 1333760 bytes · 2.9% of section data
MD5 8a897480ef113dbe9b115657fffa9a1d

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