[Feature] Implement Basic Anti-Cheat Protection

[giteku]

Fixes Features 🎫 #1

Description:
We need to add baseline anti-cheat protection to the Javelin Project.

The protection should include:

• Debugger detection: Prevent the application from running when a debugger is attached.
• Suspicious process detection: Detect and block known cheat tools (e.g., Cheat Engine, x64dbg, OllyDbg).

Acceptance Criteria:

• Application exits when a debugger is detected.
• Application exits when a suspicious process is found.
• Works for both C++ client (AntiCheat.cpp) and Python monitor (anti_cheat.py).

[orangecurl]

/bounty 5000

[algora-pbc]

💎 $10,000 bounty • Orange

Steps to solve:

1. Start working: Comment /attempt #2 with your implementation plan
2. Submit work: Create a pull request including /claim #2 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

❗ Important guidelines:

• To claim a bounty, you need to provide a short demo video of your changes in your pull request
• If anything is unclear, ask for clarification before starting as this will help avoid potential rework
• Low quality AI PRs will not receive review and will be closed
• Do not ask to be assigned unless you've contributed before

Thank you for contributing to javelin-anticheat/py-workedtask!

[orangecurl]

/attempt #2

[aybanda]

/attempt #2

[Pranjal6955]

/attempt #2

[Brijeshthummar02]

@sfatzmw can you share more details regarding the issue.

[debaa98]

hey @orangecurl @giteku is this Bounty still available ?

[rbxict]

/attempt #2

Implementation plan:

1. Add a native Python anti-cheat monitor that matches the C++ scope: debugger detection plus suspicious process detection on Windows.
2. Keep the implementation dependency-light by using Windows APIs / built-in process listing instead of introducing heavy external packages.
3. Add focused unit tests for debugger detection, process parsing, and guarded exit behavior so the acceptance criteria are verifiable from a clean clone.
4. Tighten the README with exact run/test steps for both the C++ client and Python monitor.