GridinSoft Threat Intelligence

vcomp110.dll file report

Clean record File reputation report
MD5 77b1b6b9d8ead7033f7958d6161107ef
Latest seen 2021-02-08 16:56:27 (5 years ago)
First seen 2017-11-27 16:01:43 (8 years ago)
Size 122 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-11-27 16:01:43 (8 years ago); latest analysis 2021-02-08 16:56:27 (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

vcomp110.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:56:27 (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: 77b1b6b9d8ead7033f7958d6161107ef
Size: 122 KB
First Published: 2017-11-27 16:01:43 (8 years ago)
Latest Published: 2021-02-08 16:56:27 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-08 16:56:27 (5 years ago)

Overview

Signed By: Microsoft Corporation
Status: Valid

The signature on vcomp110.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%\dllescort\sysscan\windows\syswow64
%programfiles%\wintools
%system%
%commonappdata%\bromium\vsentry\4.1.6.3263\stage1\stage1image0005\swapdata-3c361943-c05b-474d-ab60-39abecec01e0
%programfiles%\dllescort2021\sysscan\windows
%commonappdata%\bromium\vsentry\4.2.4.52\stage1\stage1image0002\swapdata-c38ff989-d42f-492b-bcd8-f79bb204a254

ThreatInfo has observed vcomp110.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 vcomp110.dll across 5 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Taiwan
Share 28.6%
Low High activity

The strongest geographic signal for this file is Taiwan with 28.6% 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 100.0%

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

vcomp110.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 0x00009723
Image base 0x10000000

PE Sections:

Sections 5
Raw data 109056

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

.text 86016 bytes · 78.9% of section data
MD5 d0425246e493f6c8c56c95be8ff5d4f1
.data 4096 bytes · 3.8% of section data
MD5 b2724d460b1e83e7e3118e0d4969bf77
.idata 2560 bytes · 2.3% of section data
MD5 3cbcffa9504c290a8615dd1a4c166489
.rsrc 4608 bytes · 4.2% of section data
MD5 d42493a97a98842412c858a5ed8e52e2
.reloc 11776 bytes · 10.8% of section data
MD5 142106c24d987e6e0859badbae7c1b75

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 77b1b6b9d8ead7033f7958d6161107ef.
  • 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.