easinvoker.exe
Exchange ActiveSync Invoker file version info
Program on Windows 6 known copies with hashes
Is it the real easinvoker.exe?
C:\Windows\system32\6 known copies
10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\easinvoker.exe · signed by Microsoft Windows
5e9d60a425ed50dc587afb886dbceff941f0c7d0d1c597ed5e272b3dcf1032aa10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\easinvoker.exe · signed by Microsoft Windows
4ab78dc788cead8f20227c9e2abfbefd5e74c64c85677c505ae7e694b7d4156510.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\easinvoker.exe · signed by Microsoft Windows
55c243f2c225b8e74a03a97f9f558b4c15cd82f13156327d099061e134eec1ab10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\easinvoker.exe · signed by Microsoft Windows
d6c7259046e76e147e2d0f40329e0605287c80a51e6417babcd4b5d9998949ce10.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\easinvoker.exe · signed by Microsoft Windows
6dc05888d8026acd8ebacdd6a54ad8ad64a49dfd1af9cb8f360089b8362bd0026.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\easinvoker.exe · signed by Microsoft Windows
30951db8bfc21640645aa9144cfeaa294bb7c6980ef236d28552b6f4f3f92a96From 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.