Is Xeno.exp safe?
No antivirus engine detected the COFF file, including the reporting tier-1 products, and moderate prevalence has produced no corroborated threat intelligence.
All 75 antivirus engines returned no malicious or suspicious finding, with 16 tier-1 products reporting no detection. The file has appeared across 420 sources and 478 submissions without threat-intelligence corroboration, although no completed sandbox run or host-reputation check is available.
b29565ca546538917a…453f88174bd87bRecommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened 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.
All 75 antivirus engines returned no malicious or suspicious finding, with 16 tier-1 products reporting no detection. The file has appeared across 420 sources and 478 submissions without threat-intelligence corroboration, although no completed sandbox run or host-reputation check is available.
The strongest evidence is the complete absence of malicious or suspicious detections across 75 antivirus engines. Sixteen tier-1 engines reported no detection, including Microsoft, Kaspersky, ESET-NOD32, Avast, and BitDefender. The sample has moderate prevalence, with 420 sources and 478 submissions, yet no family label or curated intelligence hit has emerged. Code signing is not meaningful for this COFF file type, so its unsigned state does not count against it. No runtime observation or complete contacted-host reputation result is available, limiting certainty about execution behavior.
What We Detected
No malicious or suspicious result was recorded across 75 antivirus engines. Sixteen tier-1 products reported no detection, and there is no family consensus, confirmed hacktool label, YARA rule match, MalwareBazaar record, or CIRCL reference hit.
Threat Behavior
No completed sandbox observation is available because behaviour is null. A complete host-reputation cross-check is also unavailable because contactedHosts is null, so no conclusions can be drawn about runtime network activity.
What To Do Now
The static evidence and prevalence history provide strong reassurance. If the file came from an unexpected source or will be linked into a sensitive project, verify its origin and build context before using it, while keeping endpoint protection enabled.
Where this verdict could be wrong3 caveats
- behaviour=null, so no sandbox execution was completed to verify what the file does at runtime.
- contactedHosts=null, meaning no completed host-reputation cross-check is available.
- file.reputation=0 provides no positive reputation signal, despite the sample's moderate prevalence.
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/75 antivirus engines reported a malicious or suspicious result.
- 16 tier-1 engines reported no detection.
- Observed across 420 sources and 478 submissions.
- No MalwareBazaar, YARAify, or CIRCL hit.
- No brand mismatch or fired heuristic was recorded.
- No completed sandbox observation is available.
- No complete contacted-host reputation cross-check is available.
- The file has a neutral reputation score of 0.
Normal handling is reasonable if the file came from an expected development or build source. Verify its origin before linking or executing associated components, and keep endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 420sources 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 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The hash has been submitted 478 times from 420 sources.
ProvenanceDerivedSourceSaved report factsObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Xeno.exp
- Format
- COFF
- Code signing
- Not applicable to this file type
- Size
- 1.2 KB
- Last analyzed
- Sep 14, 2026, 2:45 PM UTC
b29565ca546538917a4017a430e2f6b0254395e7d5d3235395453f88174bd87bSafety & 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
Open it only when its sender or download source is one 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 Xeno.exp safe?
What is Xeno.exp?
How many antivirus engines detected Xeno.exp?
What is the SHA-256 hash of Xeno.exp?
Is it safe to open Xeno.exp?
How up to date is this analysis of Xeno.exp?
Community
Member reviews and reports for this exact file hash.