Deepfake Interview Fraud: 128 Facial Landmarks Catch Imposters

Here's something that should stop you mid-scroll: in a live video interview, you could be watching a fully AI-generated person, not a recording, not a filter, but a real-time synthetic face, and your brain would probably not catch it. Not because you're inattentive. Because you were never built to spot this kind of lie.

Deepfake fraud in remote hiring isn't a theoretical future problem. According to CXOToday, detection systems flagged deepfake fraud in 25-30% of suspicious interview sessions, compared to the 10-15% baseline that human reviewers identified on their own. That gap isn't a small rounding error. It's the difference between your hiring team catching one in ten fraudulent candidates and catching one in four. The tech sector accounts for roughly 60% of these cases, which means if you work in or around technology hiring, this is already your problem.

So how does this actually work? What's happening under the hood when a detection system identifies a fake face, and why can't a sharp-eyed recruiter do the same job?

---

Deepfake Fraud News and Your Visual Perception

Human face recognition is extraordinary at one specific task: recognizing people we know. We can spot a friend across a crowded room, identify a family member from a partial profile, read emotional states from a half-second glance. Evolution spent a very long time optimizing this skill.

What evolution did not optimize for, because it couldn't have, is detecting temporal artifacts in digitally rendered video. When you watch a live interview, your brain is processing the whole scene: Does this person seem nervous? Are they making eye contact? Do their answers feel rehearsed? You're reading social signals, conversational rhythm, micro-expressions. What you are absolutely not doing is tracking whether each blink takes the statistically expected 150-400 milliseconds, or whether the lip movement in frame 847 is three frames ahead of the corresponding audio waveform. This article is part of a series, start with Deepfake Bills Photo Evidence Investigators 2026.

That's the gap deepfakes exploit. Not your intelligence. Your evolutionary priorities.

That 22-percentage-point gap between human and machine detection tells you everything about where the real work happens. Humans identified about 71% of deepfakes in benchmark testing, while detection algorithms reached 93%, and the cases where humans caught fakes that machines missed were almost always gross visual artifacts, the obvious failures. The subtle ones? Machines win every time.

---

Best Deepfake Detection Tools and Their Signals

Detection systems don't just ask "does this look like a real face?" They track three distinct signal categories that deepfake generation consistently struggles to fake simultaneously.

1. Blink Rate and Temporal Consistency

Deepfake videos are generated frame by frame. That sounds obvious, but the implication is important: each frame is optimized individually, without the rendering system necessarily "knowing" what the adjacent frames looked like. The result is that eye movements, which in real humans are tightly coordinated between both eyes, can drift out of binocular sync. Blink timing can be irregular. The rate can be statistically slow or fast compared to human baseline. None of this is visible to a casual observer. But a detection system tracking temporal consistency across hundreds of frames can calculate whether the blink pattern matches physiological norms, and flag when it doesn't.

2. Mouth Region Sync Errors

This one is particularly important, and it's where a lot of detection research is focused. A lip-syncing deepfake, where real audio is paired with a synthetic face, generates lip movements using AI models trained to match phonemes to mouth shapes. The problem, as researchers have documented in work published on arXiv, is that the artifacts from this process are spatially constrained to the mouth region. The rest of the face can look completely convincing. But when you analyze the mouth in isolation, tracking the spatial and temporal patterns of lip movement frame-by-frame, the inconsistencies become measurable. The mouth region is essentially a different video stitched into a real face, and the seam shows up in the data even when it doesn't show up to the eye.

3. Three-Dimensional Rendering Failure

Here's the structural weakness that makes simple liveness checks still surprisingly effective today: most deepfake generation tools produce frontal-facing synthetic faces. They don't model a genuine three-dimensional head. Ask a real person to slowly turn their head to show their profile, and their face naturally foreshortens, light redistributes across new surface angles, and the geometry of features shifts in ways governed by actual physics. Ask a deepfake candidate to do the same thing, and the rendering system has to extrapolate a profile view it was never trained to generate convincingly. The result frequently breaks. Worth noting: this technique works now. As generative tools improve, that window will close, which is exactly why relying on any single detection signal is the wrong approach. Previously in this series: 500 000 Deepfake Identities Expose How Investigations Fall A.

