Hello Codeforces!↵
↵
I have now created a brand-new frontend for the cheater database that has been [circulating in your CF recent actions for the last 48 hours](https://codeforces.me/blog/entry/144116). So now, please do NOT DM me or [user:Proof_by_QED,2025-06-25] or [user:cry,2025-06-25]. Now, you can submit reports here↵
↵
Just a reminder that reports:↵
↵
MUST contain conclusive evidence (just linking their profile and saying "he cheated" is NOT enough)↵
Cannot contain too many submissions (we are human after all, we don't have all the time in the world)↵
MUST have usernames spelt correctly. Case sensitivity is not important.↵
↵
Here it is: https://cf-cheater-database.vercel.app/ ↵
↵
Note that the Chrome extension remains unchanged and still works.↵
↵
UPDATE 26/06/2025↵
↵
Hello Codeforces!↵
↵
It's been amazing seeing you all contribute to this project — so thank you very much for doing so. I need to share some updates.↵
↵
1. APPEALS — now, if you feel you have been wrongly labelled as a cheater, you can submit an appeal directly on the website. Therefore, do not spam the blog further, and use the website.↵
↵
2. CHROME EXTENSION — some people have reported a bug with the chrome extension where it does not highlight all cheaters. This was a genuine coding mistake from me, due to which I have released a NEW VERSION of the chrome extension. Please redownload it from GitHub and reinstall if you downloaded the extension before today.↵
↵
3. OUTAGES — some people reported outages — these are again the fault of the developers, and the issues have been fixed.↵
↵
4. POLICY – Add ALL cheaters to the platform, no matter how they cheated. Submit concise reports with clear, conclusive evidence — full profiles will be ignored. If a report is declined, gather stronger proof before resubmitting; do not spam the same report multiple times. If you are submitting a report and see a skipped submission/contest, you can attach it, but the mere existence of a skipped contest does NOT constitute conclusive proof that the user is a cheater, especially because Codeforces marks all but the last AC submission as Skipped in Div 1 and 2 rounds.↵
↵
Thank you again for all of the support, with your help, we are well past 1000 cheaters in the database and this number is quickly increasing.
↵
I have now created a brand-new frontend for the cheater database that has been [circulating in your CF recent actions for the last 48 hours](https://codeforces.me/blog/entry/144116). So now, please do NOT DM me or [user:Proof_by_QED,2025-06-25] or [user:cry,2025-06-25]. Now, you can submit reports here↵
↵
Just a reminder that reports:↵
↵
MUST contain conclusive evidence (just linking their profile and saying "he cheated" is NOT enough)↵
Cannot contain too many submissions (we are human after all, we don't have all the time in the world)↵
MUST have usernames spelt correctly. Case sensitivity is not important.↵
↵
Here it is: https://cf-cheater-database.vercel.app/ ↵
↵
Note that the Chrome extension remains unchanged and still works.↵
↵
UPDATE 26/06/2025↵
↵
Hello Codeforces!↵
↵
It's been amazing seeing you all contribute to this project — so thank you very much for doing so. I need to share some updates.↵
↵
1. APPEALS — now, if you feel you have been wrongly labelled as a cheater, you can submit an appeal directly on the website. Therefore, do not spam the blog further, and use the website.↵
↵
2. CHROME EXTENSION — some people have reported a bug with the chrome extension where it does not highlight all cheaters. This was a genuine coding mistake from me, due to which I have released a NEW VERSION of the chrome extension. Please redownload it from GitHub and reinstall if you downloaded the extension before today.↵
↵
3. OUTAGES — some people reported outages — these are again the fault of the developers, and the issues have been fixed.↵
↵
4. POLICY – Add ALL cheaters to the platform, no matter how they cheated. Submit concise reports with clear, conclusive evidence — full profiles will be ignored. If a report is declined, gather stronger proof before resubmitting; do not spam the same report multiple times. If you are submitting a report and see a skipped submission/contest, you can attach it, but the mere existence of a skipped contest does NOT constitute conclusive proof that the user is a cheater, especially because Codeforces marks all but the last AC submission as Skipped in Div 1 and 2 rounds.↵
↵
Thank you again for all of the support, with your help, we are well past 1000 cheaters in the database and this number is quickly increasing.
