Is Xeno-v1.3.60 (1).zip safe?
No antivirus engine identified malware, while the lone sandbox run exposed potentially offensive techniques that warrant care despite otherwise reassuring evidence.
None of 75 engines flagged this ZIP, and one completed sandbox run produced no malicious sandbox finding. However, runtime telemetry mapped activity to process injection, archive collection, and defense impairment, so obtain the archive from its official source and keep endpoint protection enabled.
f51ca249fde67afae2…89c15fd05ff703Recommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted 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.
None of 75 engines flagged this ZIP, and one completed sandbox run produced no malicious sandbox finding. However, runtime telemetry mapped activity to process injection, archive collection, and defense impairment, so obtain the archive from its official source and keep endpoint protection enabled.
The archive received no malicious or suspicious detections from 75 engines, including no tier-1 detections. One completed sandbox run did not produce a malicious sandbox finding, and its only observed domain was fully checked without a reputation hit. Ten dropped files yielded no known malicious child, although eight lacked definitive cached ratings. The main concern is runtime telemetry mapped to T1055, T1560, and T1562.001, including possible process injection and defense impairment. With no family consensus or external-intelligence match, those behavioral mappings are insufficient to outweigh the broad negative scan evidence, but they justify cautious handling.
What We Detected
None of 75 antivirus engines flagged the ZIP, and 16 tier-1 engines reported no detection. CIRCL, MalwareBazaar, and YARAify supplied no corroborating malware hit or family identification.
Threat Behavior
One completed sandbox run produced no malicious sandbox finding. It nevertheless mapped activity to T1055, T1560, and T1562.001, representing possible process injection, archive collection, and defense impairment. The sole observed domain, assets.msn.com, was covered by the host-reputation check and had no malicious or suspicious cache match. Ten dropped hashes contained no known malicious child, but eight did not have definitive stored ratings.
What To Do Now
Confirm that the archive came from the project's official release channel and scan the extracted files before execution. Keep antivirus and endpoint protection enabled; use an isolated environment if the source cannot be verified.
Where this verdict could be wrong3 caveats
- The runtime mapping includes T1055 process injection, T1560 archive collection, and T1562.001 defense impairment, which are meaningful offensive indicators despite the lack of engine detections.
- Only two of 10 dropped children have definitive cached ratings; the remaining eight have verdict=null, so child-file coverage is incomplete.
- The archive is unsigned by nature because signing.applicable=false, leaving no publisher identity or signer history to validate its origin.
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 engines reported a malicious or suspicious result.
- engines.tier1Malicious=0 and engines.tier1ReportedClean=16.
- behaviour.hasMaliciousSandboxVerdict=false in one completed sandbox.
- contactedHosts inspected the sole observed domain with no malicious or suspicious match.
- No CIRCL, MalwareBazaar, or YARAify hit was present.
- Runtime evidence mapped activity to T1055 process injection.
- Runtime evidence also included T1562.001 defense impairment and T1560 archive collection.
- Eight of 10 dropped child hashes lacked definitive cached verdicts.
- The ZIP format provides no applicable code-signing identity.
Use only a copy obtained from the project's official release channel, then scan the extracted contents before running them. Keep endpoint protection enabled and isolate execution when provenance is uncertain.
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
Complete1 isolated runtime environment contributed observations.
Network
Complete1 contacted host was cross-checked.
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
- 13MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 40filesystem & mutex artifacts
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.
- assets.msn.com
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows Script\Settings\Telemetry\wscript.exe\JScriptSetScriptStateStarted
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\592920c8-7ea2-4e14-a9b6-36c6f5b08973
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\3287cca1-4d1c-4274-a053-e22e194c74cd
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AF9.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER706F.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B2C.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AF9.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER706F.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess3576
- Global\325f1322-2dd2-4ad3-b3f4-1c6c3ae54cf8
- Local\WERReportingForProcess3268
- Global\ed84653c-f20f-4902-9548-dcf767f655d4
- Local\WERReportingForProcess2520
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
- 9d16d62878486d6caad6…4b3a3dClean0/75 enginestrust 84from our cache
- 2a466648affd3d51b944…1fc1b3Never scannednever seen before
- 7d3b114326103db72409…acdccfClean0/75 enginestrust 93from our cache
- 465a7ddfb3a0da4c3965…ea0a6fNever scannednever seen before
- 4fe2c4420294758883e1…62653cNever scannednever seen before
- 43e332faef4019a95d3b…55dad2Never 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
- 0 / 75engines flagged
- 26sources 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
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 33 times from 26 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Xeno-v1.3.60 (1).zip — f51ca249fde67afae202a214e2b6e324dd039d32a17a29428e89c15fd05ff703
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Xeno-v1.3.60/msvcp140.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Xeno-v1.3.60/libcurl.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 592920c8-7ea2-4e14-a9b6-36c6f5b08973 — C:\ProgramData\Microsoft\Windows\WER\Temp\592920c8-7ea2-4e14-a9b6-36c6f5b08973
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: assets.msn.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved 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.
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.60/msvcp140.dll",#1
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-v1.3.60 (1).zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 6.7 MB
- Last analyzed
- Sep 28, 2026, 8:50 PM UTC
f51ca249fde67afae202a214e2b6e324dd039d32a17a29428e89c15fd05ff703Safety & 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 or extract it only when its sender or download source has been independently verified.
- 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-v1.3.60 (1).zip safe?
What is Xeno-v1.3.60 (1).zip?
How many antivirus engines detected Xeno-v1.3.60 (1).zip?
What is the SHA-256 hash of Xeno-v1.3.60 (1).zip?
Is it safe to open or extract Xeno-v1.3.60 (1).zip?
How up to date is this analysis of Xeno-v1.3.60 (1).zip?
Community
Member reviews and reports for this exact file hash.