Is yabasanshiro-1.20.46-9a0c56.msi safe?
Only one low-trust engine raised a generic alert, but the unsigned installer’s T1055 and LSASS-related runtime indicators warrant caution pending source verification.
The antivirus pattern strongly favors a false positive: only 1 of 74 engines flagged the installer, no tier-1 engine agreed, and no external intelligence identified it. However, the unsigned package produced a T1055 mapping and LSASS-related heuristic during one sandbox run, so those unresolved runtime indicators justify caution.
4256488ec6a6680195…03444256f4dd48Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
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.
The antivirus pattern strongly favors a false positive: only 1 of 74 engines flagged the installer, no tier-1 engine agreed, and no external intelligence identified it. However, the unsigned package produced a T1055 mapping and LSASS-related heuristic during one sandbox run, so those unresolved runtime indicators justify caution.
Antiy-AVL was the only detector among 74 engines, using the generic label Trojan/Win32.Agent; all 17 reporting tier-1 engines were clean. That low-trust-only pattern ordinarily indicates a false positive, and no known family was corroborated by YARAify, CIRCL, or MalwareBazaar. One completed sandbox did not assign a malicious result, but its evidence mapped activity to T1055 and generated an LSASS-related credential-dumping heuristic. Those runtime signals are not independently confirmed and may reflect process-list context rather than proven injection or memory access. The MSI is also unsigned and lacks signer history, removing a useful publisher-authentication safeguard. Overall, the evidence leans benign but retains enough unresolved behavioral risk to require source and hash verification before execution.
What We Detected
Only 1 of 74 antivirus engines flagged the MSI. The alert came from Antiy-AVL, a low-trust detector, and used the generic label Trojan/Win32.Agent; no tier-1 engine detected it and no engine consensus identified a malware family. YARAify, CIRCL, and MalwareBazaar provided no corroborating hit.
Threat Behavior
One completed sandbox run did not produce a malicious sandbox result. However, the saved evidence mapped activity to MITRE T1055 and generated an LSASS-related credential-dumping heuristic. These records do not prove that process injection or LSASS memory reading actually occurred, but they are meaningful enough to prevent treating the single engine alert as conclusively false. Host-reputation coverage was incomplete because the observed domain was inspected but the separately listed IP was not fully accounted for.
What To Do Now
Verify SHA-256 4256488ec6a66801952712ec1e6e5e6d335e07e5e74b73ae1203444256f4dd48 against the project's official release channel before installation. Keep endpoint protection enabled, and if provenance cannot be confirmed, avoid running the package or test it only in an isolated environment.
Where this verdict could be wrong3 caveats
- The sole detection is Antiy-AVL's generic 'Trojan/Win32.Agent' label, and all 17 reporting tier-1 engines were clean.
- The completed sandbox assigned a clean result, although the recorded T1055 and LSASS-related indicators remain unresolved.
- No YARAify, CIRCL, or MalwareBazaar hit corroborates a known malware family.
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 of 74 engines detected the file, and that detector was low-trust
- All 17 reporting tier-1 engines were clean
- The completed sandbox did not assign a malicious result
- No YARAify, CIRCL, or MalwareBazaar corroboration
- No malicious dropped child was recorded
- Unsigned Windows Installer with no verified publisher or signer history
- MITRE T1055 appeared in the saved runtime evidence
- LSASS-related activity triggered MalwareTips.Synth.CredentialDumper
- Only moderate circulation: 8 submitters and 8 submissions
- Host-reputation inspection did not clearly cover every observed domain and IP
Download this MSI only from the project's official release channel and verify its SHA-256 before use. Keep endpoint protection enabled and avoid execution if the source or hash cannot be confirmed.
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
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules 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
- 5MITRE ATT&CK techniques
- 9spawned processes
- 2network contacts
- 7filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used removable-media replication behaviour that can spread files between devices.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Connected to 2 servers during sandbox analysis.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
yabasanshiro-1.20.46-9a0c56.msi
4256488ec6a66801952712ec1e6e5e6d335e07e5e74b73ae1203444256f4dd48
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\yabasanshiro-1.20.46-9a0c56.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
MSIbbf7f.tmp
C:\MSIbbf7f.tmp
04Isolated runtime analysis - Written fileObserved
Fonts
C:\Windows\Fonts
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a1672.dscr.akamai.net
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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.
- a1672.dscr.akamai.net
- 162.159.36.2
- C:\MSIbbf7f.tmp
- C:\Windows\Fonts
- C:\Windows\system32\catroot
- C:\Windows\system32\catroot2
- C:\MSIbbf7f.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:2336: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.
- 2rule hits recorded
- 1 / 74engines 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 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 74 antivirus engines flagged the file, including Antiy-AVL.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 8 times from 8 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: yabasanshiro-1.20.46-9a0c56.msi — 4256488ec6a66801952712ec1e6e5e6d335e07e5e74b73ae1203444256f4dd48
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\yabasanshiro-1.20.46-9a0c56.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: MSIbbf7f.tmp — C:\MSIbbf7f.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Fonts — C:\Windows\Fonts
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a1672.dscr.akamai.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
1 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- yabasanshiro-1.20.46-9a0c56.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 88.6 MB
- Last analyzed
- Oct 2, 2026, 10:55 PM UTC
4256488ec6a66801952712ec1e6e5e6d335e07e5e74b73ae1203444256f4dd48Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't install it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Download a fresh installer from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is yabasanshiro-1.20.46-9a0c56.msi safe, or is it malware?
What is yabasanshiro-1.20.46-9a0c56.msi?
How many antivirus engines detected yabasanshiro-1.20.46-9a0c56.msi?
What should I do if I already installed yabasanshiro-1.20.46-9a0c56.msi?
How do I remove yabasanshiro-1.20.46-9a0c56.msi?
What is the SHA-256 hash of yabasanshiro-1.20.46-9a0c56.msi?
How up to date is this analysis of yabasanshiro-1.20.46-9a0c56.msi?
Community
Member reviews and reports for this exact file hash.
