File scan report
Verdict Safe
Is scrcpy. exe safe? Yes, no threats found.
None of the 68 antivirus engines that checked it flagged this executable, and its sole sandbox run returned clean, although an unconfirmed mapping warrants routine caution.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
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 68 flagged
- Flagged 0
- No detection 68
- No result 7
- Code signing Unsigned
- Test run Completed
- First seen 19d 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
None of the 68 antivirus engines that checked it flagged the executable, including all 17 major antivirus engines represented in the evidence. One completed sandbox run returned clean; its mapping lacked an identified injection target, while the unsigned status and recent first submission justify obtaining the file from a trusted source.
The antivirus result is uniformly favorable: none of the 68 antivirus engines that checked it flagged the file, and there is no named threat family. The completed sandbox run returned clean and showed no malicious files it created or persistence indicators. It did map T1055, but no injected process or target was identified, so that mapping alone is insufficient to establish hostile process injection. Static PE analysis found neither packing nor high-entropy code. Confidence is moderated because the executable is unsigned, recently observed, and no complete contacted-host reputation check is available.
What We Detected
None of the 68 antivirus engines that checked it flagged the executable, including the 17 major antivirus engines represented in the evidence. No malware family, hacking tool label, external-intelligence hit, packing indicator, or high-entropy code was reported.
Threat Behavior
One completed sandbox run returned clean. It mapped activity to MITRE T1055, which can relate to process injection, but no injected process or target was identified; no persistence indicators, malicious files it created, or sample-attributed network contacts were recorded. A complete host-reputation cross-check was not available.
What To Do Now
Obtain the executable from the project's official distribution channel and verify its published checksum when possible. Keep security software enabled, especially because this copy is unsigned and was first observed on Oct 8, 2026.
Where this verdict could be wrong3 caveats
- The executable is unsigned, so there is no verified publisher identity.
- The sandbox mapped T1055, which can indicate process injection, but no injected process or target was identified.
- The sample was first submitted on Oct 8, 2026, limiting the value of its current detection history.
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 68 antivirus engines that checked it flagged the executable.
- All 17 major antivirus engines represented in the evidence returned no detection.
- The completed sandbox run returned clean and recorded no persistence indicators.
- Static PE analysis found no packer and no high-entropy executable code.
- No malicious file it created or external-intelligence match was found.
- The executable has no verified digital signature or established publisher history.
- The sample was first observed on Oct 8, 2026, so its reputation history is limited.
- A runtime mapping referenced possible process injection, although it did not identify an injected process or target.
- No complete reputation check was available for contacted hosts.
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 11sandbox rule tags
- 3spawned processes
- 0network contacts
- 1filesystem & 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
11MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1036
- T1055· Process injection
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1553
- T1553.002
Observed activity
Processes started
3Programs the file ran, with their command lines.
program.exe"C:\Users\user\Desktop\program.exe" -installprogram.exe"C:\Users\user\Desktop\program.exe" /installprogram.exe"C:\Users\user\Desktop\program.exe" /load
Files
1Files the file created, changed or deleted.
- Written
\Device\ConDrv\\Connect
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1
Chapter 04
Technical details
None of the 68 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 10, 2026, 12:58 AM UTC
- SHA-256
64bcee493d9243dab1e84093928014348738e31f3225e67558210e6b6cfb9cd6- SHA-1
7adc3ddacc125713484971ceaa98da77f7fab644- MD5
182e3f2ad0d50111a2af8b6991da2b8f
About this file
scrcpy.exe is a Win32 EXE file of 766.7 kB.
- Type and size
- Win32 EXE · 766.7 kB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 8, 2026On VirusTotal.
- Submitted by
- 26 distinct sources
- Packer
- None detected
- Entropy
- 5.97 of 8
First scanned
Antivirus consensus
0 of 68 engines flagged this file
7 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-118 engines0flagged
- Tier-233 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
- ClamAVNo result
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaNo result
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is scrcpy.exe safe?
What is scrcpy.exe?
How many antivirus engines detected scrcpy.exe?
What is the SHA-256 hash of scrcpy.exe?
Is it safe to run scrcpy.exe?
How up to date is this analysis of scrcpy.exe?
Community
Member reviews and reports for this exact file hash.