Skip to content
Hiring teams6 min read

Spotting Candidate Fraud in Remote Hiring

How common fake candidates, proxy interviewers and deepfake video are, the warning signs at each hiring stage, and proportionate checks that stay fair.

By the HireRabbit.AI team · Published · Last updated

Hiring team on laptops watches a wireframe digital face on a large screen during a remote interview
On this page
  1. What the evidence says about scale
  2. Who is most exposed
  3. Warning signs at each stage
  4. Proportionate checks by stage
  5. How to avoid treating honest candidates as suspects
  6. A short incident response plan

This article is general information for HR teams and hiring managers, not legal advice. Identity checks, background checks, recording and the handling of ID documents are regulated differently by country, state and sometimes city. Check your plan with employment counsel and your privacy lead.

The problem often surfaces a few weeks after a start date, when a manager messages HR. The person on the team calls sounds different from the person they interviewed, can't do things they explained clearly in the technical round, and keeps their camera off.

Sometimes that is a nervous new hire with a bad microphone, and sometimes the person interviewed and the person doing the job are two different people.

This guide covers how often it happens, the warning signs at each stage, and checks sized to the risk that don't treat honest candidates as suspects. It fits inside the wider controls in our playbook for hiring in the AI era.

What the evidence says about scale

In a July 31, 2025 release, Gartner predicted that by 2028, one in four candidate profiles worldwide could be fake. In the same research, 6% of 3,000 surveyed job candidates said they had taken part in interview fraud, either posing as someone else or having someone else pose as them. The 2028 figure is a forecast, and the 6% is self-reported, so it is probably an undercount.

Greenhouse's AI in hiring report, published November 19, 2025, surveyed 4,136 people across the US, UK, Ireland and Germany. In it, 91% of US recruiters said they had spotted candidate deception, and 65% of hiring managers had caught applicants using AI deceptively.

The FBI's Internet Crime Complaint Center (IC3) first warned about this on June 28, 2022, reporting more complaints about deepfakes and stolen personal information being used to apply for remote roles, mostly in IT, programming and database work.

The best-documented schemes involve North Korean workers using stolen or borrowed US identities to get remote jobs. On June 30, 2025, the US Department of Justice announced searches of 21 suspected "laptop farms" across 14 states, tied to workers who had obtained jobs at more than 100 US companies using more than 80 stolen US identities.

On July 24, 2025, the DOJ announced that Christina Chapman had been sentenced to 102 months in prison for running a laptop farm from her Arizona home. Her scheme reached more than 300 US companies and generated more than $17 million for her and for North Korea.

Organized schemes aimed at remote technical roles are proven and prosecuted. But nobody has a reliable figure for how many hires overall are fraudulent, and you should be suspicious of anyone who claims one.

Who is most exposed

You don't need the same controls for every job. The FBI and DOJ material points to the same risk profile again and again:

  • fully remote roles
  • technical work
  • access to source code, customer data, financial systems or internal networks
  • a company laptop shipped to a home address

A fully remote senior engineer with production access needs more checks than a hybrid office coordinator.

Each spindle is a role, and each ring one of the four risk factors above: fully remote, technical work, access to code, data or systems, and a laptop shipped home. Point at a role to spread its rings and count them: the office coordinator carries one, a remote support agent three, the remote senior engineer all four.

Warning signs at each stage

A single sign rarely means fraud. People move, change phone numbers, have thin LinkedIn profiles, and freeze in interviews. What should get your attention is a cluster of signs, or a sign that contradicts something the candidate told you earlier.

At application

The FBI's January 23, 2025 PSA suggests checking your applicant tracking system for applicants who share resume content or contact details. A shared detail doesn't justify a rejection on its own, but it is a fair reason for an ordinary follow-up question, such as which team the person worked on at a named employer.

During interviews

Proxy interviewing leaves different traces. The person in the technical round may sound different from the person on the recruiter screen, and a proxy asked to walk through a decision on a listed project tends to give a generic answer.

Pauses, a flat delivery and poor video are also what you get from someone who is nervous, neurodivergent, speaking a second language, or on a weak connection. So an odd interview should lead to an extra verification step and nothing stronger.

At offer and onboarding

