GridinSoft Threat Intelligence

dxcompiler.dll file report

Under review File reputation report
MD5 3c87091ecbf7c91536aacf16bfaf7ea2
Latest seen 2026-05-13 23:00:34 (2 weeks ago)
First seen 2026-05-13 23:00:34 (2 weeks ago)
Size 23 MB
Publisher Microsoft(r) Corporation
Product Microsoft(r) DirectX for Windows(r) - Google Dawn Custom Build
Signed by BrowseAI LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-05-13 23:00:34 (2 weeks ago); latest analysis 2026-05-13 23:00:34 (2 weeks ago).

Publisher context

Company metadata: Microsoft(r) Corporation. Product metadata: Microsoft(r) DirectX for Windows(r) - Google Dawn Custom Build.

Digital signature

Signed by BrowseAI LLC. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

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 Undefined, based on the latest analysis from 2026-05-13 23:00:34 (2 weeks ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

File Details

Product Name: Microsoft(r) DirectX for Windows(r) - Google Dawn Custom Build
Company Name: Microsoft(r) Corporation
MD5: 3c87091ecbf7c91536aacf16bfaf7ea2
Size: 23 MB
First Published: 2026-05-13 23:00:34 (2 weeks ago)
Latest Published: 2026-05-13 23:00:34 (2 weeks ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-05-13 23:00:34 (2 weeks ago)

Overview

Signed By: BrowseAI LLC
Status: Valid

The signature on dxcompiler.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

Common Places:

%programfiles%\ace\ace\application

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 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 100.0%
Low High activity

The strongest geographic signal for this file is United States with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 100.0%

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.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x0127ee60
Image base 0x0000000180000000

PE Sections:

Sections 9
Raw data 24300032

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

.text 19650560 bytes · 80.9% of section data
Large raw data
MD5 a43d65d9689df37cf74a1b31388c4f61
.rdata 3856384 bytes · 15.9% of section data
MD5 3073e2d3d8f1c50109d23f38942b16a8
.data 29696 bytes · 0.1% of section data
MD5 1c3cd66eed525d3b1804a1cd9326ef82
.pdata 688128 bytes · 2.8% of section data
MD5 4bbdc3b5add27d3c351aa933e06c1324
.fptable 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 be6398751c1c2c4f2216552104e6a3d9
.rsrc 1024 bytes · 0.0% of section data
MD5 a3c19ce329b372632422e83817be5cde
.reloc 72704 bytes · 0.3% of section data
MD5 be72ffd68e1f9ac4a8b6ceb5ee5a71ac

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 3c87091ecbf7c91536aacf16bfaf7ea2.
  • 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.