"AI-generated avatars designed to mimic appearance and voice can bypass automated evaluation, and platforms identify behavioural and visual inconsistencies throughout the interview that humans watching in real-time would miss." CXOToday

---

How a Face Becomes 128 Numbers, and Why That's the Point

Here's where facial comparison technology earns its keep. The entire problem of "does this face match that face", which sounds like a question about visual similarity, is actually a question about geometry. And geometry is something machines handle very well.

When a facial recognition engine processes a face, it identifies a set of landmark points: the corners of the eyes, the edges of the nostrils, the peaks of the upper lip, the contours of the jawline, and dozens more. These landmarks get converted into a mathematical encoding, a vector in 128-dimensional space. As detailed in technical documentation on Medium's ML-Everything, the dlib face recognition model produces these 128-dimensional encodings and, using a Euclidean distance threshold of 0.6, achieves 99.38% accuracy on the standard LFW face recognition benchmark.

Think about what that means practically. Two photos of the same person produce two vectors. The Euclidean distance between them, how far apart those two points sit in 128-dimensional space, should be small. Two photos of different people produce vectors that are far apart. "Does this face match that face?" becomes "is this distance below 0.6?" That's not a subjective judgment. It's arithmetic.

This is the counterfeit banknote problem. A convincing fake bill looks right at a glance, correct colors, correct portrait, correct denomination. But trained bank staff don't evaluate overall appearance. They check the security thread under UV light, examine the micro-printing magnification, feel the paper texture. Each check targets a specific property that counterfeiters struggle to replicate at scale. Deepfake detection works identically: it doesn't ask "does this face look real?" It asks "do the geometric relationships between these 128 landmarks remain consistent across frames?" and "does the Euclidean distance between this face and the claimed identity fall within threshold?" The questions are specific, mathematical, and much harder to fool simultaneously than a single visual impression.

---

Why "I Watched Them Live" Doesn't Mean What You Think

The deepest misconception about deepfake hiring fraud is that live video is a safeguard. The intuition makes sense: a recording could be faked, but surely real-time interaction can't be? The candidate responded to my specific questions. They reacted to what I said. They were clearly present.

This intuition is wrong, and it's wrong for a structural reason that's worth understanding. Real-time deepfake generation doesn't need to sustain perfect rendering for 90 minutes. It needs to sustain good-enough rendering at the frame level, and "good enough for a human watching a compressed video call" is a much lower bar than "good enough to pass algorithmic analysis." Video compression artifacts, lighting variations in a home office, a slightly pixelated camera, all of these provide cover. The inconsistencies that expose a synthetic face exist at the frame-to-frame level, in the temporal record of a video file. A recruiter watching in real time processes a summary of that record. An algorithm processes the record itself. Up next: Why A Deepfake Face Can Fool Your Eyes In Seconds But Not 12.

At CaraComp, this distinction shapes how we think about facial comparison entirely. The question is never just "do these two faces look similar?" It's "do the geometric encodings match, do the temporal signals hold, and does the face behave in three dimensions the way a real face should?" That combination of checks is what separates a genuine identity verification from a confidence score that a well-rendered synthetic face can game.

Here's the shift worth sitting with. For decades, identity verification relied on a human asking: "Does this face match this document?" That question is now insufficient, not because humans got worse at it, but because the thing being faked got better. A deepfake doesn't need to fool a biometrics expert. It needs to fool a hiring coordinator on a Tuesday afternoon video call, tired, working through their fifth interview of the day. The solution isn't hiring sharper people. It's accepting that some fraud signals are simply invisible to human perception, and building verification pipelines that measure what eyes cannot.

