Is azahar-windows-mxe-2126.1.2-installer.exe safe?
No engine detected this widely submitted installer, and its completed sandbox run produced no malicious verdict or confirmed harmful child.
All 75 antivirus engines were free of detections, including 15 tier-1 engines that reported no threat. One sandbox run found mostly installer-common activity and no malicious verdict, though the executable is unsigned and its four extracted children remain unclassified.
87da5b51d11976268e…31d5fa71b43da5Recommended 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.
All 75 antivirus engines were free of detections, including 15 tier-1 engines that reported no threat. One sandbox run found mostly installer-common activity and no malicious verdict, though the executable is unsigned and its four extracted children remain unclassified.
No engine detected malware or suspicious content among 75 engines, and 15 tier-1 products reported no detection. The file also accumulated 165 submissions from 159 sources in two days, indicating broad early circulation. One completed sandbox run mapped mostly ambient techniques and produced no malicious verdict, while T1134 was the sole offensive technique. None of four inspected children was identified as harmful, but all four remain unclassified rather than confirmed benign. The unsigned status limits publisher assurance, yet there is no family consensus, malicious external-intelligence match, brand conflict, packing indicator, or corroborating runtime evidence.
What We Detected
None of 75 antivirus engines flagged the executable, including 15 tier-1 engines that reported no detection. It has also received 165 submissions from 159 sources within two days, which supports broad distribution rather than an isolated upload. No malware family was identified, and researcher intelligence returned no matching YARA rules or known-malware record.
Threat Behavior
One completed sandbox run produced no malicious verdict. Most mapped techniques were common to installers or general Windows programs; T1134, associated with access-token operations, was the only offensive technique and lacks corroborating malicious activity. Four extracted files were inspected without a harmful finding, although their individual status remains unknown. No network contacts were observed during that run, and no separate complete host-reputation result is available.
What To Do Now
The main limitation is that the executable is unsigned, so its publisher cannot be cryptographically verified. Obtain it from the project's official release channel, confirm the SHA-256 value 87da5b51d11976268ec8cd9cd0079b69ac265766a82e793ec731d5fa71b43da5, and keep endpoint protection enabled during installation.
Where this verdict could be wrong4 caveats
- signing.signed=false for a Win32 executable, so no verified publisher identity is available.
- T1134 appeared in the completed sandbox run; token manipulation can be security-sensitive, although no malicious sandbox verdict corroborated it.
- droppedChildren.rollup reports 4 unknown child verdicts, so their absence from the malicious count is not equivalent to confirmed benign status.
- contactedHosts=null, meaning no complete host-reputation cross-check is available; the sandbox itself recorded no contacted domains, IPs, or URLs.
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 malicious or suspicious result.
- 15 tier-1 engines reported no detection and tier1Malicious=0.
- One completed sandbox produced no malicious verdict.
- No inspected child was identified as malicious.
- No YARAify, MalwareBazaar, or CIRCL malicious match was present.
- The Win32 executable is unsigned and has no verified publisher identity.
- Sandbox behavior included T1134 token manipulation.
- All four extracted child files remain individually unclassified.
- The file was first observed only two days ago.
- No complete contacted-host reputation cross-check is available.
Use the installer only if its SHA-256 matches the value published through the project's official release channel. Keep antivirus and endpoint protection enabled, especially because the executable lacks a digital signature.
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
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 flight recorder
Capture complete- 1isolated sandbox run
- 16MITRE ATT&CK techniques
- 1spawned processes
- 0network contacts
- 12filesystem & 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
azahar-windows-mxe-2126.1.2-installer.exe
87da5b51d11976268ec8cd9cd0079b69ac265766a82e793ec731d5fa71b43da5
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\azahar-windows-mxe-2126.1.2-installer.exe"
02Isolated runtime analysis
Files
Created or changed
- Written fileObserved
Caches
C:\Users\user\AppData\Local\Microsoft\Windows\Caches
03Isolated runtime analysis - Written fileObserved
Temp
C:\Users\user\AppData\Local\Temp
04Isolated runtime analysis - +1 more recorded observation in Analyst mode
4 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.
- C:\Users\user\AppData\Local\Microsoft\Windows\Caches
- C:\Users\user\AppData\Local\Temp
- C:\Users\user\AppData\Local\Temp\
- C:\Users\user\AppData\Local\Temp\nsk9D3E.tmp
- C:\Users\user\AppData\Local\Temp\nslB7DD.tmp
- C:\Users\user\AppData\Local\Temp\nsk9D3E.tmp
- C:\Users\user\AppData\Local\Temp\nslB7DD.tmp
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 29550e1cc3b7f32762b1…d11504Never scannednever seen before
- f14fdfe7ee49dfea1fec…f88452Never scannednever seen before
- 417cdcc0e5ff109973fb…f5edacNever scannednever seen before
- 3ad2dc318056d0a2024a…056cf2Never 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
- 0 / 75engines flagged
- 159sources 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 165 times from 159 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: azahar-windows-mxe-2126.1.2-installer.exe — 87da5b51d11976268ec8cd9cd0079b69ac265766a82e793ec731d5fa71b43da5
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\user\Desktop\azahar-windows-mxe-2126.1.2-installer.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
File written: Caches — C:\Users\user\AppData\Local\Microsoft\Windows\Caches
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Temp — C:\Users\user\AppData\Local\Temp
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.
0 of 75 engines flagged this file
View all 75 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- azahar-windows-mxe-2126.1.2-installer.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 45.9 MB
- Last analyzed
- Sep 23, 2026, 8:12 AM UTC
87da5b51d11976268ec8cd9cd0079b69ac265766a82e793ec731d5fa71b43da5Safety & 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 azahar-windows-mxe-2126.1.2-installer.exe safe?
What is azahar-windows-mxe-2126.1.2-installer.exe?
How many antivirus engines detected azahar-windows-mxe-2126.1.2-installer.exe?
What is the SHA-256 hash of azahar-windows-mxe-2126.1.2-installer.exe?
Is it safe to install azahar-windows-mxe-2126.1.2-installer.exe?
How up to date is this analysis of azahar-windows-mxe-2126.1.2-installer.exe?
Community
Member reviews and reports for this exact file hash.