GridinSoft Threat Intelligence
vccorlib140.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-08-18 00:13:48 (8 years ago); latest analysis 2026-03-19 23:00:20 (2 months ago).
Company metadata: Microsoft Corporation. Product metadata: Microsoft® Visual Studio® 2015.
Signed by Microsoft Corporation. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
vccorlib140.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-03-19 23:00:20 (2 months 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: | 3d8e0ebbb613cbe80320a61259d18514 |
| Size: | 386 KB |
| First Published: | 2017-08-18 00:13:48 (8 years ago) |
| Latest Published: | 2026-03-19 23:00:20 (2 months ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2026-03-19 23:00:20 (2 months ago) |
Overview
| Signed By: | Microsoft Corporation |
| Status: | Valid |
The signature on vccorlib140.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%\reviversoft\pc reviver |
| %programfiles%\novo |
| %appdata%\pyinstaller\bincache00_py35_64bit |
| %profile%\p\application data |
| %programfiles% |
| %programfiles%\reviversoft |
| %appdata% |
| %sysdrive% |
| %programfiles%\zoner-1 englisch\photo studio 19 |
| %appdata%\nhm2\bin |
ThreatInfo has observed vccorlib140.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 vccorlib140.dll across 80 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 15.9% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for vccorlib140.dll is Windows 10 with 87.2% 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
vccorlib140.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
92f7a358b9b32403cf8dbbcab3d98a33
0b3ba05a4092307efcfdda38f5418e01
eda5db4fb2b2284203c2b114a784dc18
7d4b857aab9c413117b6ea970d2f5c33
bf619eac0cdf3f68d496ea9344137e8b
a07f1b80dd729609b2c518adfdeb169b
b64bb335026d87b512fd7bff126d880c
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.