GridinSoft Threat Intelligence

msvcp60.dll file report

Under review File reputation report
MD5 59a6413fb2cc89fd8651b1d2962fb8b9
Latest seen 2024-08-14 23:01:47 (2 years ago)
First seen 2017-06-09 16:09:26 (8 years ago)
Size 404 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-06-09 16:09:26 (8 years ago); latest analysis 2024-08-14 23:01:47 (2 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft (R) Visual C++.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

msvcp60.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft (R) Visual C++. The reported company name is Microsoft Corporation. The current detection status is Undefined, based on the latest analysis from 2024-08-14 23:01:47 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Microsoft (R) Visual C++
Company Name: Microsoft Corporation
MD5: 59a6413fb2cc89fd8651b1d2962fb8b9
Size: 404 KB
First Published: 2017-06-09 16:09:26 (8 years ago)
Latest Published: 2024-08-14 23:01:47 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-14 23:01:47 (2 years ago)
%appdata%
%programfiles%\claro
%programfiles%\claro\updatedog
%appdata%\claro
%programfiles%
%appdata%\contentmgr_temp\arcsoft
%appdata%\contentmgr_temp\common files\arcsoft
%appdata%\contentmgr_temp\common files\arcsoft\connection service
%profile%\windows

ThreatInfo has observed msvcp60.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 7 69.9%
Windows 10 19.6%
Windows 8.1 9.1%
Windows Server 2012 R2 1.4%

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

msvcp60.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 0x00001312
Image base 0x75ff0000

PE Sections:

Sections 5
Raw data 409600

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

.text 176128 bytes · 43.0% of section data
MD5 3bff7acfc8fae03fff56588f419255f5
.rdata 208896 bytes · 51.0% of section data
MD5 05590c0961347cfac3d652394d318b8f
.data 8192 bytes · 2.0% of section data
MD5 5bda35601f947a64ef7fd93c0bf0d135
.rsrc 4096 bytes · 1.0% of section data
MD5 e4ca694729dc155e3ce334d7a6fe1177
.reloc 12288 bytes · 3.0% of section data
MD5 a20424b242b3eb924a86854b88bc5854

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 59a6413fb2cc89fd8651b1d2962fb8b9.
  • 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.