LogonUI.exe
Windows Logon User Interface Host file version info
Program on Windows 6 known copies with hashes 5 Sigma rules name it
Is it the real LogonUI.exe?
C:\Windows\system32\6 known copies
10.0.22000.120 (WinBuild.160101.0800) · C:\WINDOWS\system32\LogonUI.exe · signed by Microsoft Windows
4a224037f9832d0bbff2d61289f4f9030b72ebd42da90fb343ca94978bfd045910.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\LogonUI.exe · signed by Microsoft Windows
cf01e46c146699f6c0e3dd447043f59bc9438dbbcb9563af6c60ebc6d82727f210.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\LogonUI.exe · signed by Microsoft Windows
630067181fa5b2e7d9e7f50c6cecf3c3e60eea426a7ab0125810e3337e14bae010.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\LogonUI.exe · signed by Microsoft Windows
9358ef8cb7fb08581d74274005263bd8fa2e6e0fc443930b25fd345cf6ce907110.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\LogonUI.exe · signed by Microsoft Windows
aa62d29803d52ec06cd27ed3124e034048f09606eb7342181913c9817c7b44c56.3.9600.17415 (winblue_r4.141028-1500) · C:\windows\system32\LogonUI.exe · not signed
997c0e69c490770815dd64189ad2f59f8309ad266981bfc5d70a728dd174d19cFrom the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.
What detects it
Sigma names LogonUI.exe in 5 rules in all, for every kind of event; these are the process creation rules CmdID evaluates.