Security: User progress data not protected, cheating possible

[anshul23102]

Problem Statement

Cheating possible:

• Progress data modifiable
• Scores fabricated
• Fairness broken

Business Impact: Unfair competition
Technical Impact: No validation

Root Cause Analysis

No server-side validation. Client data trusted.

Solution Overview

1. Validation: server-side validation
2. Verification: verify progress
3. Anti-cheat: detect cheating
4. Logging: log all actions
5. Penalties: penalty cheaters

Type of Change

• Security fix: Anti-cheat

Testing Done

• Validation test: works
• Cheat test: detected
• Fairness test: fair

Related Issue

Relates to fairness

Suggested Labels

security, anti-cheat, fairness, gssoc26

[github-actions]

Thank you for raising this issue!

We'll review it as soon as possible. We truly appreciate your contributions! ✨

Meanwhile make sure you've visited the README.md, CONTRIBUTING.md, and CODE_OF_CONDUCT.md before creating a PR for this. Also, please do NOT create a PR until this issue has been assigned to you. 😊

[pushtikadia]

Hello maintainers! I am an active GSSoC'26 contributor and I am very eager to solve this issue.

I have strong experience with backend architectures, secure state handling, and logic optimization. I can provide a robust, clean, and production-ready solution for this. Please assign this issue to me so I can start working on it right away! Thank you.