GridinSoft Threat Intelligence

vcamp140.dll file report

Clean record File reputation report
MD5 f89482c2c8a495993e2117d5d1bdf442
Latest seen 2022-01-14 21:36:20 (4 years ago)
First seen 2018-04-02 10:07:54 (8 years ago)
Size 390 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-04-02 10:07:54 (8 years ago); latest analysis 2022-01-14 21:36:20 (4 years ago).

Publisher context

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

Digital signature

Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.

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.

vcamp140.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 2022-01-14 21:36:20 (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® 2015
Company Name: Microsoft Corporation
MD5: f89482c2c8a495993e2117d5d1bdf442
Size: 390 KB
First Published: 2018-04-02 10:07:54 (8 years ago)
Latest Published: 2022-01-14 21:36:20 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-01-14 21:36:20 (4 years ago)
Signed By: Microsoft Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%commonappdata%\tencent\deskgo
%programfiles%
%commonappdata%
%programfiles%\tencent\qqpcmgr\13.0.19760.204\plugins
%programfiles%\tencent\qqpcmgr\13.0.19760.204
%programfiles%\tencent\qqpcmgr
%programfiles%\tencent\qqpcmgr\13.0.19763.206\plugins
%programfiles%\tencent\qqpcmgr\13.0.19763.206
%temp%\tencent\qqpcmgr\~cfaa3\library\win_msvc2015\x86
%programfiles%\tencent\qqpcmgr\13.0.19771.209\plugins

ThreatInfo has observed vcamp140.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 78.7%
Windows 7 16.5%
Windows Server 2012 R2 3.5%
Windows Server 2008 R2 1.2%

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

vcamp140.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 0x000373d0
Image base 0x10000000

PE Sections:

Sections 6
Raw data 382976

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

.text 336384 bytes · 87.8% of section data
MD5 6627e85bcf01bd2e8dbe4f1ba162bb77
.data 10752 bytes · 2.8% of section data
MD5 54627649181131945f896af03121093c
.idata 6656 bytes · 1.7% of section data
MD5 679610369a7e028c95e32c7c8141a18e
.tls 512 bytes · 0.1% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 9728 bytes · 2.5% of section data
MD5 a6592237b457ada1a4cf798be8f15e8d
.reloc 18944 bytes · 4.9% of section data
MD5 caa3b2526d1c983581ccd7bc902c1f90

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