❓ C++ Game Hacking Questions

Short answers to the three things you're asking.

The behaviour you describe, where the tool comes up looking like System Info, Phone Dialer or another built-in Windows app, is generally called process masquerading. It's normally done one of two ways: the loader gets into a legitimate signed process so the image on screen is a Microsoft binary, or the tool sits behind a DLL that a signed host is tricked into loading for it, which is DLL proxying / side-loading. Either way the point is that a naive check on image name or signer passes. It's a presentation trick, not a detection bypass by itself.

On the kernel side, what you're really buying is the fact that user-mode anti-cheat can't inspect a driver's memory, so reads and writes happen underneath the layer that's doing the watching. The trade-off is that drivers need signing and loading, they're tied to OS builds, and one you didn't write can be revoked or blacklisted whenever whoever signed it feels like it. I wouldn't build a project on a bought driver.

Thread hijacking is the cheaper direction if you stay in user mode. Instead of creating a thread inside the target, you borrow one that already exists and hand it work, so there's no new thread for anything to enumerate, and combined with keeping your allocations and handles out of the obvious places it gets you much further than ReadProcessMemory/WriteProcessMemory ever will.

Past that I'm not going to write the steps out on a public thread. That part is a few evenings of reading and breaking your own builds, and a working recipe posted here just shortens the detection cycle for everyone including you.

If you're still interested in this, send me a private message and we can talk through what you're actually trying to build.