Is d3dcompiler_47.dll safe?
Microsoft-signed system DLL with zero detections and five prior safe verdicts under the same signer.
Zero of 74 engines flagged the file. It is signed by Microsoft Corporation, a trusted publisher, and five similar files from the same signer were previously classified safe. Sandbox artefacts are consistent with legitimate system behaviour.
3d93ae44f8feeeede4…2ccafa6cc8161bRecommended next actions
Before using
Use it only as part of software obtained from the developer's official site or another source you independently trust.
If you already used it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Zero of 74 engines flagged the file. It is signed by Microsoft Corporation, a trusted publisher, and five similar files from the same signer were previously classified safe. Sandbox artefacts are consistent with legitimate system behaviour.
The file is a 4.3 MB Win32 DLL named d3dcompiler_47.dll, first seen in 2018 and submitted 618 times by 524 sources. All 74 engines returned clean results, including 16 tier-1 engines. The certificate is verified and matches Microsoft Corporation, which has a 14/15 safe historical rate. Five prior samples signed by the same publisher received safe verdicts under the ai:benign_signed_installer rule. Sandbox activity (T1055, T1562.001) and direct-IP contacts are typical for legitimate Microsoft components and produced no malicious verdict.
What We Detected
Zero malicious detections across 74 engines. The file carries a valid Microsoft Corporation code-signing certificate dated 2018. Five prior samples from the same signer were classified safe with identical reason codes.
Threat Behavior
Sandbox execution produced MITRE mappings T1055 and T1562.001 plus three direct-IP contacts, but no malicious sandbox verdict or dropped malicious children. These artefacts are consistent with normal Windows system-component behaviour.
What To Do Now
The file can be trusted as a legitimate Microsoft component. Keep endpoint protection enabled; no further action is required.
- Microsoft Corporation trusted publisher match
- Zero detections across 74 engines
- Five prior safe verdicts under identical signer
- Common-old prevalence with 524 unique sources
Retain the file; it is a legitimate, widely distributed Microsoft system component.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 16MITRE ATT&CK techniques
- 2spawned processes
- 3network contacts
- 40filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
d3dcompiler_47.dll
3d93ae44f8feeeede4f6773c06edbd97fa67ac0db008893cc62ccafa6cc8161b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\windows\system32\rundll32.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f
04Isolated runtime analysis - Written fileObserved
Report.wer
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f\Report.wer
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.189.173.20
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
13.89.179.12
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 20.189.173.20
- 13.89.179.12
- 104.208.16.94
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f\Report.wer
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_4a32771f54d3535aa8fbe457d667714c395a197e_e289aede_07bb189c
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_4a32771f54d3535aa8fbe457d667714c395a197e_e289aede_07bb189c\Report.wer
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_ec9fb64b36dba433354e027d86520145f114c5c_e289aede_1acee632
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER11C6.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER11C6.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1458.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1458.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1514.tmp
- DBWinMutex
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7632
- \Sessions\1\BaseNamedObjects\Global\dfdd5fa3-b114-47b0-852c-78ee904cd0d9
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7624
- \Sessions\1\BaseNamedObjects\Global\0e8cdb24-b391-47f1-971c-68fe4baeb751
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- dc66490003f4d662c6db…6b21fbNever scannednever seen before
- 27f93db58b66e517f4bf…6bf25fNever scannednever seen before
- c61cb2197f1087f81cdc…f01bceNever scannednever seen before
- 2446771b918aa497dea6…d81053Never scannednever seen before
- 0b2e2a9b410ab720cd7c…ca94a8Never scannednever seen before
- e57269898a84b7537f04…16208aNever scannednever seen before
- be7a348f3854ae9ccb69…866164Never scannednever seen before
- 50c32c52a7f902802bd7…b69cb8Never scannednever seen before
- da6a5de4f8217430cf88…ec4c17Never scannednever seen before
- 686408917341a4a9dc08…364b28Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 74engines flagged
- 524sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 524 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from Microsoft Corporation.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: d3dcompiler_47.dll — 3d93ae44f8feeeede4f6773c06edbd97fa67ac0db008893cc62ccafa6cc8161b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\windows\system32\rundll32.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f — C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Report.wer — C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f\Report.wer
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.189.173.20 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 13.89.179.12 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence20.189.173.20 · 13.89.179.12 · 104.208.16.94
0 of 74 engines flagged this file
View all 74 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- d3dcompiler_47.dll
- Format
- Win32 DLL
- Code signing
- Signature valid: Microsoft Corporation
- Size
- 4.1 MB
- Last analyzed
- Sep 7, 2026, 10:49 AM UTC
3d93ae44f8feeeede4f6773c06edbd97fa67ac0db008893cc62ccafa6cc8161bSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Use it only as part of software obtained from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is d3dcompiler_47.dll safe?
What is d3dcompiler_47.dll?
How many antivirus engines detected d3dcompiler_47.dll?
Is d3dcompiler_47.dll digitally signed?
What is the SHA-256 hash of d3dcompiler_47.dll?
Is it safe to use d3dcompiler_47.dll?
How up to date is this analysis of d3dcompiler_47.dll?
Community
Member reviews and reports for this exact file hash.