Is winscript-portable.exe safe?
Safe file assessment
0 of 75 antivirus engines flagged the file.
217663b0928af6be64…c48fec47434707Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
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
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
Not runNo independent reference checks are recorded.
No timestamp recorded
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 7MITRE ATT&CK techniques
- 5spawned processes
- 1network contacts
- 15filesystem & 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
winscript-portable.exe
217663b0928af6be647766aa9d81e028802e7b957258e821f0c48fec47434707
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\winscript-portable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\winscript-portable.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
flick.winscript.dev
C:\Users\user\AppData\Local\flick.winscript.dev
04Isolated runtime analysis - Written fileObserved
EBWebView
C:\Users\user\AppData\Local\flick.winscript.dev\EBWebView
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\user\AppData\Local\flick.winscript.dev
- C:\Users\user\AppData\Local\flick.winscript.dev\EBWebView
- C:\Users\user\AppData\Local\flick.winscript.dev\EBWebView\BrowserMetrics
- C:\Users\user\AppData\Local\flick.winscript.dev\EBWebView\BrowserMetrics\BrowserMetrics-69ED4E5D-7DC.pma
- C:\Users\user\AppData\Local\flick.winscript.dev\EBWebView\Crashpad
- \Sessions\1\BaseNamedObjects\DBWinMutex
- \Sessions\1\BaseNamedObjects\Local\ChromeProcessSingletonStartup!
- \Sessions\1\BaseNamedObjects\__OMADM_NAMED_MUTEX__
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 41c91a9c93d76295746a…1cc304Never scannednever seen before
- f7b24f2eb3d5eb055052…8b5fedNever 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 / 75engines flagged
- 18sources 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
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
The hash has been submitted 19 times from 18 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: winscript-portable.exe — 217663b0928af6be647766aa9d81e028802e7b957258e821f0c48fec47434707
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\winscript-portable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\winscript-portable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: flick.winscript.dev — C:\Users\user\AppData\Local\flick.winscript.dev
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: EBWebView — C:\Users\user\AppData\Local\flick.winscript.dev\EBWebView
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
This legacy report does not record whether the independent reference checks completed.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- winscript-portable.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 10.7 MB
- Last analyzed
- Apr 27, 2026, 9:43 AM UTC
217663b0928af6be647766aa9d81e028802e7b957258e821f0c48fec47434707Safety & 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
Run it only when it came 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 winscript-portable.exe safe?
What is winscript-portable.exe?
How many antivirus engines detected winscript-portable.exe?
What is the SHA-256 hash of winscript-portable.exe?
Is it safe to run winscript-portable.exe?
How up to date is this analysis of winscript-portable.exe?
Community
Member reviews and reports for this exact file hash.