GridinSoft Threat Intelligence

mfc120u.dll file report

Clean record File reputation report
MD5 293002e4332f01c74c2a843b5c638a90
Latest seen 2022-08-25 23:29:03 (3 years ago)
First seen 2018-08-27 10:09:24 (7 years ago)
Size 4 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-08-27 10:09:24 (7 years ago); latest analysis 2022-08-25 23:29:03 (3 years ago).

Publisher context

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

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.

mfc120u.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2013. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2022-08-25 23:29:03 (3 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® 2013
Company Name: Microsoft Corporation
MD5: 293002e4332f01c74c2a843b5c638a90
Size: 4 MB
First Published: 2018-08-27 10:09:24 (7 years ago)
Latest Published: 2022-08-25 23:29:03 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-08-25 23:29:03 (3 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.

%system%
%commondir%\reallusion

ThreatInfo has observed mfc120u.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 83.3%
Windows 10 16.7%

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

mfc120u.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 0x002570ee
Image base 0x10000000

PE Sections:

Sections 5
Raw data 4433408

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

.text 2753024 bytes · 62.1% of section data
MD5 eb7b790c9534f3b482127fc296344a3d
.data 42496 bytes · 1.0% of section data
MD5 ebd5f3263af2421659995cee9795d3c8
.idata 20480 bytes · 0.5% of section data
MD5 19ebbc5235f04a921e53f32a14130b08
.rsrc 1415168 bytes · 31.9% of section data
MD5 d56dfd5eea3abf6003856c397a44f27c
.reloc 202240 bytes · 4.6% of section data
MD5 51ee21976a33cab47cb214072a99dbda

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 293002e4332f01c74c2a843b5c638a90.
  • 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.