GridinSoft Threat Intelligence

mfc140fra.dll file report

Clean record File reputation report
MD5 31179d465f2b52220239c794851afb13
Latest seen 2023-07-28 23:37:27 (2 years ago)
First seen 2019-11-29 13:05:43 (6 years ago)
Size 74 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2019-11-29 13:05:43 (6 years ago); latest analysis 2023-07-28 23:37:27 (2 years 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.

mfc140fra.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 2023-07-28 23:37:27 (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.

Product Name: Microsoft® Visual Studio® 2017
Company Name: Microsoft Corporation
MD5: 31179d465f2b52220239c794851afb13
Size: 74 KB
First Published: 2019-11-29 13:05:43 (6 years ago)
Latest Published: 2023-07-28 23:37:27 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-07-28 23:37:27 (2 years 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.

%programfiles%

ThreatInfo has observed mfc140fra.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.

25.0%
25.0%
25.0%
25.0%

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

Windows 10 100.0%

The most common operating system signal for mfc140fra.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.

mfc140fra.dll 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.

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point
Image base

PE Sections:

Sections 2
Raw data 58880

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

.text 512 bytes · 0.9% of section data
MD5 2963c776cfb0d4b1e58e655ffa8f8f6e
.rsrc 58368 bytes · 99.1% of section data
MD5 5496a6ffc1f8e5bfa714c13c8dc61c97

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 31179d465f2b52220239c794851afb13.
  • 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.