breakin.exe
Microsoft Breakpoint forcer file version info
Program on Windows 4 known copies with hashes
Is it the real breakin.exe?
C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\4 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\breakin.exe · signed by Microsoft Windows Kits Publisher
93256e6d43c5bcfe332f31b571ec044b3b3553f894747e9f77b987d0767fbc9010.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\breakin.exe · signed by Microsoft Windows Kits Publisher
93a92739da0cf9e08cf15391a9cf3b4d3aa57dac34a701f11a34db36ee5a158f10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\breakin.exe · signed by Microsoft Corporation
c9566aaec773fbb5d0dcf12c2aab85963979dff085f8a13f03aee95a5b6c033510.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\breakin.exe · signed by Microsoft Corporation
d78fb281572d505d72a337152efdf32b2e10f2a004db4f86ae81c1fc747e0667From 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.