File scan report
Verdict Safe
Is SDL2.
No antivirus engine flagged this widely observed DLL, and the isolated sandbox mapping lacks a target, corroboration, or malicious runtime verdict.
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
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 67 flagged
- Flagged 0
- No detection 67
- No result 7
- Code signing Unsigned
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 67 antivirus engines that checked it flagged the DLL, and it has been submitted 650 times by 423 sources since 2020. One sandbox mapped possible process injection, but named no target, recorded no injected process, and returned a clean result; the complete host check also found no cached malicious or suspicious hosts.
The strongest evidence is the absence of detections across 74 engines, including no major flags. The file is also well established, with 650 submissions from 423 sources dating back to 2020. A completed sandbox run produced a mapping, but no injected process or target was recorded, and the sandbox verdict was clean. All 12 distinct observed hosts were covered by the reputation check, with no malicious or suspicious cache matches; three reverse-DNS lookups were identified as sandbox background traffic. The four YARA matches are generic capability or compiler-oriented rules rather than malware-specific signatures. Although the DLL is unsigned, that limitation does not outweigh the broad, longstanding, and mutually consistent evidence.
What We Detected
None of the 67 antivirus engines that checked it flagged the DLL, including the participating major antivirus engines. The same hash has appeared in 650 submissions from 423 sources since December 2020, which is consistent with established commodity software rather than a rare, newly introduced payload.
Threat Behavior
One completed sandbox run mapped possible process injection under MITRE T1055, but it did not identify an injected process, target, or exact injection method, and the run returned a clean verdict. The observed host list was fully covered by the reputation check: none of the 12 distinct domains and IP addresses matched cached malicious or suspicious hosts. Three reverse-DNS lookups were attributed to sandbox background traffic rather than the sample. Four community YARA rules matched, but all were generic and none was malware-specific; the PE also showed no packing or high-entropy code.
What To Do Now
The file can remain in place when it came with software obtained from a trusted source. Because it is unsigned, verify its origin or compare its SHA-256 with the supplying application's official package if provenance is uncertain, and keep security software enabled.
Where this verdict could be wrong3 caveats
- The DLL is unsigned, so publisher identity cannot be authenticated through a code-signing certificate.
- One sandbox mapped activity to process injection, although it identified no injected process or target and returned a clean verdict.
- Ten generated files lack saved child verdicts, leaving their individual reputations unconfirmed.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 67 antivirus engines that checked it flagged the file.
- The hash has 650 submissions from 423 sources and has been known since December 2020.
- The completed sandbox run returned a clean result and recorded no injected target process.
- All 12 observed hosts were checked, with no cached malicious or suspicious matches.
- No packer, high-entropy code, or malware-specific YARA rule was found.
- The DLL has no digital signature, so its publisher cannot be authenticated.
- A sandbox mapped possible process injection, but did not identify the method or target.
- Ten generated files have no saved individual verdicts.
6 sources checked · all complete. 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- 23sandbox rule tags
- 1spawned processes
- 9network contacts
- 40filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
23MITRE 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
- T1055· Process injection
- T1056· Keylogging
- T1056.001· Keylogging
- T1057· Lists programs
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1095· Custom network
- T1113
- T1115
- T1123
- T1129· Loads modules
- T1218.011
- T1497· Sandbox evasion
- T1497.002· Sandbox evasion
- T1518· Checks your AV
- T1518.001· Checks your AV
- T1564.003· Hides artifacts
- T1614
- T1614.001
Observed activity
Processes started
1Programs the file ran, with their command lines.
rundll32.exe"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\init.dll",#1
Network contacts
99 hosts, listed as 3 domains, 6 addresses. Links show the host and path only.
- Domain
cdn.onenote.net - Domain
login.live.com - Domain
prda.aadg.msidentity.com - IP address
23.39.19.41 - IP address
52.255.188.83 - IP address
40.88.32.150
Show all 9 entries for network contacts
- IP address
104.43.139.144 - IP address
104.42.151.234 - IP address
52.147.198.201
Files
30Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_SDL_58b291ffc25365ab9c7cc84d36d3b3dbfe4825d1_645d1997_1487c030 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_SDL_58b291ffc25365ab9c7cc84d36d3b3dbfe4825d1_645d1997_1487c030\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_SDL_90112e88b2dc48b3461872b6b69977ecf36f6260_645d1997_1fd39008 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_SDL_90112e88b2dc48b3461872b6b69977ecf36f6260_645d1997_1fd39008\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_SDL_e8c81af1c555da936e3f7a176cd7987d38992e9_645d1997_1fabdb59 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_SDL_e8c81af1c555da936e3f7a176cd7987d38992e9_645d1997_1fabdb59\Report.wer
Show all 30 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_SDL_fb3d40c1aac5252fb1a0eed5df7d7c6a3faf9016_645d1997_1dabd03d - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rundll32.exe_SDL_fb3d40c1aac5252fb1a0eed5df7d7c6a3faf9016_645d1997_1dabd03d\Report.wer - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7730.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7730.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER79A2.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER79A2.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A5F.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A5F.tmp.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA92.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C3F.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4C6E.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7730.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7730.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER79A2.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER79A2.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A5F.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A5F.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER8EE7.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F07.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER9EE7.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F07.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERA8EB.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERA91B.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA92.tmp
Registry and auto-start
15Settings the file changed, including ways to start again after a restart.
- Set
\REGISTRY\A\{e88c1bfe-15dc-c88c-3646-843cbba29a8b}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Set
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting\Debug - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\Debug\ExceptionRecord - Set
HKEY_CURRENT_USER\Software\Microsoft\IdentityCRL\Immersive\production\Property\0018400477976A9C - Set
HKEY_CURRENT_USER\Software\Microsoft\IdentityCRL\Immersive\production\Token\{67082621-8D18-4333-9C64-10DE93676363}\DeviceTicket - Set
HKEY_CURRENT_USER\Software\Microsoft\IdentityCRL\Immersive\production\Token\{67082621-8D18-4333-9C64-10DE93676363}\DeviceId
Show all 15 entries for registry and auto-start
- Set
\REGISTRY\A\{56fa13eb-2c4d-3877-412f-82c7b789476c}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Set
\REGISTRY\A\{3255949a-ad14-8507-c5c1-36b1a5d5bfbf}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Set
HKEY_CURRENT_USER\Software\Microsoft\IdentityCRL\Immersive\production\Property\00184005CC704D82 - Set
\REGISTRY\A\{06bae49f-e759-e867-2ba3-bd176863e9a3}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Set
\REGISTRY\A\{be2738b3-e168-1c3d-2421-78c4e8ad7300}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Set
\REGISTRY\A\{b83334ae-f09a-80f1-e865-f3e2ee4c8bd3}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Set
\REGISTRY\A\{f9a79e90-9487-701c-3351-19aaca79550e}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Set
HKEY_CURRENT_USER\Software\Microsoft\IdentityCRL\Immersive\production\Property\001800085D5248F2 - Set
\REGISTRY\A\{c58f5530-8238-9ba6-9a34-cd3a2e4b0f1c}\Root\InventoryApplicationFile\PermissionsCheckTestKey
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6876\Sessions\1\BaseNamedObjects\Global\d71c7187-644a-4d3a-9462-4d0f25d9997d\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess3900\Sessions\1\BaseNamedObjects\Global\481d3cc2-8950-4d36-8cd5-11dbbaf91513\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess5568\Sessions\1\BaseNamedObjects\Global\aeea0b62-ae90-4174-979f-1084eb91b225
Show all 10 entries for mutexes
\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess4220\Sessions\1\BaseNamedObjects\Global\a110e7a3-5dd8-4ecd-8841-54984c4b5533\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6456\Sessions\1\BaseNamedObjects\Global\cac8b902-fc9f-4207-958e-958d6329d36e
Sandbox background — not the file
3The analysis machine's own processes and connections, recorded in every run.
- VM host
201.198.147.52.in-addr.arpa - VM host
137.90.64.13.in-addr.arpa - VM host
217.106.137.52.in-addr.arpa
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.
- 139b3739ea4d0828a2e6…f11c8cNot checkedno saved verdict
- 2ddcc1130b05dc861da0…4b0615Not checkedno saved verdict
- a80b9ceb6bf92d375f82…6c5a18Not checkedno saved verdict
- 1bbf36b7fe32649e2604…db3c64Not checkedno saved verdict
- 5c028de31095e211ec5c…f89965Not checkedno saved verdict
- c6084240939652ad2dfd…60bb95Not checkedno saved verdict
- 0743007da2e36aa74fd9…00c02bNot checkedno saved verdict
- 16b42be1ea6ce353969e…25d4cbNot checkedno saved verdict
- 175f95d45e9ee0e7ca51…779ea1Not checkedno saved verdict
- ff885ab5122941ce7bd2…81ce10Not checkedno saved verdict
Chapter 04
Technical details
None of the 67 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 9, 2026, 10:24 PM UTC
- SHA-256
f65b50d693484d5d5a2bb8df1cf520628dd744e99e9a937bb936839b990943a0- SHA-1
9255b9df335ce9189e76f47b2ca99851aaddbab9- MD5
f9a859a7690fc35c5a925739ebe65fa2
About this file
SDL2.dll is a Win32 DLL file of 1.6 MB.
- Type and size
- Win32 DLL · 1.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Dec 22, 2020On VirusTotal.
- Submitted by
- 423 distinct sources
- Packer
- None detected
- Entropy
- 6.23 of 8
First scanned
Antivirus consensus
0 of 67 engines flagged this file
7 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-234 engines0flagged
- Low-trust16 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
- ClamAVNo result
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureNo result
- 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.
- DebuggerCheck__APIgeneric
- golang_bin_JCorn_CSC846generic
- pe_detect_tls_callbacksgeneric
- 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 6 questions people ask most about this file.
Is SDL2.dll safe?
What is SDL2.dll?
How many antivirus engines detected SDL2.dll?
What is the SHA-256 hash of SDL2.dll?
Is it safe to use SDL2.dll?
How up to date is this analysis of SDL2.dll?
Community
Member reviews and reports for this exact file hash.