File scan report
Verdict Safe
Is d3dcompiler_ 47. dll safe? Yes, no threats found.
Microsoft-signed system DLL with zero detections and five prior safe verdicts under the same signer.
Strong evidence · A verified publisher signature, and no engine flags it.
Retain the file; it is a legitimate, widely distributed Microsoft system component.
Good practice2 tips
We found nothing harmful in this file.
Use it only as part of a program you got from the developer's own website.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 4
- Code signing Microsoft Corporation
- Test run Completed
- First seen 8y ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Zero of the 70 antivirus engines that checked it 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 70 antivirus engines that checked it returned clean results, including 16 major antivirus 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 benign signed installer rule. Sandbox activity 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 files it created. 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 security software 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
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 16sandbox rule tags
- 2spawned processes
- 3network contacts
- 40filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
16MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1018
- T1027· Obfuscated code
- T1027.005· Obfuscated code
- T1055· Process injection
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1095· Custom network
- T1129· Loads modules
- T1218.011
- T1222
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1562.001· Disables security
- T1622
Observed activity
Processes started
2Programs the file ran, with their command lines.
rundll32.exe"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1rundll32.exeC:\windows\system32\rundll32.exe
Network contacts
33 hosts, listed as 3 addresses. Links show the host and path only.
- IP address
20.189.173.20 - IP address
13.89.179.12 - IP address
104.208.16.94
Files
30Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_2568fe37a24d9acaf6dddc61cd444a927d59_e289aede_025fac8f\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_4a32771f54d3535aa8fbe457d667714c395a197e_e289aede_07bb189c - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_4a32771f54d3535aa8fbe457d667714c395a197e_e289aede_07bb189c\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_ec9fb64b36dba433354e027d86520145f114c5c_e289aede_1acee632 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_ec9fb64b36dba433354e027d86520145f114c5c_e289aede_1acee632\Report.wer
Show all 30 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_ec9fb64b36dba433354e027d86520145f114c5c_e289aede_1d42e690 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_d3d_ec9fb64b36dba433354e027d86520145f114c5c_e289aede_1d42e690\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER11C6.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER11C6.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1458.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1458.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1514.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1514.tmp.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BAA.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER11C6.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER11C6.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1458.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1458.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1514.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1514.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BAA.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BAA.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER202F.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER202F.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2253.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2253.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A46.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A76.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B13.tmp.csv
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
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\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6872
Show all 10 entries for mutexes
\Sessions\1\BaseNamedObjects\Global\f2161960-ff0a-410f-82f7-a0a1d6679da9\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess3216\Sessions\1\BaseNamedObjects\Global\cd0e9ec9-9601-411c-adb8-89ee5d447917\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6028
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- dc66490003f4d662c6db…6b21fbNot checkedno saved verdict
- 27f93db58b66e517f4bf…6bf25fNot checkedno saved verdict
- c61cb2197f1087f81cdc…f01bceNot checkedno saved verdict
- 2446771b918aa497dea6…d81053Not checkedno saved verdict
- 0b2e2a9b410ab720cd7c…ca94a8Not checkedno saved verdict
- e57269898a84b7537f04…16208aNot checkedno saved verdict
- be7a348f3854ae9ccb69…866164Not checkedno saved verdict
- 50c32c52a7f902802bd7…b69cb8Not checkedno saved verdict
- da6a5de4f8217430cf88…ec4c17Not checkedno saved verdict
- 686408917341a4a9dc08…364b28Not checkedno saved verdict
Chapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; signed by Microsoft Corporation.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 7, 2026, 10:49 AM UTC
- SHA-256
3d93ae44f8feeeede4f6773c06edbd97fa67ac0db008893cc62ccafa6cc8161b- SHA-1
02e53dcdc40c9f359f3f2adb272616d4548c957d- MD5
3609abbd2d61fc1d95b825f4836c612d
About this file
d3dcompiler_47.dll is a Win32 DLL file of 4.3 MB.
- Type and size
- Win32 DLL · 4.3 MB
- Signer
- Microsoft CorporationValid code signature.
- First seen
- Jul 7, 2018On VirusTotal.
- Submitted by
- 524 distinct sources
- Packer
- None detected
- Entropy
- 7.40 of 8
First scanned
Antivirus consensus
0 of 70 engines flagged this file
4 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines0flagged
View all 74 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
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.