Is Horror Night 1.20.1.zip safe?
Zero detections across 75 engines and benign sandbox behaviour on a newly submitted ZIP archive.
No engine flagged the file. Sandbox activity was limited to system-info discovery and Windows error reporting. Four of five similar ZIP files previously received safe verdicts.
8d9efde0fd7ae5e795…592bb7385f999eRecommended 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.
No engine flagged the file. Sandbox activity was limited to system-info discovery and Windows error reporting. Four of five similar ZIP files previously received safe verdicts.
The file triggered no malicious detections from any of the 75 engines, including 17 tier-1 engines. Sandbox execution produced only ambient system queries and no offensive MITRE techniques. While the file is rare and newly observed, prior ZIP archives with the same matchKind have consistently been classified safe. The single heuristic that fired notes that direct-IP traffic can occur in legitimate installers, so it does not override the clean engine consensus.
What We Detected
75 engines scanned the ZIP; none returned a malicious or suspicious result. Sandbox execution recorded two direct-no complete contacted-host reputation result was available system queries (T1082) but no malicious indicators.
Threat Behavior
No dropped malicious children, no persistence mechanisms, and no C2 domains were observed. The heuristic warning about direct-IP traffic is noted but does not constitute a confirmed malicious signal without host-reputation data.
What To Do Now
The archive can be treated as clean for normal use. Continue to keep endpoint protection enabled when handling any newly submitted or rare files.
Where this verdict could be wrong1 caveat
- contactedHosts is null — no complete host-reputation result available for the two direct-IP addresses observed in behaviour.contactedIps.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero malicious detections across 75 engines
- Sandbox verdict clean
- Four prior similar ZIP files classified safe
The file shows no malicious indicators and can be considered safe to open, provided standard endpoint protection remains active.
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
Partial2 runtime contacts were observed without a completed reputation cross-check.
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
- 1MITRE ATT&CK techniques
- 2spawned processes
- 2network contacts
- 5filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
Horror Night 1.20.1.zip
8d9efde0fd7ae5e7952d160347643af206702251d6c692faf0592bb7385f999e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" "C:\Users\<USER>\AppData\Local\Temp\modlist.html"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 5064 -s 3768
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
78c76c95-e452-4d20-9cd9-8f74be765ded
C:\ProgramData\Microsoft\Windows\WER\Temp\78c76c95-e452-4d20-9cd9-8f74be765ded
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
150.171.109.114
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
150.171.74.13
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
- 150.171.109.114
- 150.171.74.13
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\78c76c95-e452-4d20-9cd9-8f74be765ded
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\0afc9114-2c4d-4eea-a5f7-cb91468f1324
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- c68afb7490db83943664…51f5deNever scannednever seen before
- a64be6681fb442371091…ba9e2cNever scannednever seen before
- b288d01cb72a4242be98…697c84Never scannednever seen before
- 609e34908b1bd8dcb070…306b27Never 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
- 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
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Horror Night 1.20.1.zip — 8d9efde0fd7ae5e7952d160347643af206702251d6c692faf0592bb7385f999e
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" "C:\Users\<USER>\AppData\Local\Temp\modlist.html"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\WerFault.exe -u -p 5064 -s 3768
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 78c76c95-e452-4d20-9cd9-8f74be765ded — C:\ProgramData\Microsoft\Windows\WER\Temp\78c76c95-e452-4d20-9cd9-8f74be765ded
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 150.171.109.114 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.74.13 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence150.171.109.114 · 150.171.74.13
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
- Horror Night 1.20.1.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 7.0 MB
- Last analyzed
- Aug 26, 2026, 10:45 PM UTC
8d9efde0fd7ae5e7952d160347643af206702251d6c692faf0592bb7385f999eSafety & 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 Horror Night 1.20.1.zip safe?
What is Horror Night 1.20.1.zip?
How many antivirus engines detected Horror Night 1.20.1.zip?
What is the SHA-256 hash of Horror Night 1.20.1.zip?
Is it safe to open or extract Horror Night 1.20.1.zip?
How up to date is this analysis of Horror Night 1.20.1.zip?
Community
Member reviews and reports for this exact file hash.