Is UnityPlayer safe?
Unity Technologies signed DLL with zero detections across 75 engines and widespread legitimate distribution.
All 75 engines returned clean results, including 17 tier-1 engines. The file is signed by Unity Technologies SF and has been submitted by 408 sources over 261 days with no malicious indicators.
b18b328000c79f5dc1…13dca2ea298d04Recommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened 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 75 engines returned clean results, including 17 tier-1 engines. The file is signed by Unity Technologies SF and has been submitted by 408 sources over 261 days with no malicious indicators.
Zero malicious detections from any engine tier combined with a verified Unity Technologies signature and common_old prevalence classification indicate this is a legitimate Unity Player component. Sandbox analysis produced no malicious verdict and no malicious child files were dropped. The absence of packing, high-entropy code, or triggered heuristics further supports a clean determination.
What We Detected
75 antivirus engines scanned the file; none flagged it as malicious. The DLL carries a valid code-signing certificate from Unity Technologies SF. No sandbox flagged malicious behaviour and the single dropped child file received no malicious verdict.
Threat Behavior
Observed MITRE techniques are ambient only (T1027, T1056, T1082, etc.) and consistent with normal Unity runtime operations. No offensive techniques, persistence mechanisms, or malicious network activity were recorded.
What To Do Now
The file can be considered safe for use. Keep endpoint protection enabled and only download Unity components from official sources.
- Verified Unity Technologies signature
- Zero detections across 75 engines
- Common_old prevalence with 408 submitters
Treat as a legitimate Unity Player component; no further action required.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 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
- 8MITRE ATT&CK techniques
- 9spawned processes
- 0network contacts
- 5filesystem & 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
UnityPlayer
b18b328000c79f5dc1d3eb6762dfbc97cd878ae150eb8559b913dca2ea298d04
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\attachment.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\UnityPlayer.dll"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Player.log
C:\Users\<USER>\AppData\LocalLow\Unknown Vendor\Unknown Unity Application\Player.log
04Isolated runtime analysis - Written fileObserved
Unknown Vendor
C:\Users\user\AppData\LocalLow\Unknown Vendor
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:\Users\<USER>\AppData\LocalLow\Unknown Vendor\Unknown Unity Application\Player.log
- C:\Users\user\AppData\LocalLow\Unknown Vendor
- C:\Users\user\AppData\LocalLow\Unknown Vendor\Unknown Unity Application
- C:\Users\user\AppData\LocalLow\Unknown Vendor\Unknown Unity Application\Player.log
- \Device\ConDrv\\Connect
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- f25f228e95f6d8f05ec2…dc61f7Never 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
- 0 / 75engines flagged
- 408sources 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 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 408 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from Unity Technologies SF.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: UnityPlayer — b18b328000c79f5dc1d3eb6762dfbc97cd878ae150eb8559b913dca2ea298d04
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\attachment.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\UnityPlayer.dll"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Player.log — C:\Users\<USER>\AppData\LocalLow\Unknown Vendor\Unknown Unity Application\Player.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Unknown Vendor — C:\Users\user\AppData\LocalLow\Unknown Vendor
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.
0 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
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
- UnityPlayer
- Format
- Win32 DLL
- Code signing
- Signature valid: Unity Technologies SF
- Size
- 32.1 MB
- Last analyzed
- Sep 7, 2026, 10:40 AM UTC
b18b328000c79f5dc1d3eb6762dfbc97cd878ae150eb8559b913dca2ea298d04Safety & 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
Open it only when its sender or download source is one 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 UnityPlayer safe?
What is UnityPlayer?
How many antivirus engines detected UnityPlayer?
Is UnityPlayer digitally signed?
What is the SHA-256 hash of UnityPlayer?
Is it safe to open UnityPlayer?
How up to date is this analysis of UnityPlayer?
Community
Member reviews and reports for this exact file hash.