GridinSoft Threat Intelligence
13 file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-05-28 20:09:13 (8 years ago); latest analysis 2024-09-21 23:02:54 (2 years ago).
Company metadata: Microsoft Corporation. Product metadata: Microsoft® Visual Studio® 2015.
Signed by Microsoft Corporation. The signature is reported as valid, but signed files can still be bundled or abused.
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
13 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 2024-09-21 23:02:54 (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® 2015 |
| Company Name: | Microsoft Corporation |
| MD5: | cfbdf284c12056347e6773cb3949fbba |
| Size: | 429 KB |
| First Published: | 2017-05-28 20:09:13 (8 years ago) |
| Latest Published: | 2024-09-21 23:02:54 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-09-21 23:02:54 (2 years ago) |
Overview
| Signed By: | Microsoft Corporation |
| Status: | Valid |
The signature on 13 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:
| %appdata%\agdata\bin |
| %programfiles%\anonymizergadget |
| %sysdrive%\config.msi |
| %sysdrive%\\program files (x86)\steam\bin\cef\cef.win7 |
| %commondir%\tencent |
| %appdata%\tencent\wxwork\upgrade |
| %programfiles%\tencent |
| %temp%\tencent\qqmusic |
| %sysdrive%\$windows.~bt\sources\panther\migrationshims\migshim1 |
| %appdata%\tencent\tim\autemp\18122697\7dofe805\oldfiles |
ThreatInfo has observed 13 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.
File Names:
6 observed namesThis hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.
Geography:
31 observed countriesThe strongest geographic signal for this file is China with 36.9% 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 13 is Windows 10 with 79.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.
Analysis
13 is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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.
6207e271e6f710e9afa4e4c15e880a75
e3fb71af6b635feb0f22a9888cb19c4a
f07d5f626f12787336c1b9aef80e93c5
ef682b18082a3e47728e89e5df5cd701
6c290c3f1598743935fe4c3df0dcd618
7e488c3a7623d7f77f700cf7ef9c9b44
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.