GridinSoft Threat Intelligence

mfcm110.dll file report

Clean record File reputation report
MD5 c3acb76bf6151814cb0fdff91bba4360
Latest seen 2025-01-22 23:00:53 (a year ago)
First seen 2018-08-09 22:10:31 (7 years ago)
Size 81 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-08-09 22:10:31 (7 years ago); latest analysis 2025-01-22 23:00:53 (a year ago).

Publisher context

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

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.

mfcm110.dll 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 2025-01-22 23:00:53 (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.

Product Name: Microsoft® Visual Studio® 2012
Company Name: Microsoft Corporation
MD5: c3acb76bf6151814cb0fdff91bba4360
Size: 81 KB
First Published: 2018-08-09 22:10:31 (7 years ago)
Latest Published: 2025-01-22 23:00:53 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-01-22 23:00:53 (a year 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.

%system%
%programfiles%\dllescort2021\sysscan\windows
%appdata%\kernel\kernel32

ThreatInfo has observed mfcm110.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 100.0%

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

mfcm110.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 0x000047d8
Image base 0x10000000

.NET Info:

MVID: f2ace1b2-95ad-4fd6-9426-fa89d77ef931

PE Sections:

Sections 5
Raw data 66048

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

.text 14848 bytes · 22.5% of section data
MD5 d906df00d51b2be52e0aaf40c3d3a319
.rdata 47104 bytes · 71.3% of section data
MD5 362bcaab72ea6b417f5f2c0c535d44ab
.data 1024 bytes · 1.6% of section data
MD5 4c2400e1adf54fbb69c07dbd8eb86237
.rsrc 1024 bytes · 1.6% of section data
MD5 de37b042dff034cf9633b9d3f4f840bc
.reloc 2048 bytes · 3.1% of section data
MD5 027942c25e50a8582403f80e39a3e5dc

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