GridinSoft Threat Intelligence
dxil.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2024-09-05 23:00:33 (2 years ago); latest analysis 2024-10-31 23:01:41 (2 years ago).
Company metadata: Microsoft(r) Corporation.
Signed by Microsoft Corporation. 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
dxil.dll is a Windows file recorded in the ThreatInfo database. The reported company name is Microsoft(r) Corporation. The current detection status is Clean, based on the latest analysis from 2024-10-31 23:01:41 (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.
File Details
| Company Name: | Microsoft(r) Corporation |
| MD5: | c90d16b3a4761064c2587de17c3fd837 |
| Size: | 1 MB |
| First Published: | 2024-09-05 23:00:33 (2 years ago) |
| Latest Published: | 2024-10-31 23:01:41 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-10-31 23:01:41 (2 years ago) |
Overview
| 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.
Common Places:
| %programfiles%\microsoft\edgecore |
| %programfiles%\microsoft\edgewebview\application |
| %programfiles%\microsoft\edge\application |
| %sysdrive%\$recycle.bin\s-1-5-21-4114190863-4098575981-4148236708-1001\$r6e103y |
| %sysdrive%\$recycle.bin\s-1-5-21-4114190863-4098575981-4148236708-1001\$r2zmcow |
| %windir%\winsxs |
| %system% |
| %commonappdata%\dell\saremediation\systemrepair\snapshots |
| %sysdrive%\windows.old\windows\winsxs |
| %sysdrive%\windows.old\windows\system32 |
ThreatInfo has observed dxil.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 dxil.dll across 45 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 36.2% 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 dxil.dll is Windows 10 with 98.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
dxil.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.
a9165e7920ec96a946e000912bdfb44a
df7b8b1b535ffe1d16520ebdfc942697
e88841cccf211706779374b11da55595
989f70f9756e0b217c16829ab6a2bec2
59838542d009ad86bd6ef135f81fe741
0ebfe37ca2cf422ba21a938ebe0a931a
ad256a9aee56be7b5e96f1f9172d333d
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.