Here the FBI flags changes of address after a person is hired but before the laptop is delivered, and changes to payment platforms. After the start date, the signs shift to IT, such as logins from several countries within a short time.

Proportionate checks by stage

The goal is to add friction where fraud is most expensive and least likely to hurt honest candidates. Identity verification at the offer stage costs a genuine candidate ten minutes and happens after you have already decided you want them. A passport scan before a first screening call asks strangers for sensitive documents for a job they may never be offered.

StageWarning signProportionate check
ApplicationDuplicate resumes, shared phone numbers or emails across different namesDeduplicate in your ATS; ask a normal follow-up question about a listed employer or project
Recruiter screenLocation answers that don't match time zone or earlier messagesConfirm city and work authorization verbally, and note the answer for later comparison
Technical interviewVoice or knowledge noticeably different from the earlier screenA live exercise where the candidate talks through their own reasoning, with the same interviewer across two rounds where possible
Video interviews generallyAudio and lip movement out of sync; coughs or sneezes that don't appear on screenA camera-on policy stated in the invitation, with accommodations offered; a short in-person or verified video step for high-risk roles
ReferencesReferences reachable only by personal email or messaging appsContact references through the company's main switchboard or a verified work address
OfferIdentity details that don't match earlier informationIdentity document check against a live person before the offer is final, using a consistent, disclosed process
Pre-startShipping address changes after the offer; freight forwarder addressesShip only to the verified home address, or require in-person pickup for high-risk roles
Payroll setupAccount in another person's name; early changes to bank detailsVerify bank account ownership matches the employee; add a callback step for any payroll change
First weeksLogins from several countries; unexpected remote desktop softwareIT monitoring under your existing acceptable use policy; least-privilege access until probation checks are done
Eight gates, one for each stage in the table, stand taller where the check is stronger: early stages ask questions, and from the offer on the checks verify identity, address, bank details and access. Point at a gate to raise it and see that stage's check.

If you require cameras on, say so in the interview invitation, along with who to contact about accommodations. For ID checks at offer, tell candidates when the check happens, what documents are accepted, who sees them and how long they are kept.

Device and payroll checks at onboarding are often the cheapest controls, and they work best against organized schemes, because laptop farms depend on company equipment being shipped somewhere the worker is not. Treat an early request to change the shipping address or payroll account as a reason for a phone call.

How to avoid treating honest candidates as suspects

Almost everyone who applies to your jobs is who they say they are. A fraud program that treats all of them as suspects will cost you good candidates, and it creates its own legal risk if checks land more heavily on people with foreign names, accents or non-US education.

Almost everyone in the tray is who they say they are. Point at a card and the loupe checks that card alone, the way an ID check at offer falls only on the candidate you have already decided you want.

Four habits keep the checks fair:

  1. Disclose the checks. Put identity verification, camera expectations and reference methods in your job posts or interview invitations. Honest candidates barely notice; people planning fraud often drop out.
  2. Apply them to everyone in the same role. Ad hoc checks triggered by a recruiter's gut feel are where bias gets in.
  3. Offer accommodations. Give candidates who can't use a camera reliably a named contact and an alternative, such as a phone call followed by a verified ID check.
  4. Separate a signal from a decision. When something looks off, the next step is a documented verification step, reviewed by a person who knows the role. Nobody should be rejected because a tool or a single interviewer flagged them.

As one example, the AI Interviewer in HireRabbit.AI shows candidates a consent screen before a spoken first-round interview starts. Its integrity flags for eye, body or hand movement go to a person to review and never change the candidate's score. More detail is on the AI Interviewer page.

A short incident response plan

Write this plan before you need it, agree it with IT, legal and payroll, and keep it to a page.

  1. Don't confront the person yet; a warning gives an organized scheme time to copy data or wipe devices.
  2. Bring in security and legal without alerting the person.
  3. Reduce privileges and rotate shared credentials in one planned step.
  4. Preserve evidence, including the fraudulent identity documents.
  5. Freeze payroll changes for the account.
  6. Report it: in the US, the FBI asks companies to report this activity to the IC3 at ic3.gov.
  7. Find the stage that should have stopped the person, and fix the process first.

Put this into practice.

Free during invite-only early access. All you need is a work email, and a person reviews every request.