Is Windose.exe safe?
Safe file assessment
The hash has a long, established submission history across 1,330 sources.
aec7b713a9d3ed7302…64661dc85aae51Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 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
- 7MITRE ATT&CK techniques
- 15spawned processes
- 20network contacts
- 3filesystem & 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
Windose.exe
aec7b713a9d3ed73029d7aeadb351ab13c57ee3d8a8a40429a64661dc85aae51
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\Windose.exe
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\aec7b713a9d3ed73029d7aeadb351ab13c57ee3d8a8a40429a64661dc85aae51.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.67
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
20.99.186.246
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- 192.168.0.67
- 20.99.186.246
- 23.192.210.9
- 20.99.133.109
- 23.216.81.152
- 131.253.33.203
- 20.69.140.28
- 192.168.0.48
- 23.197.238.105
- 23.219.78.68
- %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache\IE\KLT1I0ZU\update50[1].xml
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
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
- 1 / 74engines flagged
- 1,330sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The hash has a long, established submission history across 1,330 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 02
1 of 74 antivirus engines flagged the file, including Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1,587 times from 1,330 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Windose.exe — aec7b713a9d3ed73029d7aeadb351ab13c57ee3d8a8a40429a64661dc85aae51
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\Windose.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\aec7b713a9d3ed73029d7aeadb351ab13c57ee3d8a8a40429a64661dc85aae51.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 192.168.0.67 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 20.99.186.246 — 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.
Evidence20.99.186.246 · 23.192.210.9 · 20.99.133.109
1 of 74 engines flagged this file
View all 74 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Windose.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 651.0 KB
- Last analyzed
- Jul 4, 2026, 9:03 AM UTC
aec7b713a9d3ed73029d7aeadb351ab13c57ee3d8a8a40429a64661dc85aae51Safety & 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
Run it only when it came from the developer's official site or another source 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 Windose.exe safe?
What is Windose.exe?
How many antivirus engines detected Windose.exe?
What is the SHA-256 hash of Windose.exe?
Is it safe to run Windose.exe?
How up to date is this analysis of Windose.exe?
Community
Member reviews and reports for this exact file hash.