Is maid-mansion-win_demo.zip safe?
Only Jiangmin flagged this archive with a generic label; 18 tier-one engines, sandbox results, and independent intelligence supplied no corroborating malware evidence.
Only 1 of 78 engines detected the archive, and that detection came from Jiangmin with a generic label; all 18 tier-one engines were silent. One completed sandbox run produced no malicious verdict, while independent intelligence found no matching threat indicators, making the lone alert highly likely to be a false positive.
0017489260832fe49d…58c1d3e5a3b970Recommended 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.
Only 1 of 78 engines detected the archive, and that detection came from Jiangmin with a generic label; all 18 tier-one engines were silent. One completed sandbox run produced no malicious verdict, while independent intelligence found no matching threat indicators, making the lone alert highly likely to be a false positive.
The scan shows a single generic detection among 78 engines, with no high-trust engine flagging the archive. All 18 reporting tier-one engines found no threat, which substantially weakens Jiangmin's isolated Trojan.Generic.hpekt label. One completed sandbox run recorded two potentially offensive technique mappings, T1486 and T1562.001, but did not produce a malicious sandbox verdict or persistence indicators. Ten dropped children were checked without a malicious child being identified, although their individual verdicts remain unresolved. External intelligence supplied no YARA, known-malware, or reference-database hit, and no complete contacted-host reputation result was available.
What We Detected
Only 1 of 78 engines flagged the archive. Jiangmin, a low-trust detector in this result, reported the generic label Trojan.Generic.hpekt; all 18 reporting tier-one engines supplied no detection, and there was no family consensus.
Threat Behavior
One completed sandbox run mapped T1486 and T1562.001 alongside 13 more common techniques, but it produced no malicious sandbox verdict and found no persistence indicators. Ten extracted children were inspected without identifying a malicious child, though their individual verdicts remained unknown. The archive contacted Microsoft-related infrastructure, but the saved host-reputation check did not cover every recorded domain, IP, and URL, so it cannot establish fully benign networking.
What To Do Now
The evidence strongly favors an isolated false positive. Obtain the archive from its original developer or an established distribution page, verify its SHA-256 value as 0017489260832fe49d63cf37bd5efa23c96e72bfaf70e9e72c58c1d3e5a3b970, keep endpoint protection enabled, and rescan after extraction if source authenticity is uncertain.
Where this verdict could be wrong4 caveats
- behaviour.offensiveTechniques includes T1486 and T1562.001, which can indicate impact or defense impairment, but the sandbox produced no malicious verdict and the broader activity was predominantly ambient.
- Jiangmin labeled the archive Trojan.Generic.hpekt, but this is one generic low-trust detection without tier-1 or external-intelligence corroboration.
- All 10 inspected dropped children have unknown individual verdicts, so droppedChildren.hasMaliciousChild=false does not establish that every extracted file is benign.
- Host-reputation coverage is incomplete because contactedHosts.inspected=2 does not cover every domain, IP, and URL recorded under behaviour.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1/78 engines detected the archive.
- engines.tier1Malicious=0 and engines.tier1ReportedClean=18.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- YARAify, MalwareBazaar, and CIRCL returned no hits.
- Jiangmin reports Trojan.Generic.hpekt.
- Sandbox mappings include T1486 and T1562.001.
- The ZIP contains executable content.
- All 10 inspected child files retain unknown individual verdicts.
- Host-reputation coverage does not include every observed network indicator.
Use the archive only if it came from the original developer or a trusted storefront, and verify the SHA-256 hash before opening it. Keep endpoint protection enabled and rescan the extracted contents.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 78 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 5 contacted hosts were cross-checked; coverage is incomplete.
YARA
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 flight recorder
Capture complete- 1isolated sandbox run
- 15MITRE ATT&CK techniques
- 15spawned processes
- 6network contacts
- 39filesystem & 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.
- download.windowsupdate.com
- ax-0001.ax-msedge.net
- 204.79.197.203
- 23.40.205.81
- 8.8.8.8
- http://download.windowsupdate.com/d/msdownload/update/others/2015/05/17930914_a3b333eff1f0428f5a2c87724c542504821cdbd8.cab
- \REGISTRY\A\{0588598d-3853-3c49-54d8-575d7bbf918f}\Root\InventoryApplicationFile\WritePermissionsCheck
- \REGISTRY\A\{0588598d-3853-3c49-54d8-575d7bbf918f}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\ProgramId
- \REGISTRY\A\{0588598d-3853-3c49-54d8-575d7bbf918f}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\FileId
- \REGISTRY\A\{0588598d-3853-3c49-54d8-575d7bbf918f}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\LowerCaseLongPath
- \REGISTRY\A\{0588598d-3853-3c49-54d8-575d7bbf918f}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\LongPathHash
- \REGISTRY\A\{0588598d-3853-3c49-54d8-575d7bbf918f}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\Name
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\__pycache__\__init__.cpython-39.pyc.78155568
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\__pycache__\__init__.cpython-39.pyc
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\compat\__pycache__\__init__.cpython-39.pyc.84309776
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\compat\__pycache__\__init__.cpython-39.pyc
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\compat\__pycache__\pickle.cpython-39.pyc.87951600
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\__pycache__\__init__.cpython-39.pyc.78155568
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\compat\__pycache__\__init__.cpython-39.pyc.84309776
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\compat\__pycache__\pickle.cpython-39.pyc.87951600
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\__pycache__\vc_version.cpython-39.pyc.88316304
- C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\__pycache__\bootstrap.cpython-39.pyc.88593712
- Local\WERReportingForProcess1800
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\84959d63-8fdf-4321-bb7c-7d24a9be2259
- Local\WERReportingForProcess4744
- Global\f0a84ee8-8f08-42f3-849b-b03d5bb72872
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- ec00853d0ca064fc81e0…460579Never scannednever seen before
- 84608d246475b746327d…a2ca0bNever scannednever seen before
- c13dfa8235e8517ae79e…0d3942Never scannednever seen before
- 56b51b8d868dda9c10ee…805387Never scannednever seen before
- 7ad40c2edc7e44438ab8…68994aNever scannednever seen before
- 0cd04fb0490b7126c7fb…45a25eNever scannednever seen before
- be6a43454bf10c765e34…9c3c38Never scannednever seen before
- 8a91bd6acf7936084605…f046b4Never scannednever seen before
- 7fc36fd081021d228c2c…dd4d29Never scannednever seen before
- d70441d844921df0c540…022a97Never 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.
- 0rule hits recorded
- 1 / 78engines flagged
- 8sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 78 antivirus engines flagged the file, including Jiangmin.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 9 times from 8 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: maid-mansion-win_demo.zip — 0017489260832fe49d63cf37bd5efa23c96e72bfaf70e9e72c58c1d3e5a3b970
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win/Maid_Mansion.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: __init__.cpython-39.pyc.78155568 — C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\__pycache__\__init__.cpython-39.pyc.78155568
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: __init__.cpython-39.pyc — C:\Users\<USER>\AppData\Local\Temp\Maid_Mansion-demo-1.0.6-win\renpy\__pycache__\__init__.cpython-39.pyc
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: download.windowsupdate.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: ax-0001.ax-msedge.net — 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
1 of 78 engines flagged this file
View all 78 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
- maid-mansion-win_demo.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 100.5 MB
- Last analyzed
- Oct 3, 2026, 10:34 PM UTC
0017489260832fe49d63cf37bd5efa23c96e72bfaf70e9e72c58c1d3e5a3b970Safety & 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 maid-mansion-win_demo.zip safe?
What is maid-mansion-win_demo.zip?
How many antivirus engines detected maid-mansion-win_demo.zip?
What is the SHA-256 hash of maid-mansion-win_demo.zip?
Is it safe to open or extract maid-mansion-win_demo.zip?
How up to date is this analysis of maid-mansion-win_demo.zip?
Community
Member reviews and reports for this exact file hash.
