A job candidate at Vidoc Security Lab hid behind a real-time face filter and refused to cover his face. What happened, what's verified and what to check.
Social Engineering Examples·10 sources
Vidoc Security Lab's deepfake job interview is one of the earliest widely shared videos of a candidate hiding behind a real-time face filter. Vidoc, a Polish-founded security startup based in San Francisco, says two applicants with fake identities reached interviews for a remote engineering role in Poland. The first, around December 2024, wasn't recorded. The second, on 4 February 2025, was. When cofounder Dawid Moczadło asked him to put a hand in front of his face, he refused. Status: Company account; not independently verified.
| Candidate 1 (about December 2024) | Candidate 2 (4 February 2025) | |
|---|---|---|
| Name used | "Makary Krol", claiming a Polish background and a Warsaw University of Technology degree | "Bratislav Rakočević", claiming a Serbian background and a University of Kragujevac degree |
| How far he got | Passed CV screening, an HR call and the technical interview. First candidate ever to finish all coding tasks inside two hours | Reached the technical interview after dodging video twice with a "broken camera" |
| What was seen | Blurry camera, video lagging behind his voice, then a frozen camera | A face that didn't match his LinkedIn photo and didn't sit right on his neck |
| Recorded? | No | Yes, published the same day with the audio removed |
| Face filter? | Suspected. Vidoc "had no evidence of this," per The Pragmatic Engineer | Visible on the recording, though no forensic analysis was done |
The second candidate had approached the cofounders on LinkedIn before any job was open, asking if they were hiring. His profile had about 500 connections, some of them real mutual ones.
So what happened on the call? Moczadło started recording and asked him to hold a hand in front of his face. Real-time face filters tend to break when something covers the face. The candidate asked if it was a joke and refused. Pushed, he lifted a hand "carelessly, in a way that didn't actually cover his face", in Vidoc's words. Moczadło ended the call.
Tip: ask a remote candidate to wave a hand slowly across their face early in the call. It costs nothing and a refusal tells you plenty.
Vidoc believes one person ran both personas. The voices sounded almost identical, and the second candidate seemed oddly ready for the questions. But that view comes via The Pragmatic Engineer, and the only recording has no sound. Readers can't check it.
Read where this story comes from. Vidoc's blog post and LinkedIn posts are first-party. The Pragmatic Engineer, The Register and Inc. all interviewed the same cofounder. The Register said it hadn't done "deep forensic analysis of the video". Vidoc also sells security software, and its postmortem promotes a gated ebook and its own product.
Some viewers said the face looked like a well-known Polish politician. Nobody analysed that, and the politician has no link to the fraud, so they aren't named here. Reports raised a possible link to North Korean IT worker schemes. Unit 42 said the signs reported match that playbook, but alignment isn't attribution. Who was behind it is unknown.
Nobody was hired or paid. Moczadło told The Register the first candidate cost "more than five hours". The role had drawn roughly 500 applications.
Vidoc's own recommendations, plus Unit 42's:
See also the KnowBe4 fake IT worker and CoHost's suspected fake candidate.
On 4 February 2025, a candidate using a real-time face filter joined a Vidoc technical interview. He refused to cover his face with his hand, and the cofounder ended the call and posted the recording.
Only the second is on video. Vidoc suspected the first used a filter too but has said it had no evidence.
Unknown. Unit 42 said the reported signs match North Korean IT worker tactics, but nobody has attributed the attempts.
No one was hired or paid. The only cost cited is "more than five hours" of interview time on the first candidate.
Social Engineering Examples. “Vidoc Security Lab's deepfake job interview: two fake candidates (2024 to 2025)”. Accessed 3 November 2026. https://socialengineeringexamples.com/vidoc-security-deepfake-candidate-interviews-2025
the operator(s) likely used OSINT sources such as LinkedIn, company blogs, and funding-announcement coverage (Vidoc's $2.4M raise was publicly reported in October 2024) to identify Vidoc as an early-stage, security-focused, fully remote employer actively hiring for a Poland-based backend role. Vidoc also posted to Polish job boards such as JustJoinIT, where The Pragmatic Engineer notes the fakers were already active.
public hiring and funding announcements are hard to suppress without harming legitimate recruiting and PR, so the realistic control is not hiding this exposure but hardening the interview process a well-researched applicant will eventually reach.
the operator(s) built fabricated candidate identities, including a polished CV, an active LinkedIn profile with real mutual connections, and, in the second incident, a real-time face-swap video filter. Vidoc's own ebook describes a wider pattern it observed across many applicants: identical CVs submitted under different Eastern European names, each tied to a freshly created LinkedIn profile with AI-enhanced photos, and in one case a home address that was a public court building.
vet claimed credentials and employment history against independent, hard-to-fake signals, for example contacting claimed former employers directly, since a convincing profile and mutual connections are not proof of a real underlying identity. Check the mundane fields as well: an address that resolves to a public institution is cheap to spot and hard to explain.
per Vidoc's account, one persona approached the cofounders on LinkedIn before any role was open, asking if they were hiring, and followed up a couple of times before the company contacted him when the role went live. No source states a duration. Note the accounts disagree about which persona did this and when: Vidoc's blog and ebook attribute the outreach to the second persona, while The Pragmatic Engineer attributes a cold LinkedIn approach to the first fake profile and places it as early as February 2023.
treat unsolicited pre-role networking from unknown accounts as a neutral signal rather than a trust signal, and apply the same verification steps to warm leads as to cold applicants regardless of prior rapport.
fabricated CVs were submitted through Vidoc's normal job posting, and both personas passed an HR/operations screening call (15 to 30 minutes in the first case), exploiting the fact that early-stage screens are low-friction and not designed to catch identity fraud. Signals were already present and were not acted on: neither candidate spoke the language of the country he claimed to be from or to have taken a degree in.
add a lightweight identity-consistency check at the first live conversation, such as easily-verified biographical or cultural questions tied to the claimed background, rather than treating early screens as pure skills gates. In both of these cases the decisive inconsistency, an inability to speak the claimed home language, was audible at the screening call and was allowed to pass.
the first persona performed exceptionally in a live, timed two-hour coding interview, becoming the first candidate to finish all tasks and follow-up questions inside the allotted time. The interviewer's assessment was that this reflected real engineering ability rather than assistance. The second persona never reached a technical assessment: he was challenged within minutes of turning his camera on.
score technical performance and identity signals independently rather than letting a strong coding result offset unresolved identity doubts. The first candidate's coding was genuinely excellent, which is precisely why it carried him through three rounds.
in the second incident, the candidate first avoided video entirely by claiming a broken camera, forcing a reschedule, then joined with a real-time face filter active, which is the incident with a public recording. In the first incident, the candidate's camera was blurry and then froze; Vidoc believes a filter was in use but recorded nothing and has said it had no evidence.
require candidates to disable all video filters and virtual backgrounds and visually confirm this at the start of every video interview, and treat camera-avoidance excuses at the video stage as a reason to slow down rather than proceed.
in the second incident, the interviewer observed that the on-camera face did not match the LinkedIn profile picture, that the face did not sit correctly on the neck, and that answers came after a lag and were delivered as scripted, ChatGPT-style bullet points. That lag is a delay before answering, a tell for scripted or AI-assisted responses, and is distinct from the speech-to-video delay Vidoc reported in the first incident.
record interviews, including early screening calls, subject to disclosure and consent, so unusual speech patterns, accents, and lags can be reviewed afterward rather than resting on an interviewer's in-the-moment impression. Vidoc's inability to evidence the first incident is the direct argument for this control.
Moczadło started recording and asked the candidate to place a hand in front of his face, an occlusion test that real-time face filters handle poorly. The candidate asked whether it was a joke and refused outright; after insistence he raised his hand carelessly, in a way that did not actually cover his face, and the call was ended. No source reports that the filter visibly broke or glitched under occlusion: the test was never completed, and the interview ended on suspicion plus refusal. No liveness test appears in any account of the first incident, which was closed out by a non-technical background interview instead.
build an active liveness challenge into every final-round video interview as a standard step rather than an ad hoc response to suspicion. Unit 42 sets out the technical basis for the occlusion test and adds rapid head movements, exaggerated expressions and sudden lighting changes, noting that a refusal or a deliberately incomplete attempt is itself informative.
had either persona passed undetected, the goal was consistent with fraudulent employment, meaning securing an offer and onboarding to draw a salary under a false identity, with the added risk at a security company of gaining codebase/production access that could enable IP theft, backdoor insertion, or, per suspected DPRK-style overseas IT-worker schemes cited in reporting, sanctions-evasion revenue.
gate final onboarding on formal, ID-verified, in-person or live-unfiltered confirmation of identity before extending any offer or provisioning codebase/production access, which Vidoc adopted as a mandatory step after these incidents.
Browse by what this case has in common with others in the library.
Fraudsters faked WPP CEO Mark Read on WhatsApp and staged a Teams call with a cloned executive voice. The agency…
Prosecutors allege Ghanaian twins used fake female personas and AI video to take $15M+ from 130+ older Americans. What is…
ESET found PromptLock, ransomware that had a local AI model write its scripts at runtime. It turned out to be…
A Lapsus$ affiliate used a contractor's stolen Uber password, likely bought on the dark web, flooded them with MFA push…
In 2015, fake emails from Ubiquiti's CEO and a real London lawyer got its finance chief to wire $46.7M. How…
Fake finance "directors" in WhatsApp groups steered 18+ US investors to NanoBit, a crypto platform that never traded. The SEC…
A victim searching for the AnyDesk remote-access tool hit a typosquatted site with a fake Cloudflare Turnstile that, instead of…
North Korea-linked hackers ran fake job interviews for crypto firms, then told applicants to paste a 'camera fix' that installed…
Fugitive hacker Kevin Mitnick impersonated a vacationing Novell employee on a "top-secret" project, defeated a support analyst's voicemail-based identity check…
In 2015, fake emails from Ubiquiti's CEO and a real London lawyer got its finance chief to wire $46.7M. How…
Gootloader went quiet in the spring of 2025, the tracking researcher telling BleepingComputer his abuse reports caused the operation to…
A phishing attack resulted in disclosure of 2015 W-2 data for several thousand US employees, exposing SSNs and earnings to…
In July 2020, callers posing as Twitter IT stole staff logins and hit 130 accounts, from Obama to Musk, with…
DOJ/FTC alleged that Citizens Disability and subsidiary CD Media made 109 million-plus illegal telemarketing calls, including 25.7 million-plus to Do-Not-Call…
Someone used the White House chief of staff's phone contacts and an AI-like voice to call senators and executives, asking…
Attackers hijacked a staff email account and used fake solar-panel invoices to trick the US charity into wiring $997,400 to…
FIN7 (Carbanak) mailed USPS packages containing BadUSB hardware implants to HR, IT, and executive staff at US retail, restaurant, and…
A caller posing as Carnival's IT security team got an employee's login in April 2026. The attacker copied data on…
The SEC's 2018 Section 21(a) report detailed how fake-executive and fake-vendor BEC emails caused nearly $100 million in combined losses…
An infected USB flash drive introduced onto a U.S. military laptop in 2008 let the agent.btz worm cross onto classified…
A European subsidiary of Toyota parts maker Toyota Boshoku transferred up to about 4 billion yen (~$37M) to criminals in…
In 2025 the FBI, FTC and USPIS warned of unordered packages with QR codes that lead to phishing sites or…
Criminals posing as a vendor redirected $4.92M in North Dakota school building-fund payments in 2026. The FBI seized $4.86M. How…
JLR's 2025 cyber attack halted production for five weeks. Early reports blamed help-desk vishing; JLR's CISO later denied it. What's…