MalwareTips
Threat LensFile scan report

Is Xeno-v1.3.60.exe safe?

Verdict
Suspicious

Single tier-1 detection plus sandbox evidence of process injection and credential access on a newly signed executable.

One tier-1 engine flags Trojan.Siggen33 while 55 engines remain silent. Sandbox shows LSASS access and process injection; the signer has no prior history. Similar imphash files were previously rated suspicious.

Do not run it until verified

Treat as suspicious; do not run without further verification in an isolated environment.

Read the full analysis
Saved file evidenceAntivirus consensus
1of 75 flagged
Flagged 1No detection 74
Digital specimenXeno-v1.3.60.exe4d53875a7fc6f65842…4959770500f5d0
Size84.8 MB
Code signingSigner not verified
SandboxRuntime complete
First seen9d ago
Evidence3 priority signals
1 high-confidence signature or behavior rule matched this file.

Recommended next actions

01

Before running

Do not run it until the source and publisher can be verified independently.

02

If you already ran it

Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

65%Confidence
High
Analyst conclusion

One tier-1 engine flags Trojan.Siggen33 while 55 engines remain silent. Sandbox shows LSASS access and process injection; the signer has no prior history. Similar imphash files were previously rated suspicious.

Where this verdict could be wrong2 caveats
  • contactedHosts.maliciousHosts.length=0 and droppedChildren.hasMaliciousChild=false provide no additional malicious corroboration.
  • engines.onlyLowTrustFlagging=false and 55/75 engines undetected limit the weight of the single tier-1 flag.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Treat as suspicious; do not run without further verification in an isolated environment.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    1 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    3 of 23 contacted hosts were cross-checked; coverage is incomplete.

  • YARA

    Complete

    3 signature or behavior rules matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 33MITRE ATT&CK techniques
  • 15spawned processes
  • 24network contacts
  • 40filesystem & mutex artifacts

What this file does

Observed actions and their security significance

  • High concern: Accessed operating-system credential data, which can expose saved passwords.

  • High concern: Injected code into another process, a technique that can conceal execution.

  • High concern: Encrypted files or data, behaviour commonly associated with ransomware.

  • High concern: Changed an auto-start location that can make code run after sign-in or restart.

  • High concern: Searched files or settings where passwords and keys may be stored.

  • High concern: Accessed browser or password-store data that may contain saved logins.

  • High concern: Manipulated how the operating system loads code, which can redirect execution.

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.

Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & FAQ

Complete recovery guidance and answers for the next decision.

What to do now

We couldn't fully clear this file. Treat it with caution.

  1. Recovery step 01

    Don't run it unless you're certain it came from a source you trust.

  2. Recovery step 02

    Check where you got it — an unexpected attachment or a random download link is a red flag.

  3. Recovery step 03

    If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.

  4. Recovery step 04

    If you're still unsure, scan it again in a day or two — detections often catch up on newer files.

Safety FAQ

Direct answers grounded in the saved verdict and evidence in this report.

9 evidence-based answers
Is Xeno-v1.3.60.exe safe, or is it malware?
Evidence-based answer
Xeno-v1.3.60.exe is suspicious — treat it as unsafe until you're sure. 1 of 75 antivirus engines flag it (family: siggen33); that detection signal contributes to the cautious verdict. Don't run it unless you fully trust where it came from. Get a fresh copy from the developer's official site or an official app store.
What is Xeno-v1.3.60.exe?
Evidence-based answer
Xeno-v1.3.60.exe is a Windows executable program, about 84.8 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
How many antivirus engines detected Xeno-v1.3.60.exe?
Evidence-based answer
1 of 75 antivirus engines flagged Xeno-v1.3.60.exe, 1 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence.
I already downloaded and ran Xeno-v1.3.60.exe — what should I do?
Evidence-based answer
Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
How do I remove Xeno-v1.3.60.exe?
Evidence-based answer
To remove Xeno-v1.3.60.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this file from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
What kind of malware is Xeno-v1.3.60.exe?
Evidence-based answer
Xeno-v1.3.60.exe is classified as a trojan — malware disguised as something harmless to trick you into running it. Engines attribute it to the siggen33 family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
Is Xeno-v1.3.60.exe digitally signed?
Evidence-based answer
Xeno-v1.3.60.exe claims a signer of Rizve A, but the signature is not verified — an unverified or broken signature can be forged, so it should not be trusted as proof of who made the file.
What is the SHA-256 hash of Xeno-v1.3.60.exe?
Evidence-based answer
The SHA-256 hash of Xeno-v1.3.60.exe is 4d53875a7fc6f65842488484d95eae9df10a7ace1e4cebdd6f4959770500f5d0, and its MD5 is b857711f0516ecbd54da4f4c15980d07. 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.
How up to date is this analysis of Xeno-v1.3.60.exe?
Evidence-based answer
This report reflects the scan run on August 15, 2026. Because a file's hash never changes, the identity of Xeno-v1.3.60.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.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Scanned by
lucianLuluYT
Scan another
Check a different file
URL instead?
Check if a link is safe
The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.