GridinSoft Threat Intelligence

vcomp100.dll file report

Clean record File reputation report
MD5 28d2b08d3d33670b0d010ed2ba2ab513
Latest seen 2022-10-08 23:04:52 (3 years ago)
First seen 2017-05-29 02:10:47 (8 years ago)
Size 49 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-29 02:10:47 (8 years ago); latest analysis 2022-10-08 23:04:52 (3 years ago).

Publisher context

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

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.

vcomp100.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2010. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2022-10-08 23:04:52 (3 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® 2010
Company Name: Microsoft Corporation
MD5: 28d2b08d3d33670b0d010ed2ba2ab513
Size: 49 KB
First Published: 2017-05-29 02:10:47 (8 years ago)
Latest Published: 2022-10-08 23:04:52 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-10-08 23:04:52 (3 years ago)
Signed By: Microsoft Corporation
Status: Valid

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

%programfiles%\001
%appdata%\tencent\qqlite\stemp\txqq2052~0
%programfiles%\tencent\qq\bin
%appdata%\tencent\qq\stemp\txqq2052~1
%appdata%\tencent\qq\stemp\txqq2052~0
%appdata%\tencent\qq\autemp\3073859600\6ur0e70d\newfiles\crt
%appdata%\tencent\qq\autemp\3073859600\6ur0e70d\oldfiles\crt
%sysdrive%\applications\ymc
%appdata%\tencent\qq\autemp\2853731112\778gtu03\newfiles\crt
%appdata%\tencent\qq\autemp\2853731112\778gtu03\oldfiles\crt

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

Windows 10 64.7%
Windows 7 15.8%
Windows XP 14.1%
Windows 8.1 3.3%
Windows Vista 0.5%
Windows 8 0.5%
Windows Server 2008 R2 0.5%
Windows Server 2012 R2 0.5%

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

vcomp100.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 0x000057f4
Image base 0x72880000

PE Sections:

Sections 4
Raw data 44032

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

.text 36864 bytes · 83.7% of section data
MD5 6402cc34111ee0f64080fe12c9d514c4
.data 512 bytes · 1.2% of section data
MD5 5e1733629796dd75dc1deb0f0bc7c4b7
.rsrc 4096 bytes · 9.3% of section data
MD5 0599eeb39b228d11fa13c0f2776fd79b
.reloc 2560 bytes · 5.8% of section data
MD5 60ec49de5e6a645af85e11296e7643e9

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 28d2b08d3d33670b0d010ed2ba2ab513.
  • 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.