GridinSoft Threat Intelligence
chrome_child.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2017-05-25 14:11:15 (9 years ago); latest analysis 2021-01-15 07:03:20 (5 years ago).
Company metadata: UCWeb Inc.. Product metadata: UC Browser.
Signed by TAOBAO (CHINA) SOFTWARE CO.,LTD.. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- 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 2021-01-15 07:03:20 (5 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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: | 1afaa6a8d6e6d2e8d2fccef202143326 |
| Size: | 38 MB |
| First Published: | 2017-05-25 14:11:15 (9 years ago) |
| Latest Published: | 2021-01-15 07:03:20 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-01-15 07:03:20 (5 years ago) |
Overview
| Signed By: | TAOBAO (CHINA) SOFTWARE CO.,LTD. |
| Status: | Invalid (digital signature could be stolen or file could be patched) |
The signature on chrome_child.dll is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.
Common Places:
| %programfiles%\ucbrowser\application\5.5.8071.1004 |
| %desktop%\driver carte mere +carte reseau + carte vga\pc msi\program files (x86)\ucbrowser\application |
| %programfiles%\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 4 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Sudan with 40.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for chrome_child.dll is Windows 10 with 60.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_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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
ff3d45834f70d8bbce805ec3470d7149
b170dffdad2c6c71f010bd1369a787be
ade87c456d9550c3defdc07efaf96b8d
d9743807c2e94baf9597a2c10dada8b6
bf619eac0cdf3f68d496ea9344137e8b
91d262ca2ddef7402f71dc1e3bc531ab
d26f204751238f774810ef0abefc1cba
66ddd0d9e0a4d76a8b9b2e94f2859306
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.