Is XenoUI.deps.json safe?
No engine detected this small JSON dependency manifest, and its established circulation plus absent external-intelligence matches provide strong benign evidence.
All 75 antivirus engines produced zero malicious or suspicious detections, including the major tier-1 products. The sample is a 2.6 KB JSON dependency manifest seen from 260 sources, with no matching research-intelligence indicators; however, no completed runtime or host-reputation analysis is available.
7d3b114326103db724…9c8a0de9acdccfRecommended 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 produced zero malicious or suspicious detections, including the major tier-1 products. The sample is a 2.6 KB JSON dependency manifest seen from 260 sources, with no matching research-intelligence indicators; however, no completed runtime or host-reputation analysis is available.
The strongest evidence is complete detector agreement: 0 of 75 engines flagged the sample, and 16 tier-1 engines reported no detection. Its JSON format and 2.6 KB size are consistent with a dependency manifest rather than executable code. It has been submitted 300 times from 260 sources, reducing concern that it is an extremely rare, newly encountered artifact. CIRCL, MalwareBazaar, and YARAify supplied no matching intelligence, and no heuristic rule fired. No runtime analysis was completed, and contacted-host reputation was not checked, so those areas cannot provide additional assurance.
What We Detected
No malicious or suspicious detection was returned by any of the 75 antivirus engines. Avast, BitDefender, ESET-NOD32, Kaspersky, Microsoft, and other tier-1 products reported no detection. The file is a 2,610-byte JSON dependency manifest, and code signing is not applicable to this format.
Threat Behavior
No completed sandbox observation is available, so runtime behavior cannot be characterized. No comprehensive contacted-host reputation result is available either. Research-intelligence checks produced no CIRCL, MalwareBazaar, or YARAify match, and the file has appeared in 300 submissions from 260 sources.
What To Do Now
The available static evidence does not indicate harmful content. Keep endpoint protection enabled and obtain the file from the expected application or developer source; if it appeared unexpectedly, inspect the associated executable rather than this dependency manifest alone.
Where this verdict could be wrong3 caveats
- behaviour=null, so the file was not supported by completed runtime observation.
- contactedHosts=null, so no comprehensive host-reputation cross-check is available.
- The community annotation includes a masquerade tag, but it has zero votes and no independent engine or intelligence corroboration.
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 detection.
- 16 tier-1 engines reported no detection.
- No CIRCL, MalwareBazaar, or YARAify match was found.
- The file was submitted 300 times from 260 sources.
- No triggeredHeuristics rule fired.
- No completed runtime observation is available.
- No comprehensive contacted-host reputation cross-check is available.
- One zero-vote community annotation applied a masquerade tag without corroborating evidence.
No remediation is indicated for this JSON manifest based on the available evidence. Keep protection enabled and verify that the accompanying application came from its expected source.
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
- 260sources 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 300 times from 260 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
- XenoUI.deps.json
- Format
- JSON
- Code signing
- Not applicable to this file type
- Size
- 2.5 KB
- Last analyzed
- Sep 14, 2026, 2:43 PM UTC
7d3b114326103db72409dc3d9a2c68c1027121abddfbecf9c69c8a0de9acdccfSafety & 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 XenoUI.deps.json safe?
What is XenoUI.deps.json?
How many antivirus engines detected XenoUI.deps.json?
What is the SHA-256 hash of XenoUI.deps.json?
Is it safe to open XenoUI.deps.json?
How up to date is this analysis of XenoUI.deps.json?
Community
Member reviews and reports for this exact file hash.