GridinSoft Threat Intelligence
chrome_child.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2018-04-14 11:05:55 (8 years ago); latest analysis 2021-04-19 20:34:58 (5 years ago).
Company metadata: Dilane Limited. Product metadata: FreeU.
Signed by Dilane Limited. The signature is reported as valid, but signed files can still be bundled or abused.
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 FreeU. The reported company name is Dilane Limited. The current detection status is Undefined, based on the latest analysis from 2021-04-19 20:34:58 (5 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: | FreeU |
| Company Name: | Dilane Limited |
| MD5: | 513b506de43f154281f531b6f53a29b0 |
| Size: | 50 MB |
| First Published: | 2018-04-14 11:05:55 (8 years ago) |
| Latest Published: | 2021-04-19 20:34:58 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-04-19 20:34:58 (5 years ago) |
Overview
| Signed By: | Dilane Limited |
| 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:
| %localappdata%\freeu\application |
| %sysdrive%\$recycle.bin\s-1-5-21-350995509-4268402254-3549953969-500\$r4d5x0m\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 5 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Ukraine with 83.3% 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 55.3% 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.
36b8b66ca2de7fdc1121d885e46f7bca
87e937cf44f053d613df8eff66e017f5
fa844697c95754b4d61f1165faf06cf9
1c95cd7cd54373b288d5e2ebce7b1bca
9efa43af7b1faae15ffbd428d0485819
48e40c5b5c86e7ba76130735c5246f56
772e8bf84366a29740871ecccd28de05
6a4d701a80c9128ba46180eb8218a58f
d273139d7dd4280f40c57791927d34c6
5a24dee92bc8d50e71a82b572499d88f
6d8aee4aa3d926c6c50f49b33f28790a
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.