Is ScreenWings.exe safe?
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system.
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system.
481ecd41bef2a33076…80f602de19f214Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
Why this file is confirmed malware
The conclusion below is grounded in the recorded hash match and scan evidence.
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system.
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system. MalwareBazaar is a researcher-curated malware repository; hits there are ground-truth positives.
What We Detected
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system.
Threat Behavior
Refer to the confirmed malware threat family for known tactics.
What To Do Now
Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system with an up-to-date antivirus.
Where this verdict could be wrong1 caveat
- If this hash is a polymorphic-collision with a legitimate build, the MB label would be misleading — but MB curation makes this extremely rare.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- MalwareBazaar confirmed family: confirmed malware
- Researcher-uploaded malware sample
Delete this file from the device, then empty the Recycle Bin or Trash. Run a full-system antivirus scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete5 signature or behavior rules 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
- 21MITRE ATT&CK techniques
- 8spawned processes
- 20network contacts
- 26filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
ScreenWings.exe
481ecd41bef2a33076729680747eb92e4e2964bed89c58825d80f602de19f214
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
${SamplePath}\481ecd41bef2a33076729680747eb92e4e2964bed89c58825d80f602de19f214.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Roaming
C:\Users\user\AppData\Roaming
04Isolated runtime analysis - Written fileObserved
WER7CD3.tmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CD3.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:0:0:1400:0:0:0
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
13.107.4.50
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- a83f:8110:0:0:1400:0:0:0
- 13.107.4.50
- 23.40.197.137
- a83f:8110:766b:c00:400:80:100:0
- 23.216.147.76
- a83f:8110:0:0:6786:21:0:0
- 20.99.132.105
- 20.99.133.109
- 20.99.184.37
- a83f:8110:1a1a:1aff:1b1b:1bff:1b1b:1bff
- C:\Users\user\AppData\Roaming
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CD3.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CD3.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F93.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F93.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER38BE.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER38BF.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER396A.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER39BA.tmp.txt
- Global\{7e3fd23f-1c67-4c75-9169-ebcda3180d6e}
- 0x0
- \Sessions\1\BaseNamedObjects\Global\{7e3fd23f-1c67-4c75-9169-ebcda3180d6e}
- \BaseNamedObjects\Local\SM0:7124:304:WilStaging_02
- Local\SM0:7328:168:WilStaging_02
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 5rule hits recorded
- 4 / 74engines flagged
- 485sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The hash appears in a researcher-curated malware database.
Verdict inputView chapterProvenanceObservedSourceResearcher malware databaseObserved at - 02
4 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
4 of 74 antivirus engines flagged the file, including APEX and tehtris.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: ScreenWings.exe — 481ecd41bef2a33076729680747eb92e4e2964bed89c58825d80f602de19f214
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — ${SamplePath}\481ecd41bef2a33076729680747eb92e4e2964bed89c58825d80f602de19f214.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Roaming — C:\Users\user\AppData\Roaming
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: WER7CD3.tmp — C:\ProgramData\Microsoft\Windows\WER\Temp\WER7CD3.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:0:0:1400:0:0:0 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 13.107.4.50 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched 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.
- PE_Digital_Certificate
- PE_Potentially_Signed_Digital_Certificate
- Sectigo_Code_Signed
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:\Users\<USER>\AppData\Local\Temp\executable.exe"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.
Evidencea83f:8110:0:0:1400:0:0:0 · 13.107.4.50 · 23.40.197.137
4 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
- ScreenWings.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Hendrik Schiffer
- Size
- 4.0 MB
- Last analyzed
- Sep 10, 2026, 7:51 PM UTC
481ecd41bef2a33076729680747eb92e4e2964bed89c58825d80f602de19f214Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is ScreenWings.exe malware?
What is ScreenWings.exe?
How many antivirus engines detected ScreenWings.exe?
I already downloaded and ran ScreenWings.exe — what should I do?
How do I remove ScreenWings.exe?
What kind of malware is ScreenWings.exe?
Is ScreenWings.exe digitally signed?
Has ScreenWings.exe been seen before?
What is the SHA-256 hash of ScreenWings.exe?
How up to date is this analysis of ScreenWings.exe?
Community
Member reviews and reports for this exact file hash.