JX2 Memory Address Tracking Bypass -- 2

Job ID: 40629960

Budget: $30 – $250 USD

Project Description:
I am looking for an experienced reverse engineer to develop a stealth method that allows memory reading tools (such as Cheat Engine or a custom DLL injector) to attach to the JX2 game client without triggering the game's anti-cheat system and causing account bans.

This is Phase 1 of a larger project. At this stage, I do not need you to extract NPC IDs, map data, or item IDs yet. The only goal for this phase is to:

Successfully attach to the game process and read memory without being detected or banned.

What I Need You To Do:
Research & Analysis

Identify the anti-cheat system used by JX2 (e.g., HackShield, Xigncode, or custom).

Analyze how the anti-cheat detects external memory tools.

Develop a Bypass Method

Create a working method to bypass the anti-cheat detection.

This can be done via:

Kernel-mode driver

DLL injection

Code caves

Custom Cheat Engine driver

Or any other proven technique

Proof of Concept

Demonstrate that Cheat Engine (or your custom tool) can attach to the game and read basic memory values (e.g., player HP, gold, or character name) without the game crashing or the account being banned.

Stability Test

The bypass must work for at least 30–60 minutes of continuous gameplay without detection.

I am digging into JX2’s runtime under Windows to map every critical memory address that influences player stats, inventory and movement, then prove a safe way around its current anti-cheat layer through controlled code injection. My immediate goal is a repeatable method that lets me attach a custom DLL, locate the dynamic addresses after each update and interact with them without triggering the game’s integrity checks.

Here is the scope I need covered:

• Build or adapt a lightweight injector that slips past the existing anti-cheat driver, keeping the game stable during and after injection.
• Trace and document the relevant address chain (static bases, pointer offsets, encryption routines) so I can reproduce the map after a patch with minimal effort.
• Supply a concise write-up on how your approach avoids detection, including any obfuscation or stealth techniques used.

Your proof-of-concept should launch on a clean Windows 10/11 system, demonstrate read/write access to a chosen variable and exit cleanly with no ban or crash for at least a 30-minute session. Source code, annotated findings and a brief usage guide are the required deliverables.