GridinSoft Threat Intelligence

chrome_child.dll file report

Under review File reputation report
MD5 2387158a2160a0b4197aec6fb014c0f8
Latest seen 2021-01-12 04:39:45 (5 years ago)
First seen 2018-06-03 08:12:26 (7 years ago)
Size 55 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-06-03 08:12:26 (7 years ago); latest analysis 2021-01-12 04:39:45 (5 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-01-12 04:39:45 (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: 360极速浏览器
Company Name: 360.cn
MD5: 2387158a2160a0b4197aec6fb014c0f8
Size: 55 MB
First Published: 2018-06-03 08:12:26 (7 years ago)
Latest Published: 2021-01-12 04:39:45 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-12 04:39:45 (5 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:

%localappdata%\360chrome\chrome\application
%profile%\dmin\local settings\application data\360chrome\chrome\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.

Top country China
Share 57.1%
Low High activity

The strongest geographic signal for this file is China with 57.1% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows Server 2012 R2 71.4%
Windows 7 14.3%
Windows XP 14.3%

The most common operating system signal for chrome_child.dll is Windows Server 2012 R2 with 71.4% 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 0x00001244
Image base 0x10000000

PE Sections:

Sections 10
Raw data 57962496

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

.text 45488128 bytes · 78.5% of section data
Large raw data
MD5 10c2da6bf8a9e3b62376d0edc0dbdb0a
_text32 54784 bytes · 0.1% of section data
Uncommon name
MD5 ef92ae8dad06fa8376e4c41af70480b1
.rdata 9692160 bytes · 16.7% of section data
Large raw data
MD5 777ee6b99334061b750b6f27eccb7e7c
.data 842752 bytes · 1.5% of section data
MD5 fefe0f8e3c431685dbb0d67699d73b4c
.rodata 11776 bytes · 0.0% of section data
MD5 62e55bd76a929d35461a325caa1b1863
.content 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
_RDATA 5120 bytes · 0.0% of section data
Uncommon name
MD5 b435bad5b29a42e1a2d991dcf8ea5d81
.syzygy 1536 bytes · 0.0% of section data
Uncommon name
MD5 a81f941a51663b4faaf2543360e3d323
.rsrc 52736 bytes · 0.1% of section data
MD5 f5b1e166f879ee1cf5a91ca41ff25999
.reloc 1812992 bytes · 3.1% of section data
MD5 6c3c4e646bf67c2f51b7b94fef5568fc

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 2387158a2160a0b4197aec6fb014c0f8.
  • 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.