File scan report
Verdict Safe
Is dsetup.
No antivirus engine detected this long-established, Microsoft-signed DirectX setup DLL, while its broad YARA matches lack supporting malicious runtime or file it created evidence.
Read the whole reasonShow less
Strong evidence · A verified publisher signature, and no engine flags it.
Allow it when its source and installation context match a legitimate DirectX or trusted software package. If its origin is unexpected, obtain a fresh copy from the official distributor while keeping security protection enabled.
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 5
- Code signing Microsoft Corporation
- Test run Completed
- First seen 15y ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 70 antivirus engines that checked it avoided a malware detection, including the reporting major antivirus engines, and the signature verifies as Microsoft Corporation. Although five community YARA rules and a mapping warrant notice, the file has extensive historical prevalence, no malicious sandbox verdict, and no malicious file it created.
The strongest evidence is the complete absence of detections across 75 antivirus engines, with 16 major antivirus engines reporting no detection. The DLL carries a verified Microsoft Corporation signature and has been widely submitted since 2011. Its completed sandbox run produced no malicious verdict, and none of the 10 inspected files it created was identified as malicious. Five community YARA rules matched, but several are generic, and the ransomware-named rule lacks corroboration from engines, runtime verdicts, or file it created analysis. The mapping and direct-IP activity remain cautionary signals, although host-reputation coverage did not encompass all observed contacts. Five prior Microsoft-signer matches also received benign-installer reason codes, reinforcing the publisher context.
What We Detected
No malware detection was reported by any of 75 antivirus engines. The DLL has a verified Microsoft Corporation signature, and the recognised-publisher check confirms the publisher against the curated list. It is also well established, with 3,213 sources and 5,299 submissions dating back to 2011.
Threat Behavior
One completed sandbox mapped activity to T1055 and recorded direct-IP connections, but it did not issue a malicious sandbox verdict. Ten files it created were inspected without a malicious child finding. Five community YARA rules matched; however, most are broad static patterns, and the VECT_Ransomware rule is unsupported by antivirus family labels or observed ransomware behavior. Only two contacted URLs were reputation-checked while additional IP contacts were recorded, so a complete host-reputation result is unavailable.
What To Do Now
Use the DLL only when it comes from the expected Microsoft DirectX redistributable or a trusted software package. Keep security software enabled and re-download the installer from its official distributor if the file appeared unexpectedly or outside a legitimate application directory.
Where this verdict could be wrong4 caveats
- A count of 5 matching community YARA rules includes VECT_Ransomware, although the other matches cover certificates, debug output, Go detection, and broad obfuscation patterns.
- The sandbox's offensive-technique list includes T1055, but the completed sandbox supplied no malicious verdict.
- One of our behaviour rules cites 13 IP addresses, while contactedHosts inspected only 2 observed URLs; therefore no complete host-reputation result is available.
- The signer-history record includes 1 malicious result among 18 Microsoft-signed historical samples, so signer history is strongly favorable but not perfect.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/70 antivirus engines reported a malicious result.
- Verified signature from Microsoft Corporation.
- Trusted publisher match for Microsoft.
- Common, long-established file with 5,299 submissions since 2011.
- No malicious sandbox verdict or malicious file it created.
- Five community YARA rules matched, including VECT_Ransomware.
- Evidence from the test run mapped possible process injection to MITRE T1055.
- The sample contacted 13 IP addresses directly.
- Host-reputation coverage was incomplete for all observed network contacts.
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
- 3spawned processes
- 14network 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
- T1036
- T1055· Process injection
- T1056· Keylogging
- T1057· Lists programs
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1095· Custom network
- T1112
- T1129· Loads modules
- T1218.011
- T1497· Sandbox evasion
- T1518.001· Checks your AV
Observed activity
Processes started
3Programs the file ran, with their command lines.
rundll32.exe"C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\DSETUP.dll",#1xpcproxy/usr/libexec/xpcproxyTextEdit/Applications/TextEdit.app/Contents/MacOS/TextEdit /Applications/TextEdit.app/Contents/MacOS/TextEdit
Network contacts
1414 hosts, listed as 12 addresses, 2 links. Links show the host and path only.
- IP address
17.188.145.170 - IP address
17.188.148.41 - IP address
17.188.155.177 - IP address
17.188.145.37 - IP address
17.188.145.174 - IP address
17.188.148.43
Show all 14 entries for network contacts
- IP address
17.188.149.164 - IP address
17.188.153.47 - IP address
23.55.62.51 - IP address
23.60.84.168 - IP address
104.43.139.144 - IP address
52.255.188.83 - URL
http://init-p01st.push.apple.com/bag - URL
http://ocsp.apple.com/ocsp03-asi2ca02/ME4wTKADAgEAMEUwQzBBMAkGBSsOAwIaBQAEFDpjNYC91gD+zsNfJ0wP9wrPSi8lBBQSdXxHkv2D474u/Fl/Z0OBNRBF7AIIXJDZkJ+MrDE=
Files
30Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_f3f0552e1f33edf84cee738894a9d8bf5d8e3b78_82810a17_059661ab - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_f3f0552e1f33edf84cee738894a9d8bf5d8e3b78_82810a17_059661ab\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_f3f0552e1f33edf84cee738894a9d8bf5d8e3b78_82810a17_09aa9609 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_f3f0552e1f33edf84cee738894a9d8bf5d8e3b78_82810a17_09aa9609\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_f3f0552e1f33edf84cee738894a9d8bf5d8e3b78_82810a17_182a56be - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_f3f0552e1f33edf84cee738894a9d8bf5d8e3b78_82810a17_182a56be\Report.wer
Show all 30 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER39A1.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER39A1.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FBC.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FBC.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4173.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4173.tmp.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER478B.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER478B.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DF5.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER66AF.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER69BD.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B35.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER66AF.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER69BD.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B35.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER39A1.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER39A1.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FBC.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FBC.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4173.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4173.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4190.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER447F.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER478B.tmp
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
DSETUP DLL MutexLocal\SM0:3632:168:WilStaging_02Local\SM0:2852:168:WilStaging_02Local\WERReportingForProcess3632Global\AmiProviderMutex_InventoryApplicationFileGlobal\147c6911-2eda-4fb8-8346-b6311d32ebb4
Show all 10 entries for mutexes
Local\SM0:2852:64:WilError_03\Sessions\1\BaseNamedObjects\DBWinMutex\Sessions\1\BaseNamedObjects\DSETUP DLL Mutex\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess5696
Sandbox background — not the file
2The analysis machine's own processes and connections, recorded in every run.
- VM process
WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3632 -s 752 - VM host
204.79.197.203
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.
- f0f73c9880625fc1b212…5656dfNot checkedno saved verdict
- 5d7e8147b05db16301df…8ecccaNot checkedno saved verdict
- 4007a620e8e881d5ab29…578dd9Not checkedno saved verdict
- 3f9f268e37ee66c67ddf…18b148Not checkedno saved verdict
- b3ac81aa6e4b6d65f6f9…5e909bNot checkedno saved verdict
- 5491e4c043f4751e731d…4945c9Not checkedno saved verdict
- ed131dd0c2536b0d44c9…d3b49fNot checkedno saved verdict
- b6353a509e3950d1848d…ec5688Not checkedno saved verdict
- 424e6257e3d9887ba764…93af52Not checkedno saved verdict
- 962efad5d75c349a7796…776b62Not 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 11, 2026, 1:22 PM UTC
- SHA-256
2a61679eeedabf7d0d0ac14e5447486575622d6b7cfa56f136c1576ff96da21f- SHA-1
7897418f0fae737a3ebe4f7954118d71c6c8b426- MD5
eb701def7d0809e8da765a752ab42be5
About this file
dsetup.dll is a Win32 DLL file of 95.6 kB.
- Type and size
- Win32 DLL · 95.6 kB
- Signer
- Microsoft CorporationValid code signature.
- First seen
- Apr 19, 2011On VirusTotal.
- Submitted by
- 3,213 distinct sources
- Packer
- None detected
- Entropy
- 7.39 of 8
First scanned
Antivirus consensus
0 of 70 engines flagged this file
5 of the 75 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 75 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
- IkarusNo result
- 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
Community YARA rules matched, but all of them are generic capability, anti-debug or compiler rules that ordinary software also matches. Worth noting, not on their own cause for alarm.
- Check_OutputDebugStringA_iatgeneric
- golang_bin_JCorn_CSC846generic
- PE_Digital_Certificategeneric
- VECT_Ransomwaregeneric
- Sus_Obf_Enc_Spoof_Hide_PEgeneric
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 dsetup.dll safe?
What is dsetup.dll?
How many antivirus engines detected dsetup.dll?
Is dsetup.dll digitally signed?
What is the SHA-256 hash of dsetup.dll?
Is it safe to use dsetup.dll?
How up to date is this analysis of dsetup.dll?
Community
Member reviews and reports for this exact file hash.