Is dxgi.dll safe?
Single low-trust engine flags an unsigned DLL with no tier-1 support or sandbox malice.
Only Cynet (low_trust) reports malicious; 17 tier-1 engines are clean. The file is unsigned, shows one offensive MITRE technique but no malicious sandbox verdict, and has medium prevalence with no external-intel hits.
a2891dddbf64b63b9e…9bbc89212d7a55Recommended 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.
Only Cynet (low_trust) reports malicious; 17 tier-1 engines are clean. The file is unsigned, shows one offensive MITRE technique but no malicious sandbox verdict, and has medium prevalence with no external-intel hits.
The detection pattern matches the classic low-trust-only false-positive shape: 1/75 engines, tier1Malicious=0, onlyLowTrustFlagging=true. Absence of code signing, lack of tier-1 consensus, and zero corroboration from YARAify, CIRCL, or MalwareBazaar keep the risk low. Medium prevalence and a single sandbox run without malicious verdict further support a benign classification.
What We Detected
One low-trust engine (Cynet) flagged the sample; 17 tier-1 engines remained silent. The DLL is unsigned and contains no packers or high-entropy code sections.
Threat Behavior
Sandbox execution recorded T1562.001 (Impair Defenses) but produced no malicious verdict and no malicious child files. No domains, IPs, or URLs were contacted.
What To Do Now
Keep endpoint protection enabled. The file can be executed in a controlled environment if further validation is required, but current evidence does not indicate active malice.
- 17 tier-1 engines clean
- medium prevalence
- no external-intel hits
- no malicious children
- unsigned DLL
- single low-trust detection
- T1562.001 technique observed
The sample presents low risk; retain normal security controls and allow if internal policy permits unsigned system DLLs.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 13MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 38filesystem & 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
dxgi.dll
a2891dddbf64b63b9ec0bc5c2853b68b9e6c6a4b5285f8333d9bbc89212d7a55
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\dxgi.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 6488 -s 556
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
e059005f-fbb9-42e2-bfc3-6c00495d25e8
C:\ProgramData\Microsoft\Windows\WER\Temp\e059005f-fbb9-42e2-bfc3-6c00495d25e8
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\e059005f-fbb9-42e2-bfc3-6c00495d25e8
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\85f2581f-0d64-4296-aced-ddaf1414ec1f
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFB6.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA07.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE00.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERBFB6.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA07.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess6488
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\4d4de86c-723c-4d31-8042-a7389f52d86f
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess5816
- \Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex4324
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 89adc69ebebf9580d68b…34f354Never scannednever seen before
- 7eb601ecd9a02988231f…447389Never scannednever seen before
- 21ff592d1957acdbc0a7…497a4cNever scannednever seen before
- 4e1e01588ebd49d81a30…e103e2Never scannednever seen before
- 011ba3d7f331f253f445…6ae34cNever scannednever seen before
- c0c978ee26533e47bf3c…e4f5e5Never scannednever seen before
- a3f404210a382ed6bc15…0de9ffNever scannednever seen before
- 19885f52e5b71b9eba5e…d1f342Never scannednever seen before
- 18830565123671fe0312…e529f4Never scannednever seen before
- cc761442155ce38da92f…28dd8dNever 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.
- 0rule hits recorded
- 1 / 75engines flagged
- 696sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 75 antivirus engines flagged the file, including Cynet.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 862 times from 696 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: dxgi.dll — a2891dddbf64b63b9ec0bc5c2853b68b9e6c6a4b5285f8333d9bbc89212d7a55
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\dxgi.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\WerFault.exe -u -p 6488 -s 556
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: e059005f-fbb9-42e2-bfc3-6c00495d25e8 — C:\ProgramData\Microsoft\Windows\WER\Temp\e059005f-fbb9-42e2-bfc3-6c00495d25e8
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
1 of 75 engines flagged this file
View all 75 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- dxgi.dll
- Format
- Win32 DLL
- Code signing
- No verified publisher
- Size
- 172.5 KB
- Last analyzed
- Aug 10, 2026, 11:56 PM UTC
a2891dddbf64b63b9ec0bc5c2853b68b9e6c6a4b5285f8333d9bbc89212d7a55Safety & 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 dxgi.dll safe?
What is dxgi.dll?
How many antivirus engines detected dxgi.dll?
What is the SHA-256 hash of dxgi.dll?
Is it safe to use dxgi.dll?
How up to date is this analysis of dxgi.dll?
Community
Member reviews and reports for this exact file hash.