Safe
Zero engine detections across 72 reporting engines with clean sandbox behaviour despite one heuristic on direct-IP usage.
3432bd1996ec998c41…7f84cd6f80The verdict, reasoned out.
Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.
The file triggered zero malicious detections from any engine tier. Sandbox execution produced only ambient techniques and wrote expected configuration and cache files without persistence or malicious children. While the DirectIpC2 heuristic flagged eight direct-IP contacts without DNS resolution, this pattern alone does not override the unanimous clean engine consensus and medium prevalence over 1148 days. No external intelligence sources returned hits. The unsigned status is noted but does not elevate risk given the absence of any malicious indicators.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.tier1ReportedClean=18 with engines.malicious=0
signing.signed=false and signing.signerStats.found=false
behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false
triggeredHeuristics[0].rule=MalwareTips.Synth.DirectIpC2 (medium severity)
prevalence.classification=medium (39 uniqueSources)
- Zero malicious detections across all engine tiers
- Clean sandbox verdict and no malicious dropped children
- Medium prevalence with 1148-day history and no external-intel hits
- Unsigned executable
- Direct IP communication without DNS (heuristic trigger)
Treat as safe for intended use; the single heuristic is insufficient to override unanimous clean engine results and clean behavioural profile.
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.
- 20.99.186.246
- 192.229.211.108
- 20.99.133.109
- 23.216.147.64
- 184.25.191.235
- 20.99.185.48
- a83f:8110:3deb:929:d811:7000:3000:6fee
- 20.99.184.37
- xenia.log
- C:\Users\<USER>\Documents\Xenia\xenia.config.toml
- C:\Users\<USER>\Downloads\xenia.log
- C:\Users\user\AppData\Local\D3DSCache
- C:\Users\user\AppData\Local\D3DSCache\22221b550a9147e4\
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C7.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B2.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER6F1.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD98.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD99.tmp.csv
- DirectInput.{89521361-AA8A-11CF-BFC7-444553540000}
- DirectInput.{5944E682-C92E-11CF-BFC7-444553540000}
- \Sessions\1\BaseNamedObjects\DirectInput.{89521361-AA8A-11CF-BFC7-444553540000}
- \Sessions\1\BaseNamedObjects\DirectInput.{5944E682-C92E-11CF-BFC7-444553540000}
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 751b88e8c1a502b90fb7…b44c90Never scannednever seen before
- d4c13eecb8f9ca2b84ea…456f60Never scannednever seen before
- 7852fce59c67ddf1d6b8…011fbaNever scannednever seen before
- 87380a0c13f55f9e09a2…c9d078Never scannednever seen before
YARA + heuristic rules that fired
One or more medium-severity heuristic rules matched. Not definitive, but the patterns match known malware behaviour.
Sample contacted 8 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence20.99.186.246 · 192.229.211.108 · 20.99.133.109
0 detections across 76 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.
How often this file shows up in the wild
Moderate prevalence — neither rare nor common. No strong prior applies.
Forensic fingerprint
- File name
- xenia.exe
- Size
- 11.01 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- 3432bd1996ec998c417cc6a51ca03d72496ba64076789ccbdacb7f7f84cd6f80
- MD5
- 67e903d37307a3795e664cc1726e9c02
- SHA-1
- c9d673dcffae3effe6fd210fe367536ffdd92cb4
- PE imphash
- 79f010452b8e4431729db5090c2961d5
- First seen (VT)
- 5/19/2023, 11:50:59 PM
- Last analysis (VT)
- 3/26/2024, 9:44:05 AM
- First scan (MalwareTips)
- 7/10/2026, 8:24:23 PM
- Last scan (MalwareTips)
- 7/10/2026, 8:24:23 PM
Safety FAQ
Common questions about xenia.exe, answered from the scan data above.
- xenia.exe appears safe. 76 of 76 antivirus engines report it clean. As a habit, only run files you downloaded from the official source, since attackers sometimes distribute trojanised copies of legitimate software under the same name.
- xenia.exe is a Windows executable program, about 11 MB. Our analysis found no threat indicators for it. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
- None — all 76 antivirus engines we queried report xenia.exe as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- The SHA-256 hash of xenia.exe is 3432bd1996ec998c417cc6a51ca03d72496ba64076789ccbdacb7f7f84cd6f80, and its MD5 is 67e903d37307a3795e664cc1726e9c02. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- Based on this scan, yes — xenia.exe shows no threat indicators. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it while we report it clean, that is most often a false positive, but verify the source before overriding your antivirus.
- This report reflects the scan run on July 10, 2026. Because a file's hash never changes, the identity of xenia.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.