File scan report
Verdict Malicious
Is veax. exe safe? No, we rate this exact file malicious.
The executable is detected by 48 of the 71 antivirus engines that checked it, including nine major detections and repeated Barys identification.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already ran it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
48 of 71 flagged
- Flagged 48
- No detection 23
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
6 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Detection is broad: 48 of the 71 antivirus engines that checked it flagged the sample, including nine major antivirus engines. BitDefender, Emsisoft, and GData converge on Barys, while other engines use GenKryptik, MalwareX, Tedy, or generic trojan labels. 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 the 71 antivirus engines that checked it flagged the executable, including nine major 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
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 security software 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 devices for related indicators.
Where this verdict could be wrong4 caveats
- No sandbox returned a malicious verdict, although the completed run still recorded six offensive techniques.
- Major antivirus engines do not agree on one malware family and labels vary among Barys, MalwareX, GenKryptik, Tedy, and other generic trojan names.
- No code section has packed-level entropy and the file does not appear packed, so no static packing indicator supports the detections.
- The file is widely seen and long established 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.
- No code section has packed-level entropy
- The file does not appear packed
- droppedChildren contains no recorded malicious child
- No sandbox returned a malicious verdict
- 48/71 antivirus-engine detections
- Nine major antivirus engines flagged the executable
- Repeated Barys-family identification
- T1543.003 Windows service creation evidence
- reflective code loading evidence
- Unsigned Win32 executable
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 27sandbox rule tags
- 4spawned processes
- 3network contacts
- 1filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Used an unusual way to talk to a server.
Moderate concern: Stopped a service or program on the test computer.
Note: Read the network settings of the test computer.
Note: Listed the programs running on the test computer.
Note: Talked to servers over the internet during the test run.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, 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.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
veax.exe
b8386e6d73ab4786a4bb03c32759caddcdf89ace25e9070428c67624dbb2698c
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
veax.exe
Test run - Evidence 3 of 5: ProcessSeen in the test run
b8386e6d73ab4786a4bb03c32759caddcdf89ace25e9070428c67624dbb2698c.exe
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 4 of 5: Contacted hostSeen in the test run
104.98.118.163
Contacted during the test run.
Test run - Evidence 5 of 5: Contacted hostSeen in the test run
23.53.122.211
Contacted during the test run.
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 27 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
48 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 48
- Avast (major engine)Win64:MalwareX-gen [Cryp]
- AVG (major engine)Win64:MalwareX-gen [Cryp]
- Avira (major engine)TR/W64.MalwareX
- BitDefender (major engine)Gen:Variant.Barys.504257
- Emsisoft (major engine)Gen:Variant.Barys.504257 (B)
- ESET-NOD32 (major engine)Win64/GenKryptik.HHUX trojan
- F-Secure (major engine)Trojan.TR/W64.MalwareX
- Fortinet (major engine)W64/GenKryptik.HHUO!tr
File fingerprint
- Last analyzed
- Sep 10, 2026, 12:22 PM UTC
- SHA-256
b8386e6d73ab4786a4bb03c32759caddcdf89ace25e9070428c67624dbb2698c- SHA-1
6958e0488935b4abd613b515eb13c1ac950a83e7- MD5
230c6f781dd6e773fe8dedcd6213e999
About this file
veax.exe is a Win32 EXE file of 2.9 MB.
- Type and size
- Win32 EXE · 2.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- May 16, 2025On VirusTotal.
- Submitted by
- 336 distinct sources
- Packer
- None detected
- Entropy
- 6.75 of 8
First scanned
Includes every engine result (75), 8 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
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.