Updates on curtailing plagiarism

All same codes from Starters 29 for Problem CCD.

https://www.codechef.com/viewsolution/60033141
https://www.codechef.com/viewsolution/60037314
https://www.codechef.com/viewsolution/60037348
https://www.codechef.com/viewsolution/60037350
https://www.codechef.com/viewsolution/60037350

1 Like

Its really frustrating to see a cheater getting rank 1 in a contest.

@admin @shaily_adm these cheaters have ruined your platform

Here is one such cheater @ankitraj6767
https://www.codechef.com/users/ankitraj6767

Here is his submission for SUBXOR which he has cheated

https://www.codechef.com/viewsolution/60217374

1 Like

same solution for min coloring
sol1: CodeChef: Practical coding for everyone
sol2 : CodeChef: Practical coding for everyone
sol3 : CodeChef: Practical coding for everyone

@admin

2 Likes

Here is the account he keeps on cheating and destroy the coding environment in codechef: https://www.codechef.com/users/sayan1303 @sayan1303
Please ban him. @admin
Solution: 60614557 | CodeChef
Solution: 60621632 | CodeChef
This proves how he cheats codechef.
@admin

2 Likes

Cheating in Starter 30 :1)CodeChef: Practical coding for everyone
2)CodeChef: Practical coding for everyone

Both of them has almost same code with a few changes in variable names and function name.
@admin

2 Likes

@shaily_adm when can we get the stats for starters 26,27,28,29 Feb-cookoff and Feb lunchtime at least. Its been over a month and cheaters who have been plagiarised are still cheating. Please take some action. Please inform us about the relevant stats as we were told we will know the relevant stats in 10 days but its been over a month

3 Likes

Rampant cheating in Stater 30.
Problem: MLIS

Code difference of first and last Python submission

CodeChef: Practical coding for everyone submitted at 21:26:45
CodeChef: Practical coding for everyone submitted at 22:59:35

Almost all PYTH 3.6 and PYPY 3 submissions have the same code with little to no changes.
AC Submissions PYTH 3.6
AC Submissions PYPY3

Combining them, 450+ submissions are based on the same code.

@admin

4 Likes

@cheat_reporter @admin @shaily_adm seeing the pattern many submissions are different and many are common too. Even if the logic was not that difficult and it could have been done in this way by many. So definitely all 450 submissions are not having the same submissions but around 30 percent are the same. I checked almost 60+ have the same code and the CodeChef team is not giving us any statistics about plagiarism in the past contests sadly

2 Likes

I have solved more than 200 questions and after that a plagiarism on my profile , its a very demotivating point for me.
Its showing on my profile that i have been plagarised in FEB222C. I didn’t received an email regarding plagarism… I haven’t copied anyone’s code. I have solved the question by myself, this is a very demotivating moment for me, please revert my rating to the original rating. Please solve my issue as soon as possible so that I can continue my learning on this platform. @admin @admin5

3 Likes

Please send an email to help@codechef.com so that we can have a better look at the issue.

1 Like

Huge amount of cheating happened in the 4th problem (Div.2) in the last 10-15 minutes.

This is the leaked solution:-
[CodeChef: Practical coding for everyone]
[CodeChef: Practical coding for everyone]
[CodeChef: Practical coding for everyone] added spaces, changed one-two variables.
[CodeChef: Practical coding for everyone]
[CodeChef: Practical coding for everyone]
[CodeChef: Practical coding for everyone]

These are just few examples, There will be tons of these type of solutions.

I request @admin, to also increase the ratings of non cheaters, when you penalize the cheaters in that round, because after penalizing, the non cheater’s rank gets better. Otherwise, there is no benefit of penalizing them.

1 Like

@admin @shaily_adm @lavish_adm
Again cheating happened on a large scale in March Lunchtime [LTIME106B (Div 2)].
Solution: 60873535 | CodeChef
Solution: 60873394 | CodeChef

There are at least 40 exact same to same submissions of the problem C in div 2 and many of those who are cheating are the ones who have cheated before.

It is requested to update us about the plagiarism stats for the past contests of starters 27,28,29, March cookoff at least as they happened almost a month earlier.

Its been a long time since these cheaters are constantly cheating and affecting the rank of the ones who are doing it honestly thus it is requested for the rating to be changed and increased for the honest ones if possible shortly. It is requested if we are updated about all the relevant statistics

2 Likes

@admin @shaily_adm @lavish_adm

It is obvious from the number of posts on this topic, and the number of users who have taken time to list obvious plagiarized solutions, that most users would like Codechef to do more to reduce plagiarism. Unfortunately it doesn’t seem like this is a very high priority for Codechef. Some questions it would be interesting to get answers to:

  1. Does Codechef do anything with the information that some users are providing listing plagiarized code, or are these users just wasting their time?

  2. If the users can identify plagiarized code with simple brute force checking of code submitted for the harder problems during the last few minutes of a contest, why is it so hard for Codechef to detect this cheating by similar means?

  3. Does Codechef really care that much about cheating, or is there simply more interest in just getting large numbers of contest entries regardless of whether the participants are cheating or not?

Codechef needs to perform the plagiarism checking prior to posting updated user ratings. Anything else makes a mockery of the rating process.

Users who are caught cheating should have their account removed, not simply have their rating decremented by some arbitrary number of points. This would require the cheaters to start over with a new account.

As an alternative to plagiarism checking Codechef could just eliminate calculating any ratings. Ratings calculated by the current process are pretty close to meaningless (in terms of actual skill) for many of the participants. Some are getting far higher ratings than they deserve due to cheating, and many more are getting far lower ratings than they deserve since the cheaters are skewing the scoring.

9 Likes

No updates yet for the plagiarism statistics for starters 27,28,29,30, February long challenge, March cookoff, March lunchtime. It is way beyond 10-15 days to update as promised by the admin to catch cheaters plagiarism. Please update us and deduct more than 275 ratings so that they don’t dare to cheat again. @admin @shaily_adm @lavish_adm

1 Like

This User plagiarized in todays starters32
https://www.codechef.com/viewsolution/61696512
As you can see the telegram link is commented out
@admin

1 Like

Thanks for reporting, we’ll surely look into this and take necessary action.

2 Likes

Dear @admin @shaily_adm
I have been falsely accused of a plagiarism case in the LTIME106D contest. The solutions that have been flagged are of easy level and short in nature, so there is no reason to copy a solution from anyone.

I have never tried to violate CodeChef’s code of conduct and would continue doing the same. I request you to look into the matter as this clearly is a co-incidental match.

Kindly reply to me as soon as possible because I have worked really hard to gain the ratings I currently have and will get demotivated if I get falsely accused.
I have already mailed back but got no response so far.
The matching solutions are:-

  1. CodeChef: Practical coding for everyone
  2. CodeChef: Practical coding for everyone

Thanks and Regards,
Ayush Kumar

1 Like

Please send an email to help@codechef.com so that we can have a better look at the issue.
Due to the number of appeals we receive, it’ll take us up to 7 days to reply to you.

3 Likes

It would be much better if the stats are written in the order of format and occurrence for eg. Stats of all the February events under February Title and then Starter events under Starter title and so on. This would be easier for everyone including the moderators to view and edit the stats.
Eg:

February 2022

Starters
Starter 1:
Starter 2:

Long Event
Long Event 1
Long Event 2

1 Like