Is House 2 demo.exe safe?
No engine detected malware, but this newly observed unsigned executable lacks runtime evidence, established provenance, and a complete contacted-host reputation check.
All 75 engines were free of detections, including 17 tier-1 products, and no external intelligence source identified a threat. However, the executable is unsigned, newly observed, and potentially packed, while no completed sandbox run or host-reputation check is available, so its safety cannot yet be established confidently.
15a0d6ab740409963a…4da83a253ad82eRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
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.
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 engines were free of detections, including 17 tier-1 products, and no external intelligence source identified a threat. However, the executable is unsigned, newly observed, and potentially packed, while no completed sandbox run or host-reputation check is available, so its safety cannot yet be established confidently.
Static scanning produced no malicious or suspicious detections from 75 engines, with all 17 participating tier-1 products silent. No named malware family, research-rule match, known-malware database hit, malicious child, or brand conflict was identified. Against that, the executable has no signature or publisher history and has only one recorded submission. Static PE analysis marks it as potentially packed, although code entropy is not high and no section is independently marked suspicious. No completed runtime observation exists, and contacted-host reputation was not checked or retained. The evidence therefore favors a benign explanation but leaves meaningful uncertainty around a brand-new executable with unverified provenance.
What We Detected
None of the 75 antivirus engines flagged the executable, and 17 tier-1 engines reported no detection. External checks also produced no known-malware database hit, no CIRCL reference, and no YARAify rules. No malware family can be assigned from the available evidence.
Threat Behavior
No completed sandbox observation is available, so execution behavior, persistence, process activity, and network communications were not observed. A complete contacted-host reputation result is also unavailable. Static PE analysis labels the file as potentially packed, but it does not show high-entropy code or suspicious sections.
What To Do Now
Confirm that the file came directly from the developer's official release channel and compare its SHA-256 hash with a publisher-provided value if one exists. Keep endpoint protection enabled and avoid running the executable on an important system until its origin is verified or a completed sandbox analysis becomes available.
Where this verdict could be wrong3 caveats
- The complete 0/75 detection result, including 17 tier-1 engines without detections, weighs strongly against known malware.
- MalwareBazaar returned no hit and YARAify returned 0 matching rules, although absence of a database or rule match cannot establish benignness.
- All five similarHashes entries were previously marked suspicious, but matchKind=filetype is too broad to establish meaningful binary similarity.
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 antivirus engines reported a detection
- 17 tier-1 engines reported no detection
- No YARAify, MalwareBazaar, or CIRCL hit
- peAnalysis.highEntropyCode=false
- No brand mismatch or triggered heuristic
- Unsigned Windows executable with no verified publisher
- Only 1 submitter and 1 recorded submission
- First observed on the analysis date
- peAnalysis.likelyPacked=true
- No completed runtime observation
- No complete contacted-host reputation result
Verify the download source and hash before execution, and keep endpoint protection enabled. If provenance cannot be confirmed, wait for a completed sandbox analysis or test it only in an isolated disposable environment.
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.
ProvenanceObservedSourceAntivirus analysisObserved at - 02
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
Section entropy & packers
A known packer signature (UPX / Themida / VMProtect / etc.) matched this file. Packers aren't malicious on their own, but most malware uses them.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
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
- House 2 demo.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 36.0 MB
- Last analyzed
- Oct 1, 2026, 5:18 PM UTC
15a0d6ab740409963a0b3993bca74f5d430017e22c903a20974da83a253ad82eSafety & 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 run 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 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.
- 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 House 2 demo.exe safe, or is it malware?
What is House 2 demo.exe?
How many antivirus engines detected House 2 demo.exe?
What should I do if I already ran House 2 demo.exe?
How do I remove House 2 demo.exe?
What is the SHA-256 hash of House 2 demo.exe?
How up to date is this analysis of House 2 demo.exe?
Community
Member reviews and reports for this exact file hash.