chrome_child_IObitDel.dll file report

MD5 49bbad0a5eb8c6690f25d4f4ddd435cd
Latest seen 2026-02-11 23:01:34 (3 months ago)
First seen 2018-07-28 04:07:18 (7 years ago)
Size 48 MB
Publisher WebDiscover Media
Signed by web discover

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-07-28 04:07:18 (7 years ago); latest analysis 2026-02-11 23:01:34 (3 months ago).

Publisher context

Company metadata: WebDiscover Media. Product metadata: WebDiscover Browser.

Digital signature

Signed by web discover. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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_IObitDel.dll is a Windows file recorded in the ThreatInfo database. It is associated with WebDiscover Browser. The reported company name is WebDiscover Media. The current detection status is Undefined, based on the latest analysis from 2026-02-11 23:01:34 (3 months 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: WebDiscover Browser
Company Name: WebDiscover Media
MD5: 49bbad0a5eb8c6690f25d4f4ddd435cd
Size: 48 MB
First Published: 2018-07-28 04:07:18 (7 years ago)
Latest Published: 2026-02-11 23:01:34 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-11 23:01:34 (3 months ago)
Signed By: web discover
Status: Valid

The signature on chrome_child_IObitDel.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.

%programfiles%\webdiscoverbrowser
%localappdata%\webdiscoverbrowser
%programfiles%\webdiscoverbrowser
%programfiles%\webdiscoverbrowser
%programfiles%\webdiscoverbrowser
%programfiles%\webdiscoverbrowser
%programfiles%\webdiscoverbrowser
%programfiles%\webdiscoverbrowser
%programfiles%\webdiscoverbrowser
%programfiles%\webdiscoverbrowser

ThreatInfo has observed chrome_child_IObitDel.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.

chrome_child.dll
chrome_child_IObitDel.dll

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

25.6%
23.9%
13.2%
5.4%
5.0%
3.9%
2.8%
2.4%
2.1%
1.7%
1.5%
1.3%
1.1%
1.1%
1.1%
0.7%
0.7%
0.6%
0.6%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%

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

Windows 10 68.6%
Windows 7 28.5%
Windows 8.1 2.5%
Windows 8 0.4%

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

chrome_child_IObitDel.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: 0x01a311c2

PE Sections:

Name Size of data MD5
.text 39223296 ae2682212076828e7b8e770cf5452daf
_text32 54784 27c54634d63f6d20a0262e78e38c6eaa
.rdata 10040832 1d199e8e7e16c8049cf788ad7fd37c4d
.data 328704 f9ed1154be0e0e2e7078725af54111af
.rodata 5632 1fc256eca633effac133eb08ded9a867
CPADinfo 512 d273139d7dd4280f40c57791927d34c6
.rsrc 52736 ce2f9641dcf198d0adb5020de66470be
.reloc 1462784 897d404800a57393773c21fbc86ba3ba

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: