chrome_child.dll file report
ThreatInfo file report
chrome_child.dll
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-05-21 10:03:24 (8 years ago); latest analysis 2024-12-19 23:03:22 (a year ago).
Company metadata: Google Inc.. Product metadata: Google Chrome.
Signed by Google Inc. 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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
chrome_child.dll is a Windows file recorded in the ThreatInfo database. It is associated with Google Chrome. The reported company name is Google Inc.. The current detection status is Clean, based on the latest analysis from 2024-12-19 23:03:22 (a year ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Google Chrome |
| Company Name: | Google Inc. |
| MD5: | ac9f025d821a40f31dbffde53cc06fed |
| Size: | 32 MB |
| First Published: | 2017-05-21 10:03:24 (8 years ago) |
| Latest Published: | 2024-12-19 23:03:22 (a year ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-12-19 23:03:22 (a year ago) |
Overview
| Signed By: | Google Inc |
| 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:
| %appdata%\chportu\app\chrome-bin\39.0.2171.95 |
| %appdata%\chportu\app\chrome-bin |
| %appdata%\chportu\app\chrome-bin |
| %appdata%\chportu\app\chrome-bin |
| %appdata%\chportu\app\chrome-bin |
| %appdata%\chportu\app\chrome-bin |
| %appdata%\chportu\app\chrome-bin |
| %appdata%\chportu\app\chrome-bin |
| %appdata%\chportu\app\chrome-bin |
| %appdata%\chportu\app\chrome-bin |
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.
Geography:
| 17.9% | ||
| 7.5% | ||
| 7.0% | ||
| 6.5% | ||
| 5.5% | ||
| 4.5% | ||
| 4.5% | ||
| 4.0% | ||
| 3.0% | ||
| 3.0% | ||
| 2.5% | ||
| 2.5% | ||
| 2.0% | ||
| 2.0% | ||
| 1.5% | ||
| 1.5% | ||
| 1.5% | ||
| 1.5% | ||
| 1.5% | ||
| 1.5% | ||
| 1.5% | ||
| 1.5% | ||
| 1.0% | ||
| 1.0% | ||
| 1.0% | ||
| 1.0% | ||
| 1.0% | ||
| 1.0% | ||
| 1.0% | ||
| 1.0% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% |
The strongest geographic signal for this file is Turkey with 17.9% 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 | 61.6% | |
| Windows 7 | 30.0% | |
| Windows 8.1 | 6.9% | |
| Windows 8 | 1.0% | |
| Windows Vista | 0.5% |
The most common operating system signal for chrome_child.dll is Windows 10 with 61.6% 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 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.
| Subsystem: | Windows CUI |
| PE Type: | pe |
| OS Bitness: | 32 |
| Image Base: | 0x10000000 |
| Entry Address: | 0x000010e6 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 24751616 | 386223e9435ad578e3d36c4c8141585d |
| .rdata | 7877632 | b58b69f955d3a5b6c4fb99ba22f7984d |
| .data | 323072 | 70c8e09a7f48552d6f2a0d35caa162b5 |
| .tls | 512 | bf619eac0cdf3f68d496ea9344137e8b |
| .rodata | 4608 | bd222cfddb36edca11f5262c49f502ad |
| _RDATA | 2560 | da55554d0f358304af75f0cd4b819799 |
| .syzygy | 1536 | 946901ef71913d3fca3e52cce85e4095 |
| .rsrc | 2048 | 3e7b0c18a73ee21a9e72833e53321545 |
| .reloc | 1042944 | 1d9546252696fb3a970e986f4c901c3d |
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.
More information:
