Is wt_launcher_1.0.3.535-njn5ccpcc.exe safe?
Unsigned 13 MB installer for War Thunder launcher shows zero detections across 74 engines and common prevalence.
No engine flagged the file. The sample is an unsigned installer that writes legitimate War Thunder binaries and opens firewall rules for the game. While four MITRE techniques were observed, the complete absence of detections and the common_new classification support a benign verdict.
20aa8c586e4c46371f…60574054317f4dRecommended 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 an unsigned installer that writes legitimate War Thunder binaries and opens firewall rules for the game. While four MITRE techniques were observed, the complete absence of detections and the common_new classification support a benign verdict.
Zero malicious detections from 74 engines, including 16 tier-1 engines, is the strongest signal. The file is unsigned, yet the prevalence data (187 submitters) and the dropped children matching known War Thunder components indicate a legitimate game launcher. The MITRE mappings reflect expected installer behaviour (firewall rules, process elevation) rather than confirmed malice. Similar imphash matches are framework collisions and do not outweigh the clean engine consensus.
What We Detected
74 engines scanned the 13 MB Win32 EXE; none returned a malicious or suspicious result. The sample is unsigned and contains no code-signing certificate. Sandbox execution recorded four MITRE techniques (T1055 process injection, T1134 token manipulation, T1485 data destruction, T1548 abuse elevation) plus direct-IP connections to 15 addresses, but contacted-host reputation cross-check found no malicious entries among the inspected hosts.
Threat Behavior
The installer drops War Thunder binaries (launcher.exe, gaijin_downloader.exe, etc.) and creates firewall rules for the game client. No malicious child files were produced, and external-intel sources (CIRCL, MalwareBazaar, YARAify) returned no hits. Prevalence is classified common_new with nearly 200 submissions, consistent with a widely distributed game updater.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If the file was obtained from the official Gaijin launcher portal, it can be executed; otherwise re-download from the vendor site to ensure integrity.
Where this verdict could be wrong2 caveats
- Unsigned installer with process-injection and direct-IP MITRE mappings could indicate malicious intent, but zero engine detections and common_new prevalence weaken that hypothesis.
- contactedHosts.inspected=1 covers only one of the 15 observed IPs, so host-reputation coverage is incomplete.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/74 engines flagged malicious
- common_new prevalence (187 sources)
- dropped children match known War Thunder components
- File is unsigned
- Observed MITRE techniques T1055, T1134, T1485, T1548
The evidence supports treating the file as benign; run it only if downloaded from the official War Thunder distribution channel and leave 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
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 23MITRE ATT&CK techniques
- 15spawned processes
- 40network contacts
- 33filesystem & 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
wt_launcher_1.0.3.535-njn5ccpcc.exe
20aa8c586e4c46371f17e38178adf297186aab5606761efb6860574054317f4d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\netsh" netsh advfirewall firewall add rule name="War Thunder" program="C:\Users\<USER>\AppData\Local\WarThunder\win64\aces-min-cpu.exe" protocol=UDP localport=20010-20500
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\system32\netsh" netsh advfirewall firewall add rule name="War Thunder" program="C:\Users\<USER>\AppData\Local\WarThunder\win64\aces-min-cpu.exe" protocol=UDP localport=3478-3480
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Communication
\Device\Http\Communication
04Isolated runtime analysis - Written fileObserved
wt_launcher_1.0.3.535-owpo6gh5q.tmp
C:\Users\<USER>\AppData\Local\Temp\is-VU46U.tmp\wt_launcher_1.0.3.535-owpo6gh5q.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
188.42.61.240
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
54.217.186.184
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.
- 188.42.61.240
- 54.217.186.184
- 3.161.241.91
- 172.66.151.104
- 104.18.18.220
- 23.205.110.202
- 209.192.190.204
- 18.238.171.48
- 89.149.224.35
- 239.255.255.250
- http://01.warthunder-cf.cdn.gaijin.net/warthunder/2.57.1.9/2a71a90656526d1937343e890c08f17908a06f4f/sound/dialogs_chat_en.assets.bank
- http://01.warthunder-cf.cdn.gaijin.net/warthunder/2.57.1.9/2a71a90656526d1937343e890c08f17908a06f4f/sound/dialogs_chat_en.bank
- http://01.warthunder-cf.cdn.gaijin.net/warthunder/2.57.1.9/2a71a90656526d1937343e890c08f17908a06f4f/BattlEye/Privacy/en.txt
- http://01.warthunder-cf.cdn.gaijin.net/warthunder/2.57.1.9/2a71a90656526d1937343e890c08f17908a06f4f/BattlEye/Text/cs.ini
- http://01.warthunder-cf.cdn.gaijin.net/warthunder/2.57.1.9/2a71a90656526d1937343e890c08f17908a06f4f/cef_paks.zip
- http://01.warthunder-cf.cdn.gaijin.net/warthunder/2.57.1.9/2a71a90656526d1937343e890c08f17908a06f4f/char.vromfs.bin
- \Device\Http\Communication
- C:\Users\<USER>\AppData\Local\Temp\is-VU46U.tmp\wt_launcher_1.0.3.535-owpo6gh5q.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-0OPI7.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\WarThunder\launcher.exe
- C:\Users\<USER>\AppData\Local\WarThunder\bpreport.exe
- C:\Users\<USER>\AppData\Local\WarThunder\is-C00PA.tmp
- C:\Users\<USER>\AppData\Local\WarThunder\is-8QKU0.tmp
- C:\Users\<USER>\AppData\Local\WarThunder\is-LPHRM.tmp
- C:\Users\<USER>\AppData\Local\WarThunder\is-933FA.tmp
- C:\Users\<USER>\AppData\Local\WarThunder\is-Q58DP.tmp
- Local\InternetShortcutMutex
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- cbe86cf047876ad8fbac…ec52c7Never scannednever seen before
- 0eef23c2185da153a05c…b84dbdNever scannednever seen before
- d753e45dde98e2627947…768e6dNever scannednever seen before
- 5b47aee36f594b7737e0…16bdb9Never scannednever seen before
- 44c1db6b7bf4103b2c4d…90a896Never scannednever seen before
- cc497b36d97123f1bf35…8158caNever scannednever seen before
- b0d2eb6892dba457d621…ccba01Never scannednever seen before
- a8335e43e14d45c59cfd…16f03aNever scannednever seen before
- ef4bc61593ad4ee1b587…04f63bNever scannednever seen before
- 9baee42d66f715bba878…b40256Never 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
- 187sources 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
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: wt_launcher_1.0.3.535-njn5ccpcc.exe — 20aa8c586e4c46371f17e38178adf297186aab5606761efb6860574054317f4d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\netsh" netsh advfirewall firewall add rule name="War Thunder" program="C:\Users\<USER>\AppData\Local\WarThunder\win64\aces-min-cpu.exe" protocol=UDP localport=20010-20500
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\system32\netsh" netsh advfirewall firewall add rule name="War Thunder" program="C:\Users\<USER>\AppData\Local\WarThunder\win64\aces-min-cpu.exe" protocol=UDP localport=3478-3480
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Communication — \Device\Http\Communication
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: wt_launcher_1.0.3.535-owpo6gh5q.tmp — C:\Users\<USER>\AppData\Local\Temp\is-VU46U.tmp\wt_launcher_1.0.3.535-owpo6gh5q.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 188.42.61.240 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 54.217.186.184 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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\Explorer.EXEThe 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.
Evidence188.42.61.240 · 54.217.186.184 · 3.161.241.91
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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- wt_launcher_1.0.3.535-njn5ccpcc.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 12.7 MB
- Last analyzed
- Jul 30, 2026, 6:34 AM UTC
20aa8c586e4c46371f17e38178adf297186aab5606761efb6860574054317f4dSafety & 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 wt_launcher_1.0.3.535-njn5ccpcc.exe safe?
What is wt_launcher_1.0.3.535-njn5ccpcc.exe?
How many antivirus engines detected wt_launcher_1.0.3.535-njn5ccpcc.exe?
What is the SHA-256 hash of wt_launcher_1.0.3.535-njn5ccpcc.exe?
Is it safe to run wt_launcher_1.0.3.535-njn5ccpcc.exe?
How up to date is this analysis of wt_launcher_1.0.3.535-njn5ccpcc.exe?
Community
Member reviews and reports for this exact file hash.