Is LoaderExodus.exe safe?
Seven tier-1 engines flag this unsigned 3-day-old EXE as MalwareX-gen with direct-IP contact observed.
20 of 75 engines, including seven tier-1 detections, label the file Win64:MalwareX-gen [Misc] or Trojan variants. The sample is unsigned, three days old, and contacted an external IP without domain resolution.
1258813c624c736290…f2d5211687f43eRecommended 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.
20 of 75 engines, including seven tier-1 detections, label the file Win64:MalwareX-gen [Misc] or Trojan variants. The sample is unsigned, three days old, and contacted an external IP without domain resolution.
Multiple high-trust engines converge on malicious labels despite the absence of a strong family consensus. The file lacks any code signature and shows direct-IP network activity flagged by the DirectIpC2 heuristic. No sandbox verdict was returned and external-intel sources are silent, yet the tier-1 count alone outweighs these gaps. Medium prevalence and recent first-seen date indicate active distribution rather than a legacy false positive.
What We Detected
Seven tier-1 engines (Avast, AVG, Avira, ESET-NOD32, F-Secure, Microsoft, Symantec) plus additional tier-2 and low-trust detections returned malicious labels. The dominant family string is MalwareX-gen [Misc]. The executable is unsigned and three days old.
Threat Behavior
One sandbox execution recorded direct-IP contact to 162.159.36.2 and triggered the DirectIpC2 heuristic. No dropped children, persistence mechanisms, or malicious sandbox verdict were observed. No researcher rules from YARAify or CIRCL matched the sample.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and submit the sample to your security vendor for further analysis if additional context is required.
Where this verdict could be wrong2 caveats
- behaviour.hasMaliciousSandboxVerdict=false and sandboxCount=1 — single sandbox run showed no malicious verdict.
- externalIntel.yaraify.ruleCount=0 and MalwareBazaar.hit=false — no researcher-curated rules or family hits.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- single sandbox run returned no malicious verdict
- no external-intel corroboration
- 7 tier-1 malicious detections
- unsigned executable
- direct-IP contact observed
- recent first-seen (3 days)
Block or quarantine the file; the tier-1 consensus and unsigned status indicate malicious intent.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete20 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 5MITRE ATT&CK techniques
- 2spawned processes
- 1network contacts
- 1filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
Note: Connected to 1 server during sandbox analysis.
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
LoaderExodus.exe
1258813c624c736290620d809c88b44b48b8e65432bc90c5dbf2d5211687f43e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Connect
\Device\ConDrv\\Connect
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
05Isolated runtime analysis
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.
- 162.159.36.2
- \Device\ConDrv\\Connect
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 20 / 75engines flagged
- 16sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
20 of 75 antivirus engines flagged the file, including AhnLab-V3 and APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 16 times from 16 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: LoaderExodus.exe — 1258813c624c736290620d809c88b44b48b8e65432bc90c5dbf2d5211687f43e
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\user\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Connect — \Device\ConDrv\\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The 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.
Evidence162.159.36.2
20 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- LoaderExodus.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 38.4 MB
- Last analyzed
- Aug 21, 2026, 12:16 AM UTC
1258813c624c736290620d809c88b44b48b8e65432bc90c5dbf2d5211687f43eSafety & 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
If you typed any passwords while it was open, change them from a device you trust.
- 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 LoaderExodus.exe a virus?
What is LoaderExodus.exe?
How many antivirus engines detected LoaderExodus.exe?
What should I do if I already ran LoaderExodus.exe?
How do I remove LoaderExodus.exe?
What kind of malware is LoaderExodus.exe?
What is the SHA-256 hash of LoaderExodus.exe?
How up to date is this analysis of LoaderExodus.exe?
Community
Member reviews and reports for this exact file hash.