GridinSoft Threat Intelligence

vccorlib110.dll file report

Clean record File reputation report
MD5 2aeb4f8e2bd49fa46e7fca142a1003a8
Latest seen 2021-02-08 16:59:19 (5 years ago)
First seen 2017-05-27 23:09:14 (9 years ago)
Size 345 KB
Publisher Microsoft Corporation
Product Microsoft® Visual Studio® 2012
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-27 23:09:14 (9 years ago); latest analysis 2021-02-08 16:59:19 (5 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.

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

vccorlib110.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-02-08 16:59:19 (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

Product Name: Microsoft® Visual Studio® 2012
Company Name: Microsoft Corporation
MD5: 2aeb4f8e2bd49fa46e7fca142a1003a8
Size: 345 KB
First Published: 2017-05-27 23:09:14 (9 years ago)
Latest Published: 2021-02-08 16:59:19 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-08 16:59:19 (5 years ago)

Overview

Signed By: Microsoft Corporation
Status: Valid

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

%appdata%\taskmgr\win64
%appdata%
%localappdata%
%programfiles%\minergate
%appdata%\hgemxnrtqrutsfsuxpwnbtfjnsnillbo
%sysdrive%\sysdata
%appdata%\ujlwdgbyninkgnzwijzdldzzwjbbnghu
%commonappdata%\windows
%commonappdata%\appdata\local\microsoft\windows\templates\synctemplate
%appdata%\appdata

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

Geographic signal

Observed country distribution

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

Top country Russian Federation
Share 50.8%
Low High activity

The strongest geographic signal for this file is Russian Federation with 50.8% 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 58.9%
Windows 7 32.9%
Windows 8.1 6.4%
Windows Server 2008 R2 0.9%
Windows 8 0.9%

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

vccorlib110.dll is identified as pe for 64-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 64-bit
Subsystem Windows CUI
Entry point 0x000247e4
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 337408

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

.text 157184 bytes · 46.6% of section data
MD5 0a4672d9f7962f8f2c21c4069a4e9534
.rdata 118784 bytes · 35.2% of section data
MD5 c416fb9a2d8634ee8941569153c3ded5
.data 43008 bytes · 12.7% of section data
MD5 3c55f184f1e43bc65f627cd3b94c21bc
.pdata 8704 bytes · 2.6% of section data
MD5 029c77315ed5bfdc7d28266287070e4f
minATL 512 bytes · 0.2% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1024 bytes · 0.3% of section data
MD5 f24b45d5717455c35bb4ef3e9f462adf
.reloc 8192 bytes · 2.4% of section data
MD5 f1865d37071991d23872a952358d1ae1

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 2aeb4f8e2bd49fa46e7fca142a1003a8.
  • 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.