GridinSoft Threat Intelligence

chrome_child.dll file report

Under review File reputation report
MD5 dca088a6dff96440b167c2b9a9ebac78
Latest seen 2021-06-16 20:45:54 (4 years ago)
First seen 2018-08-01 14:07:19 (7 years ago)
Size 38 MB
Publisher 360.cn
Product 360安全浏览器
Signed by Qihoo 360 Software (Beijing) Company Limited

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-08-01 14:07:19 (7 years ago); latest analysis 2021-06-16 20:45:54 (4 years ago).

Publisher context

Company metadata: 360.cn. Product metadata: 360安全浏览器.

Digital signature

Signed by Qihoo 360 Software (Beijing) Company Limited. 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 360安全浏览器. The reported company name is 360.cn. The current detection status is Undefined, based on the latest analysis from 2021-06-16 20:45:54 (4 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: 360安全浏览器
Company Name: 360.cn
MD5: dca088a6dff96440b167c2b9a9ebac78
Size: 38 MB
First Published: 2018-08-01 14:07:19 (7 years ago)
Latest Published: 2021-06-16 20:45:54 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-06-16 20:45:54 (4 years ago)

Overview

Signed By: Qihoo 360 Software (Beijing) Company 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:

%appdata%\360se6\application
%system%\config\systemprofile\appdata\roaming\360se6\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 7 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Taiwan
Share 31.8%
Low High activity

The strongest geographic signal for this file is Taiwan with 31.8% 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 63.6%
Windows 7 22.7%
Windows 8.1 9.1%
Windows Server 2008 R2 4.5%

The most common operating system signal for chrome_child.dll is Windows 10 with 63.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-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 0x00001145
Image base 0x10000000

PE Sections:

Sections 11
Raw data 40290304

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

.text 29146112 bytes · 72.3% of section data
Large raw data
MD5 cc1242502d08e2087f7f8dc0ebaa2109
.rdata 8973824 bytes · 22.3% of section data
Large raw data
MD5 1084f9c3c882ea21e5267a4d7dc5303b
.data 808448 bytes · 2.0% of section data
MD5 b1d505abe8b073aa42a6cf760d60d5e3
.rodata 7168 bytes · 0.0% of section data
MD5 00c7ebd44b77f16c30a77cb099f434c5
.gfids 2560 bytes · 0.0% of section data
Uncommon name
MD5 e0ae0a2a4c1263cb0ae3f3960be740c5
.tls 512 bytes · 0.0% of section data
MD5 edda25907019e5cc74c177f6952e5e4b
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 6a4d701a80c9128ba46180eb8218a58f
.content 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.syzygy 1536 bytes · 0.0% of section data
Uncommon name
MD5 d3dc1925b9f3e4b636f9f9c537d19af6
.rsrc 52736 bytes · 0.1% of section data
MD5 f225103b6182308f907456c41c34872f
.reloc 1296384 bytes · 3.2% of section data
MD5 208bc393a33f44444abf3a70c8abad98

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