GridinSoft Threat Intelligence
FMAPO64.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2020-08-07 14:44:29 (5 years ago); latest analysis 2021-01-10 23:58:33 (5 years ago).
Company metadata: Fortemedia Corporation. Product metadata: Windows (R) Win 7 DDK driver.
Signed by Microsoft Windows Hardware Compatibility Publisher. ThreatInfo marks this publisher as trusted for this record.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
FMAPO64.dll is a Windows file recorded in the ThreatInfo database. It is associated with Windows (R) Win 7 DDK driver. The reported company name is Fortemedia Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-10 23:58:33 (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.
File Details
| Product Name: | Windows (R) Win 7 DDK driver |
| Company Name: | Fortemedia Corporation |
| MD5: | c96c7b2facad6f5630d6c6a3ad1180cb |
| Size: | 6 MB |
| First Published: | 2020-08-07 14:44:29 (5 years ago) |
| Latest Published: | 2021-01-10 23:58:33 (5 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-01-10 23:58:33 (5 years ago) |
Overview
| Signed By: | Microsoft Windows Hardware Compatibility Publisher |
| 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.
Common Places:
| %commonappdata%\reviversoft\pc reviver\s-1-5-21-3345049087-2262454278-399833233-1001\driver updater\downloads\36 |
| %commonappdata%\reviversoft\pc reviver\s-1-5-21-3345049087-2262454278-399833233-1001\driver updater\downloads\e972203d-6394-472a-a612-cdf5ddcfd97d |
| %commonappdata%\reviversoft\driver reviver\downloads\35646135-7f58-4c7d-b76a-c4b7d40cda45 |
| %commonappdata%\reviversoft\driver reviver\downloads\2 |
ThreatInfo has observed FMAPO64.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.
Geographic signal
Observed country distribution
ThreatInfo has seen FMAPO64.dll across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Mexico with 50.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for FMAPO64.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.
Analysis
FMAPO64.dll is identified as pe for 64-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
9e21ec342b0a8586b2ae65082557b09a
eabec99e3e930a42a430573c7f8364b3
d41d8cd98f00b204e9800998ecf8427e
a0e00627bb65bea91b19fa76d945931c
9003c4cc5427f5971fab51409288c8e0
3b1d4986a502db3eb7c1f51fa33e798f
0c7921330b9eace56426bd05f2d6b8db
8e8232304d2e0a434fe324448de3f71d
0301494e557427160de25c77b5b795e0
a67a7caad3a0a8a39d691e04588e27a6
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.