GridinSoft Threat Intelligence
dxcompiler.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2024-09-22 23:01:05 (2 years ago); latest analysis 2024-10-17 23:01:01 (2 years ago).
Company metadata: Microsoft(r) Corporation. Product metadata: Microsoft(r) DirectX for Windows(r) - Google Dawn Custom Build.
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
dxcompiler.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft(r) DirectX for Windows(r) - Google Dawn Custom Build. The reported company name is Microsoft(r) Corporation. The current detection status is Clean, based on the latest analysis from 2024-10-17 23:01:01 (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
| Product Name: | Microsoft(r) DirectX for Windows(r) - Google Dawn Custom Build |
| Company Name: | Microsoft(r) Corporation |
| MD5: | 7d848406f55d069285ea3aa64a5c088c |
| Size: | 19 MB |
| First Published: | 2024-09-22 23:01:05 (2 years ago) |
| Latest Published: | 2024-10-17 23:01:01 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-10-17 23:01:01 (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\edge\application |
| %programfiles%\microsoft\edgecore |
| %programfiles%\microsoft\edgewebview\application |
| %localappdata%\microsoft\edgewebview\application |
| %localappdata%\microsoft\edgecore |
| %programfiles%\microsoft\edge beta\application |
| %programfiles%\windowsapps\duckduckgo.desktopbrowser_0.91.0.0_x64__ya2fgkz3nks94\windowsbrowser |
ThreatInfo has observed dxcompiler.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 dxcompiler.dll across 48 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 28.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 dxcompiler.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
dxcompiler.dll is identified as pe for 64-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
359a3ec7750498a0562666f3f5371097
224a63b027bbbb8fc55207e96b4d850b
e29ae6b79c989d90cde6ec4a040685e5
1a9656c841ff484c0fca447c96462177
a48416c004663459725e4e631dbcb3b5
8c950f651287cbc1296bcb4e8cd7e990
1f354d76203061bfdd5a53dae48d5435
482f055a934771b42f97e2eeca91554a
e0655d2e3dd74866bb8551043dac2fe2
8124304c54db6735b90e9adc5485158b
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.