GridinSoft Threat Intelligence

mfcm140.dll file report

Clean record File reputation report
MD5 ebf946190367c9d94243707ccd16dc15
Latest seen 2025-11-15 23:01:10 (6 months ago)
First seen 2018-08-09 22:10:23 (7 years ago)
Size 90 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:23 (7 years ago); latest analysis 2025-11-15 23:01:10 (6 months ago).

Publisher context

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

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.

mfcm140.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2017. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2025-11-15 23:01:10 (6 months 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® 2017
Company Name: Microsoft Corporation
MD5: ebf946190367c9d94243707ccd16dc15
Size: 90 KB
First Published: 2018-08-09 22:10:23 (7 years ago)
Latest Published: 2025-11-15 23:01:10 (6 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-11-15 23:01:10 (6 months 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%
%commonappdata%\bromium\vsentry\4.1.9.2740\stage1\stage1image0005\swapdata-54ee731a-8898-4715-9dce-7378a635560b

ThreatInfo has observed mfcm140.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 80.0%
Windows 7 20.0%

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

mfcm140.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 0x00005040
Image base 0x10000000

.NET Info:

MVID: ac5fe785-be94-429b-aea3-996c974537ea

PE Sections:

Sections 5
Raw data 75264

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

.text 16896 bytes · 22.4% of section data
MD5 3bb8b287dca2656eb36e9ef10a4d6f69
.rdata 54784 bytes · 72.8% of section data
MD5 ce92402d628f9b29255e1342012dd61e
.data 1024 bytes · 1.4% of section data
MD5 f05c14d4c7c84c7807a5eb58f16f3ce0
.rsrc 1024 bytes · 1.4% of section data
MD5 27efabd3cb373df4ecc297cac1ef12ec
.reloc 1536 bytes · 2.0% of section data
MD5 bebd0ec288819212a06b1f70b92be242

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