Is eden-uwp_0.29.msix safe?
All 75 antivirus engines avoided flagging this MSIX package, although its unsigned status, recent appearance, and absent runtime evidence warrant source verification.
No antivirus engine flagged the package, including 17 high-trust engines, and external intelligence produced no threat matches. Because it is unsigned, newly observed, and lacks completed runtime analysis, install it only if it came from the expected official release channel.
2bbd30e626f03526d0…a70e724eccd683Recommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed 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.
No antivirus engine flagged the package, including 17 high-trust engines, and external intelligence produced no threat matches. Because it is unsigned, newly observed, and lacks completed runtime analysis, install it only if it came from the expected official release channel.
The strongest evidence is complete agreement across the antivirus network: 0 of 75 engines reported a malicious or suspicious result. Seventeen high-trust engines, including Microsoft, Kaspersky, BitDefender, Avast, and ESET-NOD32, produced no detection. External intelligence added no malware-family, research-rule, or known-bad reference hit. However, the MSIX package has no verified signature and has been submitted only once, so publisher identity and established reputation are absent. No completed sandbox observation or complete contacted-host reputation result is available, leaving runtime activity unverified.
What We Detected
None of the 75 antivirus engines flagged the package, and 17 high-trust engines reported no detection. External checks also returned no MalwareBazaar match, no CIRCL reference, and zero YARAify rules.
Threat Behavior
No completed sandbox run is available, so execution behavior was not observed. Contacted-host reputation was not checked or saved, and therefore no conclusion can be drawn about possible network destinations.
What To Do Now
Confirm that the SHA-256 hash and version match the publisher's official release channel before installation. The package is unsigned and newly observed, so keep endpoint protection enabled and avoid installing it if its origin cannot be verified.
Where this verdict could be wrong3 caveats
- signing.applicable=true and signing.signed=false, so the MSIX package lacks verified publisher attribution.
- prevalence.classification=rare_new records only one source and one submission, limiting reputation history.
- behaviour=null and contactedHosts=null leave runtime activity and contacted-host reputation unassessed.
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.tier1ReportedClean=17 and engines.tier1Malicious=0
- externalIntel.malwareBazaar.hit=false
- externalIntel.yaraify.ruleCount=0
- brandMismatch.detected is not present
- signing.signed=false despite signing.applicable=true
- prevalence.uniqueSources=1 and prevalence.timesSubmitted=1
- behaviour=null, so no completed runtime observation is available
- contactedHosts=null, so no complete host-reputation result is available
Use the package only if its hash and version can be confirmed through the expected official distribution channel. Keep endpoint protection enabled and rescan if publisher verification or newer runtime evidence becomes available.
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
- 1sources 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 1 time from 1 source.
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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- eden-uwp_0.29.msix
- Format
- ZIP
- Code signing
- No verified publisher
- Size
- 12.6 MB
- Last analyzed
- Sep 26, 2026, 4:18 AM UTC
2bbd30e626f03526d07958bee3433879bb13b20f8b749d235aa70e724eccd683Safety & 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
Install it only when it came from the developer's official site or an official app store.
- 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 eden-uwp_0.29.msix safe?
What is eden-uwp_0.29.msix?
How many antivirus engines detected eden-uwp_0.29.msix?
What is the SHA-256 hash of eden-uwp_0.29.msix?
Is it safe to install eden-uwp_0.29.msix?
How up to date is this analysis of eden-uwp_0.29.msix?
Community
Member reviews and reports for this exact file hash.