Is Xeno-v1.3.55.zip safe?
ZIP archive flagged by two tier-1 engines as adware/PUA with process-injection behaviour observed in one sandbox but no malicious verdict.
Six of 74 engines flagged the sample, two of them tier-1, all pointing to adware or PUA rather than a named malware family. Sandbox execution showed process-injection activity but returned no malicious verdict and no malicious child files or host contacts were confirmed.
1c289425268302a153…a0a793a7adb658Recommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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.
Six of 74 engines flagged the sample, two of them tier-1, all pointing to adware or PUA rather than a named malware family. Sandbox execution showed process-injection activity but returned no malicious verdict and no malicious child files or host contacts were confirmed.
The file is a portable ZIP containing multiple PE modules that triggered adware labels from DrWeb and Sophos. While two tier-1 engines agree on the PUA classification, the family consensus is weak and the remaining 68 engines are silent. Runtime evidence maps to MITRE T1055 but the sandbox did not classify the behaviour as malicious, and no dropped children or contacted hosts carry known-bad reputations.
What We Detected
Two tier-1 engines (DrWeb, Sophos) and four additional engines labelled the archive or its contents as adware or a potentially-unwanted application. The dominant labels reference Downware / ABApplication families. Sandbox execution extracted several DLLs and invoked them via rundll32, mapping to MITRE T1055, T1560 and T1562.001, yet the sandbox itself returned no malicious verdict.
Threat Behavior
The archive behaves like a self-extracting portable application. Extracted modules are loaded at runtime, which is common for legitimate portable software but also for adware bundles. No persistence mechanisms, registry changes or external host contacts were recorded, and none of the ten dropped children have been previously classified malicious.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If the archive is not required, delete it. Should you need the software, obtain it from the vendor’s official site and verify the digital signature of any executables before execution.
Where this verdict could be wrong2 caveats
- If the two tier-1 detections represent independent high-trust votes on adware, the file could be borderline malicious; however tier1FamilyConsensus.strong=false and only one engine agrees on the family, weakening that signal.
- Process-injection mapping (T1055) via rundll32 on extracted DLLs could indicate malicious behaviour, but the sandbox produced no malicious verdict and the activity matches common installer or portable-app extraction patterns.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 68 of 74 engines report clean
- No malicious sandbox verdict
- No malicious dropped children
- Widely submitted (common_new)
- Two tier-1 engines flag adware/PUA
- Process-injection techniques observed in sandbox
- Contains multiple PE files inside archive
Treat as potentially unwanted; scan any extracted executables and avoid running unknown modules.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete6 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 17MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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.
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
Xeno-v1.3.55.zip
1c289425268302a153c03e144c0ee13fcbbac0081780f68db6a0a793a7adb658
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Xeno-v1.3.55/Microsoft.Web.WebView2.Core.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Xeno-v1.3.55/Microsoft.Web.WebView2.WinForms.dll",#1
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
03f4c5c5-0375-4b53-8ac7-ed0d2831bff3
C:\ProgramData\Microsoft\Windows\WER\Temp\03f4c5c5-0375-4b53-8ac7-ed0d2831bff3
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
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.
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\03f4c5c5-0375-4b53-8ac7-ed0d2831bff3
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\f30e55b6-0ac0-4ef9-9914-8ce19ca19c96
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER9423.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF94.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B7.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER9423.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF94.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess3648
- Global\b5fe0bd8-6f62-45d1-a933-c9fa68f1a8aa
- Local\WERReportingForProcess540
- Global\ff71db28-bf4e-4889-8c27-edbe212b9c4b
- Local\WERReportingForProcess5884
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- f7c6c7ea22edd2f8bd07…f91dc1Never scannednever seen before
- 2a466648affd3d51b944…1fc1b3Never scannednever seen before
- 465a7ddfb3a0da4c3965…ea0a6fNever scannednever seen before
- 4fe2c4420294758883e1…62653cNever scannednever seen before
- 43e332faef4019a95d3b…55dad2Never scannednever seen before
- 7125b2f8f8753ad2770f…5da6a9Never scannednever seen before
- 2a005904a24a22d69a56…e91439Never scannednever seen before
- 615824c59ed1e07f5924…839451Never scannednever seen before
- 84425efa675012d33433…6803d3Never scannednever seen before
- 51541ec6684b43157a85…01318dNever scannednever seen before
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
- 6 / 74engines flagged
- 2,734sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
6 of 74 antivirus engines flagged the file, including DrWeb and Google.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 3,850 times from 2,734 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Xeno-v1.3.55.zip — 1c289425268302a153c03e144c0ee13fcbbac0081780f68db6a0a793a7adb658
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Xeno-v1.3.55/Microsoft.Web.WebView2.Core.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Xeno-v1.3.55/Microsoft.Web.WebView2.WinForms.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 03f4c5c5-0375-4b53-8ac7-ed0d2831bff3 — C:\ProgramData\Microsoft\Windows\WER\Temp\03f4c5c5-0375-4b53-8ac7-ed0d2831bff3
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Xeno-v1.3.55/Microsoft.Web.WebView2.Core.dll",#1
6 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- Xeno-v1.3.55.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 6.8 MB
- Last analyzed
- Jul 27, 2026, 1:33 PM UTC
1c289425268302a153c03e144c0ee13fcbbac0081780f68db6a0a793a7adb658Safety & 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.
- Recovery step 01
Don't open or extract it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- 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.
Is Xeno-v1.3.55.zip safe, or is it malware?
What is Xeno-v1.3.55.zip?
How many antivirus engines detected Xeno-v1.3.55.zip?
What should I do if I already opened or extracted Xeno-v1.3.55.zip?
How do I remove Xeno-v1.3.55.zip?
What kind of malware is Xeno-v1.3.55.zip?
What is the SHA-256 hash of Xeno-v1.3.55.zip?
How up to date is this analysis of Xeno-v1.3.55.zip?
Community
Member reviews and reports for this exact file hash.