Is asyar_0.1.1-47_x64_en-US.msi safe?
No antivirus engine or completed sandbox identified malware activity, although the unsigned, newly observed installer made one direct-IP connection with unresolved reputation.
All 74 antivirus engines reported no detection, including 17 tier-1 engines, and the completed sandbox produced no malicious verdict or offensive behavior. Caution remains appropriate because the installer is unsigned, newly observed, and contacted one IP address whose reputation was not fully checked.
56a12faef2ec6a53dd…92fcc92f68a133Recommended 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 74 antivirus engines reported no detection, including 17 tier-1 engines, and the completed sandbox produced no malicious verdict or offensive behavior. Caution remains appropriate because the installer is unsigned, newly observed, and contacted one IP address whose reputation was not fully checked.
The strongest evidence is the complete absence of detections across 74 antivirus engines, including 17 tier-1 products. One completed sandbox run found no offensive techniques, persistence indicators, malicious child files, or malicious sandbox verdict. The observed system-information and removable-media checks are common contextual activities and do not independently establish harmful intent. However, the installer lacks a digital signature and has only one submission from one source, limiting confidence in its provenance. It also contacted 162.159.36.2 directly, and no complete host-reputation result is available because the contacted-host check was not saved.
What We Detected
None of 74 antivirus engines flagged the MSI, and all 17 reporting tier-1 engines returned no detection. Researcher-curated sources supplied no matching malware family or YARA rules.
Threat Behavior
One completed sandbox run observed installer execution, system-information discovery (T1082), removable-media discovery (T1120), and removable-media interaction (T1091). It found no offensive techniques, persistence indicators, dropped malicious children, or malicious sandbox verdict. The installer contacted 162.159.36.2 directly, but the host-reputation cross-check was not completed or saved, so that endpoint cannot be characterized as benign or malicious.
What To Do Now
Obtain the installer from its official release channel and verify its SHA-256 value, especially because it is unsigned and newly observed. Keep endpoint protection enabled and rescan if the file's source is uncertain or new detections appear.
Where this verdict could be wrong2 caveats
- The Windows Installer is unsigned and was first observed only one day ago from one source, so its origin has not developed an established reputation.
- The sandbox recorded contact with 162.159.36.2 without an application domain; contactedHosts=null prevents a complete reputation assessment of that endpoint.
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/74 antivirus engines reported a detection
- 17 tier-1 engines reported no detection
- One sandbox produced no malicious verdict and no offensive techniques
- No persistence indicators or dropped malicious children were observed
- No CIRCL, MalwareBazaar, or YARAify corroboration
- Unsigned Windows Installer with no verified publisher identity
- Observed for only one day with one submission from one source
- Direct-IP connection to 162.159.36.2 lacks a completed reputation cross-check
Use the MSI only if it came from the project's official release channel and its SHA-256 matches the published value. Keep endpoint protection enabled and avoid installation when the source cannot be verified.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was 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
- 3MITRE ATT&CK techniques
- 3spawned processes
- 1network contacts
- 9filesystem & 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
asyar_0.1.1-47_x64_en-US.msi
56a12faef2ec6a53dd3279092ccc991670ada91a379c07c85392fcc92f68a133
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\asyar_0.1.1-47_x64_en-US.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\System32\msiexec.exe" /i "C:\Users\user\Desktop\asyar_0.1.1-47_x64_en-US.msi"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
MSI7f4b7.tmp
C:\MSI7f4b7.tmp
04Isolated runtime analysis - Written fileObserved
ProgramData
C:\ProgramData
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\MSI7f4b7.tmp
- C:\ProgramData
- C:\ProgramData\Microsoft\Windows\Templates
- C:\Windows\Fonts
- C:\Windows\system32\catroot
- C:\MSI7f4b7.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:6520:304:WilStaging_02
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 / 74engines 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 74 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: asyar_0.1.1-47_x64_en-US.msi — 56a12faef2ec6a53dd3279092ccc991670ada91a379c07c85392fcc92f68a133
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\asyar_0.1.1-47_x64_en-US.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Windows\System32\msiexec.exe" /i "C:\Users\user\Desktop\asyar_0.1.1-47_x64_en-US.msi"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: MSI7f4b7.tmp — C:\MSI7f4b7.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ProgramData — C:\ProgramData
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 162.159.36.2 — 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
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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.
Evidence162.159.36.2
0 of 74 engines flagged this file
View all 74 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
- asyar_0.1.1-47_x64_en-US.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 28.3 MB
- Last analyzed
- Sep 18, 2026, 6:37 PM UTC
56a12faef2ec6a53dd3279092ccc991670ada91a379c07c85392fcc92f68a133Safety & 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 asyar_0.1.1-47_x64_en-US.msi safe?
What is asyar_0.1.1-47_x64_en-US.msi?
How many antivirus engines detected asyar_0.1.1-47_x64_en-US.msi?
What is the SHA-256 hash of asyar_0.1.1-47_x64_en-US.msi?
Is it safe to install asyar_0.1.1-47_x64_en-US.msi?
How up to date is this analysis of asyar_0.1.1-47_x64_en-US.msi?
Community
Member reviews and reports for this exact file hash.