The deepfake candidate isn't a sci-fi scenario anymore. The only interesting question now is whether the tools checking the identity are measuring the right 128 things, or just asking if the face looks about right.

If you had to verify someone's identity over video today, what's the one extra check you'd add after learning that a convincing deepfake can pass a casual live interview?

Interview Fraud: Why It Slips Past Standard Screening

Interview fraud is what happens when the person on your screen is not who your applicant tracking system says they are. This can mean a deepfake face layered over a real person's voice, or it can mean a completely different human being standing in for the actual candidate during a remote interview. Standard screening, resume checks, reference calls, a recruiter's gut read during the video call, was never designed to catch either version, because both were rare enough to ignore until recently.

The reason interview fraud works so well right now is timing. Hiring moved to remote interviews faster than verification tooling caught up, and a lot of companies still treat "I saw them on camera" as equivalent to "I confirmed their identity." Those are not the same claim, and treating them as interchangeable is exactly the gap deepfake candidates are built to exploit.

Remote Interviews and the New Verification Gap

Remote interviews removed a layer of friction that used to matter more than people realized: physically showing up. When candidates had to walk into an office, sit across from a hiring manager, and hand over a badge or ID at the door, identity was confirmed almost as a side effect of the process. Remote interviews strip that step out entirely, replacing it with a video call that most teams never designed to be a security checkpoint.

That gap is exactly why detection tooling has become necessary rather than optional for remote interviews. A hiring manager conducting remote interviews back to back has no reasonable way to track blink timing or mouth-sync artifacts frame by frame, and expecting them to is unfair to the interviewer and unsafe for the company. The fix isn't asking recruiters to watch harder during remote interviews, it's giving them software that watches the parts human attention was never built to monitor.

Deepfake Candidates: What Recruiting Teams Are Actually Facing

Deepfake candidates come in two flavors, and it's worth keeping them separate. The first is a synthetic face generated in real time, worn like a mask over a real person's video feed during the interview. The second is a stolen or fabricated identity, a real face, but not the face of the person who will actually show up for work. Both count as deepfake candidates in the broad sense recruiting teams now have to worry about, and both exploit the same blind spot: nobody on the hiring side is trained to verify identity at the frame level.

Recruiting teams facing deepfake candidates for the first time often assume the fix is more scrutiny, slower calls, more follow-up questions, closer attention. That helps a little, but it doesn't address the core problem, because deepfake candidates are specifically engineered to survive normal human scrutiny. The actual fix is layering in detection systems that check the things scrutiny can't reach: landmark geometry, temporal consistency, and mouth-region sync.

Deepfake Interviews in Practice: A Walkthrough

Picture a deepfake interview from the detection system's point of view rather than the recruiter's. The video feed comes in, and instead of asking "does this look like a real person," the system extracts 128 landmark points per frame and tracks how they move relative to each other across the session. A deepfake interview will show geometric relationships that drift slightly from frame to frame in ways a real face's bone structure would never allow.

At the same time, the system checks blink timing against physiological norms and isolates the mouth region to look for the sync errors described earlier in this article. None of these checks require the reviewer to "notice" anything unusual in the moment, the deepfake interview gets flagged by the math, not by a gut feeling. That's the entire point of building detection into the pipeline instead of relying on the interviewer's instincts.

For companies hiring at volume, this matters more than it might seem. A single deepfake interview that slips through can mean a fraudulent hire gaining access to internal systems, sensitive data, or a company laptop shipped to an address that has nothing to do with the person who interviewed. Security teams increasingly treat interview-stage identity verification as part of the same discipline as endpoint security and access control, not as a separate HR concern bolted on afterward.

Recruiting teams that have adopted layered detection report a simple shift in how they talk about candidates: instead of "this felt off," they can point to a specific flagged signal, a blink pattern outside normal range, a mouth region that didn't match the rest of the face, a profile turn the rendering system couldn't handle. That specificity is what turns a vague suspicion into an actionable security decision, and it's why detection tools are becoming standard rather than optional across recruiting.