Is suf_launch.exe safe?
Zero detections across 74 engines, common for years, unsigned installer with sandbox process-injection flags.
No engine flagged the file. The sample is a 55 MB unsigned EXE that has been submitted 602 times since 2019. Sandbox recorded process-injection and direct-IP activity, but returned no malicious verdict and no malicious children were dropped.
99f5f6ea0319770ad4…98d9d56ab4f2d0Recommended 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.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
No engine flagged the file. The sample is a 55 MB unsigned EXE that has been submitted 602 times since 2019. Sandbox recorded process-injection and direct-IP activity, but returned no malicious verdict and no malicious children were dropped.
Zero malicious detections from 74 engines, including 17 tier-1 engines, rules out widespread malware consensus. The file is unsigned, yet its prevalence classification of common_old and 544 unique submitters indicate it has circulated for years without raising alarms. Sandbox telemetry shows MITRE techniques T1055, T1485, T1486, T1547.001 and T1548, but the sandbox itself issued no malicious verdict and dropped ten children that also carry no malicious verdicts. Contacted-host reputation data is unavailable, so the direct-IP traffic cannot be confirmed malicious. The combination of long-term prevalence, zero engine detections, and lack of corroborating malicious signals supports a safe determination.
What We Detected
74 engines scanned the 55 MB Win32 EXE; none returned a malicious or suspicious result. The file is unsigned and contains no code-signing certificate. Sandbox execution recorded MITRE techniques T1055 (process injection), T1485/T1486 (data destruction), T1547.001 (boot-persistence) and T1548 (privilege escalation), plus direct-IP connections to 18 addresses. Ten dropped child files were inspected; none carried malicious verdicts.
Threat Behavior
The observed techniques are consistent with a self-extracting installer that performs system-level setup tasks. No sandbox verdict labeled the activity malicious, and no external-intel source (CIRCL, MalwareBazaar, YARAify) produced a hit. The file has been submitted 602 times by 544 sources since March 2019, indicating long-term benign distribution.
What To Do Now
Keep endpoint protection enabled. If the file originates from a trusted vendor, verify its digital signature or checksum against the publisher. Otherwise treat any unsigned installer with caution and run it only in an isolated environment.
Where this verdict could be wrong1 caveat
- Sandbox observed T1055 process injection and direct-IP traffic, but sandboxVerdicts is empty and contactedHosts is null so no host-reputation result is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 74 engines
- Common_old prevalence (602 submissions since 2019)
- No malicious child files dropped
- No external-intel hits
- Unsigned executable
- Sandbox observed process-injection and file-wipe techniques
The evidence supports treating the file as safe for normal use, provided it is obtained from a trusted source; keep all security software active.
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
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 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
- 24MITRE ATT&CK techniques
- 12spawned processes
- 20network 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
suf_launch.exe
99f5f6ea0319770ad44e39fc69fca128c13c5fac8a167997b698d9d56ab4f2d0
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\suf_launch.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
irsetup.exe
C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\irsetup.exe
04Isolated runtime analysis - Written fileObserved
lua5.1.dll
C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\lua5.1.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
142.250.125.94
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
209.197.3.8
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.
- 142.250.125.94
- 209.197.3.8
- 131.253.33.203
- 23.216.147.76
- 23.216.147.64
- 20.99.132.105
- 23.40.197.137
- 20.62.24.77
- 20.99.133.109
- 192.168.0.1
- C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\irsetup.exe
- C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\lua5.1.dll
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\CMS\Uninstall CMS.lnk
- C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\irsetup.dat
- C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\IRIMG1.JPG
- C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\irsetup.exe
- C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0
- C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\lua5.1.dll
- C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\
- C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Caches\{AFBF9F1A-8EE8-4C77-AF34-C647E37CA0D9}.1.ver0x0000000000000000.db
- Local\ZonesCacheCounterMutex
- Local\ZonesLockedCacheCounterMutex
- Global\OneSettingQueryMutex+compat+encapsulation
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\AmiProviderMutex_InventoryApplication
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 5ffd4b20dccfb84c8890…1f97d9Never scannednever seen before
- 214286fbccef2eca0bee…e4be80Never scannednever seen before
- 2e50b1f56fc0c74c255c…5a17b7Never scannednever seen before
- 98b4229f27dea4d268a4…f07bfdNever scannednever seen before
- 398d6850b11ebc9d7203…b24eaaNever scannednever seen before
- 6641f9981028a2e9b98b…cf14d4Never scannednever seen before
- b773ddca7388f466d968…1908fcNever scannednever seen before
- 599a22467459640bf918…35df35Never scannednever seen before
- 7db3589ebefcecf85538…924760Never scannednever seen before
- a5fc3c2ec14b54181b84…745b48Never 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.
- 2rule hits recorded
- 0 / 74engines flagged
- 544sources 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 544 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: suf_launch.exe — 99f5f6ea0319770ad44e39fc69fca128c13c5fac8a167997b698d9d56ab4f2d0
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\suf_launch.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: irsetup.exe — C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\irsetup.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: lua5.1.dll — C:\Users\<USER>\AppData\Local\Temp\_ir_sf_temp_0\lua5.1.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 142.250.125.94 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 209.197.3.8 — Contact observed during runtime.
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.
EvidenceC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -pThe 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.
Evidence142.250.125.94 · 209.197.3.8 · 131.253.33.203
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
- suf_launch.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 53.2 MB
- Last analyzed
- Aug 19, 2026, 3:48 AM UTC
99f5f6ea0319770ad44e39fc69fca128c13c5fac8a167997b698d9d56ab4f2d0Safety & 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 suf_launch.exe safe?
What is suf_launch.exe?
How many antivirus engines detected suf_launch.exe?
What is the SHA-256 hash of suf_launch.exe?
Is it safe to run suf_launch.exe?
How up to date is this analysis of suf_launch.exe?
Community
Member reviews and reports for this exact file hash.