Does HackerRank Detect Copy and Paste?

Yes, on every test, and the employer does not have to switch it on. As of September 9, 2026, HackerRank documents copy-paste tracking as a built-in feature: the report records when a candidate copies or pastes, and "Pasted content appears in the candidate's test report." Secure Mode and Desktop App Mode go further and block pasting from outside the test. The AI plagiarism model, when enabled, treats "External Copy-Paste" as one of its named patterns. What HackerRank cannot see is text that never passes through the clipboard into its editor.

What the default tracking records

HackerRank's Test Integrity documentation lists copy-paste tracking alongside tab proctoring as features that apply without any integrity mode. It records copy and paste actions, and the pasted content itself appears in the candidate report. Recruiters also get a "Copy-Paste Frequency" column in the CSV export and an indicator on the detailed report that helps them spot large pastes.

HackerRank's own article on tab proctoring includes "Attempts to copy content from or paste content into the assessment" among the events it logs with a timestamp (Tab-Proctoring: What It Catches and What It Misses).

The mechanism is ordinary browser behavior. A web page receives paste events in its own editor and can read the text as it lands. It cannot see what you copy in another application until that text arrives in HackerRank. The browser side of this, including what a paste event cannot prove, is in how interview websites detect copy and paste.

What Secure Mode and Desktop App Mode block

The Secure Mode documentation says the mode "Blocks external copy and paste actions during the test", and Proctor Mode includes Secure Mode. The Desktop App Mode documentation states that "Copy-paste functionality is disabled to prevent pasting content from external sources".

HackerRank's wording in both cases is external. Moving a line within the editor is not what the block targets. HackerRank does not publish how it separates internal from external clipboard content, so the safe reading is that anything that arrives by paste is logged, and clipboard text that originated outside the editor is what the block and the flag are about.

How a paste feeds a plagiarism flag

Tracking alone produces a record. A flag comes from the AI Plagiarism Detection model, which uses copy-paste activity together with code-writing patterns, solve time, and tab switching, and names "External Copy-Paste" and "Suspicious Code Resetting" as the patterns it looks for. HackerRank reports "an overall precision of 85%, meaning flagged sessions are correct 85% of the time." Flags are rated High or Medium, and the reviewer can watch where the paste landed in the Keystroke Codeplayer. HackerRank says candidates must consent before a test that uses this model starts.

The typing side of that replay, and what HackerRank does and does not log about keystrokes, is covered in whether HackerRank tracks keystrokes.

What a paste does not prove

A paste of your own boilerplate, a test harness, or a snippet copied from the problem statement is logged the same way as a paste from a solutions site. The report shows the content; a person judges it. HackerRank does not notify the candidate that a paste was flagged, and it documents no automatic penalty. The full list of what reaches the recruiter, by mode, is in what HackerRank proctoring detects and records.

Typing instead of pasting

Retyping code from a second screen produces no paste event. It does produce typing data: finished blocks arriving at a steady pace, solve times that do not match the iteration, and the deletion-and-retype pattern HackerRank calls Suspicious Code Resetting. That is not detection of the source. It is a signal handed to the same model and the same reviewer.

What this means for candidates

Assume every paste is visible with its full content. If you paste a template you keep for competitive programming, expect it in the report and be ready to say what it is. If the rules allow reference material, pasting from it is still logged, which is fine when it is allowed and a problem when it is not. Read the consent screen for the paste rule on your specific test, and if it is unclear, ask the recruiter in writing before you start.