Contact person: Business Client

Phone:Show

Email:Show

Location: Hong Kong, China

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Building a high-integrity, kernel-level anti-cheat solution requires a professional truly passionate about Windows kernel development.​ The cornerstone of this work is a robust, production-ready driver written in C/C++.

Must be familiar with IOMMU memory isolation strategies.

Required Qualifications:

Proven experience in designing or maintaining commercial game security drivers, ideally those deployed by EAC, BattlEye, or major studios.

Deep mastery of NT kernel internals—particularly memory management and the object manager—to identify and block any attempts to tamper with protected regions or kernel objects.

Battle-tested reverse engineering skills with WinDbg, IDA Pro, and x64dbg; you will spend significant time tracing the source of DLL injection, illegal memory reads/writes, and communication tampering attempts.

A track record of successful offensive-defensive collaboration, demonstrating the ability to think like an attacker, simulate emerging threats, and write extremely stable code across all supported Windows builds.

Preferred Qualifications (Will elevate your candidacy):

Prior experience publishing defenses against techniques for loading unsigned drivers, or deep familiarity with the intricacies of the Microsoft code signing process (and how attackers attempt to bypass it).

A passion for gaming and a desire to maintain fairness are significant advantages.

Deliverables:

A kernel driver with complete, well-commented source code.

A concise technical report detailing the covered attack vectors, hardening of memory and object manager hooks, and the methodology for validating stability across cold starts, sleep/hibernate cycles, and heavy I/O operations.

Reproduction steps and symbol files to enable seamless debugging in WinDbg by our team.

I highly value meticulous code, detailed threat reasoning, and the ability to quickly resolve tricky race conditions or paging IRQL vulnerabilities. If this sounds like your everyday workflow, let's talk." (client-provided description)