GridinSoft Threat Intelligence
msvcp90.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-05-21 18:09:32 (9 years ago); latest analysis 2024-02-12 23:20:32 (2 years ago).
Company metadata: Microsoft Corporation. Product metadata: Microsoft® Visual Studio® 2008.
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
msvcp90.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2008. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2024-02-12 23:20:32 (2 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® 2008 |
| Company Name: | Microsoft Corporation |
| MD5: | f7cd95a47f9c2291db184c6c4ad7e120 |
| Size: | 831 KB |
| First Published: | 2017-05-21 18:09:32 (9 years ago) |
| Latest Published: | 2024-02-12 23:20:32 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-02-12 23:20:32 (2 years ago) |
Overview
| Signed By: | Microsoft Corporation |
| Status: | Valid |
The signature on msvcp90.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%\uniblue\driverscanner\x64 |
| %programfiles%\acad2010\setup |
| %sysdrive%\archivos de programa\uniblue\driverscanner\x64 |
| %programfiles%\uniblue\powersuite\x64 |
| %programfiles%\uniblue\driverscanner |
| %programfiles%\uniblue\powersuite |
| %programfiles%\gegeek_toolkit\gegeek toolkit\maintenance\glary utilities portable\portable |
| %programfiles%\glaryutilitiesportable\portable |
| %sysdrive%\programmi\glary utilities portable\glary utilities_portable\portable |
| %sysdrive%\archivos de programa\uniblue\driverscanner |
ThreatInfo has observed msvcp90.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 msvcp90.dll across 66 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Taiwan with 13.6% 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 msvcp90.dll is Windows 10 with 57.3% 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
msvcp90.dll is identified as pe for 64-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
c9a8be84b7e864dcc1ea1ae70bdc9c94
e71b99c143854af5b695862f5c42c0a8
5bf3a0e7dfef610ce4d0c5a4c58db1a3
f3d912b72cc12c5948d9f29276849bae
ecddd6c67e2643b5d2a2bc1c3cae66a1
401dfbc5ac24b2aa6854ecc5aa0ee31d
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.