GridinSoft Threat Intelligence

msvcr110.dll.quarantined file report

Clean record File reputation report
MD5 7c3b449f661d99a9b1033a14033d2987
Latest seen 2024-12-16 23:02:08 (a year ago)
First seen 2017-05-21 04:02:48 (9 years ago)
Size 829 KB
Publisher Microsoft Corporation
Product Microsoft® Visual Studio® 2012
Signed by Microsoft Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 04:02:48 (9 years ago); latest analysis 2024-12-16 23:02:08 (a year ago).

Publisher context

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

Digital signature

Signed by Microsoft Corporation. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

File context

msvcr110.dll.quarantined is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2012. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2024-12-16 23:02:08 (a year 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® 2012
Company Name: Microsoft Corporation
MD5: 7c3b449f661d99a9b1033a14033d2987
Size: 829 KB
First Published: 2017-05-21 04:02:48 (9 years ago)
Latest Published: 2024-12-16 23:02:08 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2024-12-16 23:02:08 (a year ago)

Overview

Signed By: Microsoft Corporation
Status: Valid

The signature on msvcr110.dll.quarantined 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%\runbooster
%appdata%\tencent\qqgametempest\minigames\kov3
%appdata%\taskmgr\win64
%windir%\syssecure\16.9.17.5
%appdata%
%localappdata%
%programfiles%\minergate
%appdata%\hgemxnrtqrutsfsuxpwnbtfjnsnillbo
%appdata%\dll-files.com\dll-files.com client\backup
%commonappdata%\ea56063c-ccf6-4a50-a577-5ca19bc9f4c8\dell\drivers\video_driver_ffyvx_wn32_16.400.2301_a02\bin64

ThreatInfo has observed msvcr110.dll.quarantined 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:

24 observed names
msvcr110.dll 27 25 8 11 15 6 13 10 23 2 3 9 12 2467f6b8.rbf 149c7cf.rbf 2cd78.rbf 501a733.rbf 1a890d.rbf 1255da9c.rbf 6b7dc1f7.rbf aa59647.rbf msvcr110_IObitDel.dll msvcr110.dll.quarantined

This 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.

Geographic signal

Observed country distribution

ThreatInfo has seen msvcr110.dll.quarantined across 74 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 38.0%
Low High activity

The strongest geographic signal for this file is Russian Federation with 38.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 60.3%
Windows 7 31.7%
Windows 8.1 7.3%
Windows 8 0.5%
Windows Server 2008 R2 0.1%
Windows XP 0.1%

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

msvcr110.dll.quarantined 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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x0002336c
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 832512

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

.text 594432 bytes · 71.4% of section data
MD5 f06909e0170e47d9c722196d4d395d3e
.rdata 184832 bytes · 22.2% of section data
MD5 73e91c1bb0345eded1066765d74381ff
.data 16384 bytes · 2.0% of section data
MD5 7bffde3814f876a40ba72755df6bb1e1
.pdata 26624 bytes · 3.2% of section data
MD5 376c47a15e665493b2c3a2af7419da39
.rsrc 1024 bytes · 0.1% of section data
MD5 0dd2a9a1339e6fd55b82b094b3cfb4ec
.reloc 9216 bytes · 1.1% of section data
MD5 0ce2b1bbfccf2a03ff3262fb75be9ae7

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