GridinSoft Threat Intelligence

mfc71.dll file report

Clean record File reputation report
MD5 02f885954f9ea8249b38c72584127c51
Latest seen 2021-03-08 16:12:53 (5 years ago)
First seen 2017-12-25 14:05:57 (8 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-12-25 14:05:57 (8 years ago); latest analysis 2021-03-08 16:12:53 (5 years ago).

Publisher context

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

Digital signature

Signed by HUAWEI Technologies Co., Ltd.. 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.

mfc71.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio .NET. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-03-08 16:12:53 (5 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 .NET
Company Name: Microsoft Corporation
MD5: 02f885954f9ea8249b38c72584127c51
Size: 1 MB
First Published: 2017-12-25 14:05:57 (8 years ago)
Latest Published: 2021-03-08 16:12:53 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-08 16:12:53 (5 years ago)
Signed By: HUAWEI Technologies Co., Ltd.
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.

%appdata%

ThreatInfo has observed mfc71.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 7 85.7%
Windows 10 14.3%

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

mfc71.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 0x0000f41a
Image base 0x7c140000

PE Sections:

Sections 4
Raw data 1056768

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

.text 901120 bytes · 85.3% of section data
MD5 6b258aa9bb668b774e87ce31eef90fdf
.data 40960 bytes · 3.9% of section data
MD5 914fac808e3e28cb80c53c0c044438e6
.rsrc 49152 bytes · 4.7% of section data
MD5 77e05fb22835f20283d14a4a41c8df21
.reloc 65536 bytes · 6.2% of section data
MD5 8c10ee952ea1e4defcd686c5a1012b7f

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 02f885954f9ea8249b38c72584127c51.
  • 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.