GridinSoft Threat Intelligence

scan_IObitDel.dll file report

Clean record File reputation report
MD5 0d964826c1c31b2ff899677e2172852d
Latest seen 2021-03-01 04:25:14 (5 years ago)
First seen 2017-08-27 00:03:16 (8 years ago)
Size 509 KB
Signed by Bitdefender SRL

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-08-27 00:03:16 (8 years ago); latest analysis 2021-03-01 04:25:14 (5 years ago).

Digital signature

Signed by Bitdefender SRL. 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.

File context

scan_IObitDel.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-03-01 04:25:14 (5 years 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.

File Details

MD5: 0d964826c1c31b2ff899677e2172852d
Size: 509 KB
First Published: 2017-08-27 00:03:16 (8 years ago)
Latest Published: 2021-03-01 04:25:14 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-01 04:25:14 (5 years ago)

Overview

Signed By: Bitdefender SRL
Status: Valid

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

Common Places:

%programfiles%\tencent\qqpcmgr\12.3.26474.901\bitdefender
%programfiles%\tencent\qqpcmgr\12.8.19072.214\bitdefender
%programfiles%\tencent\qqpcmgr\12.3.26498.901\bitdefender
%programfiles%\tencent\qqpcmgr\12.3.26492.901\bitdefender
%programfiles%\tencent\qqpcmgr\12.3.26514.901\bitdefender
%programfiles%\tencent\qqpcmgr\12.3.26514.901
%programfiles%\tencent\qqpcmgr\12.3.26525.901
%programfiles%\tencent\qqpcmgr\12.3.26529.901
%programfiles%\tencent\qqpcmgr\12.3.26531.901
%commonappdata%\tencent\qqpcmgr

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

File Names:

2 observed names
scan.dll scan_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.

Geographic signal

Observed country distribution

ThreatInfo has seen scan_IObitDel.dll across 25 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country China
Share 11.5%
Low High activity

The strongest geographic signal for this file is China with 11.5% 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 69.8%
Windows 7 24.5%
Windows 8.1 1.9%
Windows Server 2012 R2 1.9%
Windows 8 1.9%

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

scan_IObitDel.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x00032dd6
Image base 0x10000000

PE Sections:

Sections 6
Raw data 495104

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

.text 305152 bytes · 61.6% of section data
MD5 26516dfc19988c1042e0516c76c0748d
.orpc 512 bytes · 0.1% of section data
Uncommon name
MD5 ebdfd5e733060238e92d751867fc0334
.rdata 117760 bytes · 23.8% of section data
MD5 96140df436f410df85e0c70bacc48046
.data 17920 bytes · 3.6% of section data
MD5 89ec73af42c58bd59087a8277a8483bb
.rsrc 27136 bytes · 5.5% of section data
MD5 18eeaffb68d603e1481cbceda0928127
.reloc 26624 bytes · 5.4% of section data
MD5 ddf9250f84ef0145c889c0a22b9dd3cd

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 0d964826c1c31b2ff899677e2172852d.
  • 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.