Is 2020.09-bink2w64.dll safe?
No engine detected this long-established, correctly signed RAD Game Tools DLL, while one isolated T1055 mapping lacks corroborating sandbox or payload evidence.
All 74 antivirus engines returned without a malicious or suspicious detection, including 14 tier-1 engines that reported no detection. The valid RAD Game Tools signature, six-year circulation across hundreds of sources, and lack of corroborating payload evidence substantially outweigh the sandbox's isolated T1055 technique mapping.
4f60fb1acd3cc03da5…13603fb8e74334Recommended 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.
All 74 antivirus engines returned without a malicious or suspicious detection, including 14 tier-1 engines that reported no detection. The valid RAD Game Tools signature, six-year circulation across hundreds of sources, and lack of corroborating payload evidence substantially outweigh the sandbox's isolated T1055 technique mapping.
The sample received zero malicious and zero suspicious detections from 74 engines, with no tier-1 family consensus. Its signature verifies to RAD Game Tools, and no conflicting brand identity was detected. The DLL has circulated since 2020 through 657 distinct sources and 769 submissions, which is consistent with established commodity software. One completed sandbox mapped activity to T1055, but it produced no malicious sandbox verdict and observed eleven benign-common techniques alongside that single offensive mapping. Ten child hashes were inspected without a malicious child, while static analysis found neither likely packing nor high-entropy code. No complete contacted-host reputation result is available, although the saved run recorded no network contacts.
What We Detected
None of 74 antivirus engines flagged the DLL as malicious or suspicious. Fourteen tier-1 engines reported no detection, the file carries a verified signature from RAD Game Tools, and no publisher-brand conflict was identified. It has also been submitted 769 times by 657 sources since December 2020, indicating broad and long-standing distribution.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055, which can represent process injection. That mapping is worth noting, but it was not accompanied by a malicious sandbox verdict, persistence indicators, recorded network contacts, a malicious child file, or packing evidence. The ten inspected child hashes were not identified as malicious, although their individual classifications remain unknown. No complete contacted-host reputation cross-check was saved.
What To Do Now
Use the DLL only as part of software obtained from its official distributor or another trusted installation source. Keep endpoint protection enabled and verify that the file's RAD Game Tools signature remains valid if it was acquired separately or appeared unexpectedly.
Where this verdict could be wrong3 caveats
- The fired MalwareTips.Synth.ProcessInjection heuristic maps runtime evidence to T1055, a potentially offensive technique, although the single sandbox did not issue a malicious verdict.
- signing.signerStats.found=false, so there is no internal historical signer record to reinforce the valid 'RAD Game Tools' signature.
- contactedHosts=null means no saved host-reputation cross-check is available, though the recorded sandbox contacts were empty.
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/74 engines reported a malicious or suspicious detection.
- The code signature verifies to 'RAD Game Tools'.
- The file has 657 sources and 769 submissions dating to 2020.
- No malicious sandbox verdict or malicious child was recorded.
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false.
- One runtime heuristic mapped activity to MITRE T1055.
- No internal signer-history record exists for 'RAD Game Tools'.
- The contacted-host reputation cross-check was not completed or saved.
- All 10 inspected child hashes have unknown individual verdicts, despite no child being identified as malicious.
Retain or use the DLL when it came with legitimate software from a trusted source and its RAD Game Tools signature verifies. If its origin is unexpected, quarantine it for provenance checks while keeping endpoint protection enabled.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete1 signature or behavior rule 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
- 12MITRE ATT&CK techniques
- 2spawned processes
- 0network 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
2020.09-bink2w64.dll
4f60fb1acd3cc03da501fadc378b093f5ec99f5c99a7bb9d1013603fb8e74334
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\init.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 2964 -s 516
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
AppCrash_rundll32.exe_ini_3ed4789af864be6d9ab1185228a24be3778f62_4e5ca135_0c53dad6
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_ini_3ed4789af864be6d9ab1185228a24be3778f62_4e5ca135_0c53dad6
04Isolated runtime analysis - Written fileObserved
Report.wer
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_ini_3ed4789af864be6d9ab1185228a24be3778f62_4e5ca135_0c53dad6\Report.wer
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\ReportQueue\AppCrash_rundll32.exe_ini_3ed4789af864be6d9ab1185228a24be3778f62_4e5ca135_0c53dad6
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_ini_3ed4789af864be6d9ab1185228a24be3778f62_4e5ca135_0c53dad6\Report.wer
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_ini_578b1890a740ccb9878189733f9d76d0e5c86f_4e5ca135_1a23ce24
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_ini_578b1890a740ccb9878189733f9d76d0e5c86f_4e5ca135_1a23ce24\Report.wer
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_ini_65121ce9a5f3f0ba38b781f2b1b44124c6fa8db_4e5ca135_09bfc1b0
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER304D.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3465.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER358F.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER304D.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3465.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess2964
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\417efbee-6aa2-4d3e-8688-19fdc26dcfb9
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess2036
- \Sessions\1\BaseNamedObjects\Global\886f9a5a-329d-4fed-99b2-13427d16ce4e
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- f9658cb0bc660f3a0ab5…f41346Never scannednever seen before
- f575741c49c6fdd41fcd…2a7c88Never scannednever seen before
- 57f1e55b8ccac5d4a88a…4faa0dNever scannednever seen before
- b33427afdbbaa61c5b0f…201e33Never scannednever seen before
- b673888917e3b3141809…b0324dNever scannednever seen before
- 1fa5aad1dd7bf3f25839…15bb87Never scannednever seen before
- 13c340fd5e2a3c691922…b69702Never scannednever seen before
- 636708424b93f85ab6e2…c4a3b1Never scannednever seen before
- 29474bb339af9d831f58…69e833Never scannednever seen before
- 0cd04b42b45aea21ca99…f9694fNever 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.
- 1rule hit recorded
- 0 / 74engines flagged
- 657sources 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 657 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from RAD Game Tools.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: 2020.09-bink2w64.dll — 4f60fb1acd3cc03da501fadc378b093f5ec99f5c99a7bb9d1013603fb8e74334
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\init.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 2964 -s 516
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: AppCrash_rundll32.exe_ini_3ed4789af864be6d9ab1185228a24be3778f62_4e5ca135_0c53dad6 — C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_ini_3ed4789af864be6d9ab1185228a24be3778f62_4e5ca135_0c53dad6
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Report.wer — C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_ini_3ed4789af864be6d9ab1185228a24be3778f62_4e5ca135_0c53dad6\Report.wer
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>\AppData\Local\Temp\init.dll",#1
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
- 2020.09-bink2w64.dll
- Format
- Win32 DLL
- Code signing
- Signature valid: RAD Game Tools
- Size
- 385.7 KB
- Last analyzed
- Sep 23, 2026, 5:04 AM UTC
4f60fb1acd3cc03da501fadc378b093f5ec99f5c99a7bb9d1013603fb8e74334Safety & 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 2020.09-bink2w64.dll safe?
What is 2020.09-bink2w64.dll?
How many antivirus engines detected 2020.09-bink2w64.dll?
Is 2020.09-bink2w64.dll digitally signed?
What is the SHA-256 hash of 2020.09-bink2w64.dll?
Is it safe to use 2020.09-bink2w64.dll?
How up to date is this analysis of 2020.09-bink2w64.dll?
Community
Member reviews and reports for this exact file hash.