GridinSoft Threat Intelligence

vcruntime140_IObitDel.dll file report

Clean record File reputation report
MD5 a2523ea6950e248cbdf18c9ea1a844f6
Latest seen 2026-05-03 23:00:54 (3 weeks ago)
First seen 2017-05-24 14:03:03 (9 years ago)
Size 81 KB
Publisher Microsoft Corporation
Product Microsoft® Visual Studio® 2015
Signed by Microsoft Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-24 14:03:03 (9 years ago); latest analysis 2026-05-03 23:00:54 (3 weeks ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft® Visual Studio® 2015.

Digital signature

Signed by Microsoft Corporation. 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

vcruntime140_IObitDel.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2015. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2026-05-03 23:00:54 (3 weeks 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

Product Name: Microsoft® Visual Studio® 2015
Company Name: Microsoft Corporation
MD5: a2523ea6950e248cbdf18c9ea1a844f6
Size: 81 KB
First Published: 2017-05-24 14:03:03 (9 years ago)
Latest Published: 2026-05-03 23:00:54 (3 weeks ago)
Status: Clean (on last analysis)
Analysis Date: 2026-05-03 23:00:54 (3 weeks ago)

Overview

Signed By: Microsoft Corporation
Status: Valid

The signature on vcruntime140_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%\zaxar
%appdata%\agdata\bin
%programfiles%\zaxar\_update
%profile%\peeder sp3\application data
%programfiles%\anonymizergadget
%localappdata%\host app service\engine
%localappdata%\host app service\swbd
%programfiles%\firefox
%programfiles%\iqiyi video\geeplayer\3.0.40.3591
%programfiles%\iqiyi video\lstyle\6.1.51.4886

ThreatInfo has observed vcruntime140_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:

12 observed names
vcruntime140.dll a2523ea6950e248cbdf18c9ea1a844f6 a5d666c.rbf 10cd7dc7.rbf 456a.rbf 2e60d61f.rbf 245305b5.rbf 569da041.rbf 1b16793b.rbf vcruntime140 (1).dll vcruntime140.dll.quarantined vcruntime140_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 vcruntime140_IObitDel.dll across 85 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 10.2%
Low High activity

The strongest geographic signal for this file is United States with 10.2% 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 91.9%
Windows 7 6.5%
Windows 8.1 1.2%
Windows XP 0.3%
Windows 8 0.2%

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

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

PE Sections:

Sections 6
Raw data 66560

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

.text 59392 bytes · 89.2% of section data
MD5 fb97aafe8a6cd1b9e4fd3d20ef404852
.data 512 bytes · 0.8% of section data
MD5 89c9a0e23b407822d7e2b53f03ebdda7
.idata 1536 bytes · 2.3% of section data
MD5 f5369625aebf79954cc8112f9f87322e
_RDATA 512 bytes · 0.8% of section data
Uncommon name
MD5 9475a59226943a3ad422e18169989f66
.rsrc 1536 bytes · 2.3% of section data
MD5 916d5dda347a517af780ab31d45eb4d7
.reloc 3072 bytes · 4.6% of section data
MD5 305846d31a4f0d03a78507b6189e60d2

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 a2523ea6950e248cbdf18c9ea1a844f6.
  • 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.