Repository navigation
Replies: 1 comment
|
I am sorry about this. The problem is that Kiri is not signed for windows. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi!
I recently installed Kiri v0.2.0 on Windows 11 Pro and encountered a Microsoft Defender detection while setting up Kiri's bundled Alpine Linux environment.
The application initially launched without any issues. However, during the WSL/Alpine VM setup, Microsoft Defender quarantined
kiri-win.exe.Detection details
Behavior:Win32/DefenseEvasion.A!ml2147738096%LOCALAPPDATA%\Kiri\kiri-win.exe1.463.288.01.1.26100.4Additional observations
Defender also associated the detection with the following persistence mechanisms:
HKCU\Software\Microsoft\Windows\CurrentVersion\Run\KiriStart Menu\Programs\Kiri.lnkBoth appear consistent with Kiri's documented autostart functionality.
The original MSI was scanned on VirusTotal without any reported detections:
VirusTotal analysis
Its SHA-256 matches the official GitHub v0.2.0 release.
Possible explanation
While reviewing the source, I noticed references to a previous Microsoft Defender false-positive detection in v0.1.7 (
Trojan:Win32/Bearfoos.A!ml), apparently caused by PowerShell execution patterns.I understand that these execution patterns were subsequently changed.
The current detection is different, but I suspect the combination of PowerShell execution, WSL provisioning and autostart registration may be triggering Defender's behavioral detection.
This is only a hypothesis, not a confirmed false positive.
Questions
I have left the executable in quarantine rather than creating a Defender exclusion.
Happy to provide additional Defender event logs or diagnostic details if useful.
Thanks for developing Kiri!
All reactions