GridinSoft Threat Intelligence

chrome_child.dll file report

Under review File reputation report
MD5 4a9546336bf8c85cc8893236faa61443
Latest seen 2021-01-03 13:50:34 (5 years ago)
First seen 2017-10-01 15:06:33 (8 years ago)
Size 48 MB
Publisher Google Inc.
Product Applemy

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-10-01 15:06:33 (8 years ago); latest analysis 2021-01-03 13:50:34 (5 years ago).

Publisher context

Company metadata: Google Inc.. Product metadata: Applemy.

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.

chrome_child.dll is a Windows file recorded in the ThreatInfo database. It is associated with Applemy. The reported company name is Google Inc.. The current detection status is Undefined, based on the latest analysis from 2021-01-03 13:50:34 (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.

Product Name: Applemy
Company Name: Google Inc.
MD5: 4a9546336bf8c85cc8893236faa61443
Size: 48 MB
First Published: 2017-10-01 15:06:33 (8 years ago)
Latest Published: 2021-01-03 13:50:34 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-03 13:50:34 (5 years ago)
%programfiles%\applemy\application
%programfiles%\applemy

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.

Windows 10 44.4%
Windows 7 33.3%
Windows 8.1 16.7%
Windows 8 5.6%

The most common operating system signal for chrome_child.dll is Windows 10 with 44.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.

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 0x01f1e940
Image base 0x10000000

PE Sections:

Sections 9
Raw data 50729472

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

.text 39913984 bytes · 78.7% of section data
Large raw data
MD5 c1d017632b3cfc40fad2608027fef777
.rdata 8986112 bytes · 17.7% of section data
Large raw data
MD5 b160fca7899560ed21348078afc12932
.data 321024 bytes · 0.6% of section data
MD5 7d9765e1f9dcd51f4386e1298a2426cf
.didat 512 bytes · 0.0% of section data
Uncommon name
MD5 2e907f5a547aa9ccb3c7df2e898a4c65
.tls 512 bytes · 0.0% of section data
MD5 9efa43af7b1faae15ffbd428d0485819
.rodata 11776 bytes · 0.0% of section data
MD5 b4d7e1a9ef00c79e3fcb7bbb2c24a418
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 541ae312af8f5981a726b33a1eae1f6e
.rsrc 52224 bytes · 0.1% of section data
MD5 5d426d0a420d443e32aaf2d6523eb21c
.reloc 1442816 bytes · 2.8% of section data
MD5 56f1db1d437de6f835fd8f82c5d57638

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 4a9546336bf8c85cc8893236faa61443.
  • 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.