GridinSoft Threat Intelligence

widevinecdm_IObitDel.dll file report

Clean record File reputation report
MD5 75bb7fd4799a6801b4e2c0ca160f09b3
Latest seen 2025-04-12 23:02:38 (a year ago)
First seen 2017-05-21 03:02:05 (9 years ago)
Size 7 MB
Publisher Google Inc.
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 03:02:05 (9 years ago); latest analysis 2025-04-12 23:02:38 (a year ago).

Publisher context

Company metadata: Google Inc.. Product metadata: Widevine Content Decryption Module.

Digital signature

Signed by Google Inc. 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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

widevinecdm_IObitDel.dll is a Windows file recorded in the ThreatInfo database. It is associated with Widevine Content Decryption Module. The reported company name is Google Inc.. The current detection status is Clean, based on the latest analysis from 2025-04-12 23:02:38 (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.

Product Name: Widevine Content Decryption Module
Company Name: Google Inc.
MD5: 75bb7fd4799a6801b4e2c0ca160f09b3
Size: 7 MB
First Published: 2017-05-21 03:02:05 (9 years ago)
Latest Published: 2025-04-12 23:02:38 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-04-12 23:02:38 (a year ago)
Signed By: Google Inc
Status: Valid

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

%localappdata%\browserair\application\widevinecdm\1.4.8.866\_platform_specific\win_x86
%appdata%\profiles\phogotion.default\gmp-widevinecdm\1.4.8.866
%localappdata%\3810282d-6c19-47b0-8283-5c6c29a7e108\widevinecdm\1.4.8.866\_platform_specific\win_x86
%localappdata%\peaellz\user data\widevinecdm\1.4.8.866\_platform_specific\win_x86
%appdata%\profiles\aredetahedom.default\gmp-widevinecdm\1.4.8.866
%appdata%\profiles\bgercultchrose.default\gmp-widevinecdm\1.4.8.866
%appdata%\profiles\beserdomjerdasy.default\gmp-widevinecdm\1.4.8.866
%appdata%\profiles\thrlecqupyqagertain\gmp-widevinecdm\1.4.8.866
%appdata%\profiles\bvakdrocghtcouhaied\gmp-widevinecdm\1.4.8.866
%profile%\eep\local settings\application data\3810282d-6c19-47b0-8283-5c6c29a7e108\widevinecdm\1.4.8.866\_platform_specific\win_x86

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

widevinecdm.dll widevinecdm_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.

Windows 10 43.4%
Windows 7 41.2%
Windows 8.1 11.8%
Windows 8 1.7%
Windows XP 1.2%
Windows Server 2012 R2 0.5%
Windows Vista 0.2%

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

widevinecdm_IObitDel.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 0x003de5eb
Image base 0x10000000

PE Sections:

Sections 10
Raw data 7984640

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

.text 4222976 bytes · 52.9% of section data
MD5 9a6850af856bf5c6d7a668b6b445bf37
.rdata 1147904 bytes · 14.4% of section data
MD5 49b40f98ff7ff65828a1ba5fb5e54253
.data 956928 bytes · 12.0% of section data
MD5 eeb4d101dfb912ee3e9221124263b30f
.rodata 4608 bytes · 0.1% of section data
MD5 28a1caf133ef4221c59fcffb8363ffb7
.tls 512 bytes · 0.0% of section data
MD5 fa7d484c8c4c13d0e968cce3ade179c7
_RDATA 1536 bytes · 0.0% of section data
Uncommon name
MD5 8099038b8f242109158668876e03af7a
.rsrc 2048 bytes · 0.0% of section data
MD5 0300a49ecf1df01b9e7f361e97f52961
.reloc 121856 bytes · 1.5% of section data
MD5 b4821443b59518a04f92617496ad71f4
.text 331264 bytes · 4.1% of section data
MD5 4e6423e193118d7cdd64db774e922ede
.data 1195008 bytes · 15.0% of section data
MD5 ddc34cb23921e2153b24bf954aad848f

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 75bb7fd4799a6801b4e2c0ca160f09b3.
  • 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.