Process protection challenges-no HOOK, no KDOM, Microsoft Standard Functions

Some people criticized 360 for self-protection, and some people in China, such as Jiangmin and weidian, used a lot of hooks to protect their processes, which not only led to system instability, but also failed to protect them.

Put some little things out for fun. POC-level, no HOOK, no DKOM, No undisclosed data structures or calls modified, completely Microsoft's standard interfaces and functions, but let countless processes end. The ARK tool sighs. Haha!

Download challenge site and test procedure:

Http://www.debugman.com/read.php? Tid = 1122 & page = e #

Current fail tool list:

Icesword 1.22 --- failed
RKU 3.7 --- failed
Gmer 1.14 --- failed
SnipeSword 2008 0225 -- failed

Wsyscheck 20080223 -- failed

Hacker security expert Process Management 3.05 --- failed
DarkSpy 1.0.5 --- failed
SysProt 1.0.0.5 --- failed