GridinSoft Threat Intelligence

vccorlib110 (1).dll file report

Clean record File reputation report
MD5 c5c2295981eedeff9924889a7f084cc2
Latest seen 2021-10-12 20:40:48 (4 years ago)
First seen 2017-05-25 18:07:01 (9 years ago)
Size 246 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-25 18:07:01 (9 years ago); latest analysis 2021-10-12 20:40:48 (4 years ago).

Publisher context

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

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.

vccorlib110 (1).dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2012. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-10-12 20:40:48 (4 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.

Product Name: Microsoft® Visual Studio® 2012
Company Name: Microsoft Corporation
MD5: c5c2295981eedeff9924889a7f084cc2
Size: 246 KB
First Published: 2017-05-25 18:07:01 (9 years ago)
Latest Published: 2021-10-12 20:40:48 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-10-12 20:40:48 (4 years ago)
Signed By: Microsoft Corporation
Status: Valid

The signature on vccorlib110 (1).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%
%programfiles%\dllescort\sysscan\windows\system32
%appdata%\taskmgr\win32
%appdata%\ruddh
%appdata%\windows\system32\recovery
%sysdrive%\sysdata
%appdata%\gpvbfpjzmlwbistebndrvfwnnirsqmmh
%appdata%\appdata
%appdata%\pjfnochayxeotjejdppdeoqnbasofvuh
%appdata%\tripp

ThreatInfo has observed vccorlib110 (1).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.

vccorlib110.dll vccorlib110 (1).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 7 45.7%
Windows 10 44.9%
Windows 8 4.6%
Windows 8.1 3.6%
Windows Server 2012 R2 0.5%
Windows Vista 0.5%
Windows XP 0.2%

The most common operating system signal for vccorlib110 (1).dll is Windows 7 with 45.7% 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.

vccorlib110 (1).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 0x00022dd7
Image base 0x10000000

PE Sections:

Sections 6
Raw data 235520

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

.text 174080 bytes · 73.9% of section data
MD5 43d3361c627faf49c8a2a0416cb76ceb
.data 28160 bytes · 12.0% of section data
MD5 cc4baa180edcad9e6e0758b53047a4ed
.idata 4096 bytes · 1.7% of section data
MD5 5975083c1b75339e0dfd57086cce17ea
minATL 512 bytes · 0.2% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1024 bytes · 0.4% of section data
MD5 affe3cf16bd2d6030a53642e353fec58
.reloc 27648 bytes · 11.7% of section data
MD5 a618610c5dd3948bc9fce1750ca6229b

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