Is veax.exe safe?
Forty-eight of 75 engines detected this unsigned executable, while Barys naming, process injection, service creation, and seven YARA matches provide strong corroboration.
The executable is detected by 48 of 75 engines, including nine high-trust detections and repeated Barys identification. A completed sandbox run recorded process injection, service creation, PowerShell execution, and reflective code loading; keep endpoint protection enabled and quarantine the file.
b8386e6d73ab4786a4…c67624dbb2698cRecommended 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.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The executable is detected by 48 of 75 engines, including nine high-trust detections and repeated Barys identification. A completed sandbox run recorded process injection, service creation, PowerShell execution, and reflective code loading; keep endpoint protection enabled and quarantine the file.
Detection is broad: 48 of 75 engines flagged the sample, including nine high-trust engines. BitDefender, Emsisoft, and GData converge on Barys, while other engines use GenKryptik, MalwareX, Tedy, or generic trojan labels. Runtime evidence records six offensive techniques, notably T1055.003 process injection, T1543.003 service creation, and T1620 reflective code loading. Seven YARA rules matched, independently strengthening the engine evidence, and the executable is unsigned. No complete reputation result is available for the observed IP contacts because the contacted-host cross-check was not saved.
What We Detected
48 of 75 antivirus engines flagged the executable, including nine high-trust detections. BitDefender, Emsisoft, and GData identify the Barys family, while ESET-NOD32 reports GenKryptik and Microsoft reports Tedy. The different names indicate imperfect family attribution, but the broad trojan assessment is consistent.
Threat Behavior
One completed sandbox run recorded six offensive MITRE techniques: T1055.003 process injection, T1059.001 PowerShell, T1134 access-token manipulation, T1543.003 Windows service creation, T1560 archive collection, and T1620 reflective code loading. Seven YARA rules also matched, including debugger-checking rules. The sample contacted several external IP addresses, but no complete saved host-reputation assessment is available for those contacts.
What To Do Now
Do not execute the file. Keep endpoint protection enabled, quarantine or remove the sample, and run a full system scan. If it already ran, isolate the device from untrusted networks and review services, PowerShell activity, credentials, and other endpoints for related indicators.
Where this verdict could be wrong4 caveats
- behaviour.hasMaliciousSandboxVerdict=false, although the completed run still recorded six offensive techniques.
- engines.tier1FamilyConsensus.strong=false and labels vary among Barys, MalwareX, GenKryptik, Tedy, and other generic trojan names.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false, so no static packing indicator supports the detections.
- prevalence.classification=common_old with 336 sources and 386 submissions, which reduces uncertainty about novelty but does not outweigh the detections.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- peAnalysis.highEntropyCode=false
- peAnalysis.likelyPacked=false
- droppedChildren contains no recorded malicious child
- behaviour.hasMaliciousSandboxVerdict=false
- 48/75 antivirus-engine detections
- Nine high-trust engines flagged the executable
- Repeated Barys-family identification
- T1055.003 process injection evidence
- T1543.003 Windows service creation evidence
- T1620 reflective code loading evidence
Quarantine the file and run a full endpoint scan while keeping all security protections enabled. If it executed, isolate the system and investigate service creation, PowerShell activity, process injection, and possible credential exposure.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete48 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial19 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete7 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
- 27MITRE ATT&CK techniques
- 11spawned processes
- 19network contacts
- 1filesystem & 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: Used an input-capture technique that can record credentials or keystrokes.
High concern: Created or modified a system service, which can keep code running.
High concern: Manipulated how the operating system loads code, which can redirect execution.
High concern: Loaded code directly into memory instead of from a normal file.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
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
veax.exe
b8386e6d73ab4786a4bb03c32759caddcdf89ace25e9070428c67624dbb2698c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\veax.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\UI0Detect.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.40
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
a83f:8110:0:0:678e:21:0:0
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- 192.168.0.40
- a83f:8110:0:0:678e:21:0:0
- 20.99.133.109
- 23.55.140.42
- 192.168.0.22
- a83f:8110:0:0:0:200:0:0
- 192.168.0.55
- 20.69.140.28
- 23.196.193.245
- 184.27.218.92
- %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache\IE\KLT1I0ZU\update50[1].xml
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 7rule hits recorded
- 48 / 75engines flagged
- 336sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
48 of 75 antivirus engines flagged the file, including AhnLab-V3 and Alibaba.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 336 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: veax.exe — b8386e6d73ab4786a4bb03c32759caddcdf89ace25e9070428c67624dbb2698c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\veax.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\UI0Detect.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 192.168.0.40 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: a83f:8110:0:0:678e:21:0:0 — 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.
- Check_Debugger
- DebuggerCheck__API
- DebuggerCheck__RemoteAPI
- dsc
- golang_bin_JCorn_CSC846
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%SAMPLEPATH%\veax.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.
Evidencea83f:8110:0:0:678e:21:0:0 · 20.99.133.109 · 23.55.140.42
48 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
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
- veax.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 2.7 MB
- Last analyzed
- Sep 10, 2026, 12:22 PM UTC
b8386e6d73ab4786a4bb03c32759caddcdf89ace25e9070428c67624dbb2698cSafety & 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
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- 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 veax.exe a virus?
What is veax.exe?
How many antivirus engines detected veax.exe?
What should I do if I already ran veax.exe?
How do I remove veax.exe?
What kind of malware is veax.exe?
What is the SHA-256 hash of veax.exe?
How up to date is this analysis of veax.exe?
Community
Member reviews and reports for this exact file hash.