Case Library / Agentic AI Attacks (AI-Powered Social Engineering) / Vidoc Security Lab's deepfake job interview: two fake candidates (2024 to 2025)

Vidoc Security Lab's deepfake job interview: two fake candidates (2024 to 2025)

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.

Share:

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.

Key takeaways

  • Every public account traces back to Vidoc's two cofounders. Nobody independent has verified either incident.
  • Only the second incident is evidenced. The first rests on the team's impressions.
  • The first fake candidate really could code. He aced the technical test. Skill doesn't prove identity.
  • The cheapest red flag came first: a "Polish" graduate who couldn't speak Polish.

Two candidates, two levels of evidence

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.

The tells

  • Language mismatch. The "Polish" graduate spoke no Polish. The "Serbian" one spoke no Serbian. Audible at the first screening call, and not acted on.
  • Answers with a lag, delivered as tidy, ChatGPT-style bullet points rather than conversation.
  • A background that didn't hold up. In the final interview, cofounder Klaudia Kloc pressed the first candidate on his history and stopped believing it.
  • Camera excuses, again and again.

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.

What the account can't show

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.

What stops it

Vidoc's own recommendations, plus Unit 42's:

  • Filters and backgrounds off, checked at the start of the call.
  • Record interviews, screening calls included, with proper consent.
  • Use a liveness check like the hand test, or quick head turns and lighting changes.
  • Screen the video feed itself. Deepfake candidate detection can flag a face swap during the interview, before a hiring decision rests on it.
  • Test the claimed background. Ask a claimed native speaker a question in that language.
  • Add an in-person or ID-verified final round before any offer. Vidoc now requires one on-site.
  • Don't let a strong coding score settle an identity doubt.

See also the KnowBe4 fake IT worker and CoHost's suspected fake candidate.

Common questions

What happened in the Vidoc deepfake job interview?

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.

Were both candidates deepfakes?

Only the second is on video. Vidoc suspected the first used a filter too but has said it had no evidence.

Was North Korea behind it?

Unknown. Unit 42 said the reported signs match North Korean IT worker tactics, but nobody has attributed the attempts.

Did Vidoc lose money?

No one was hired or paid. The only cost cited is "more than five hours" of interview time on the first candidate.

Sources
  • Fake Engineer - Advanced Deepfake Fraud and How to Detect It. Vidoc Security Lab (company blog) (primary). First-party company postmortem, published 2025-03-27, written by the cofounders describing both incidents directly. Re-fetched and content-matched 2026-09-02: confirms both incidents, the hand-in-front-of-face request and refusal, the politician resemblance stated as an impression, and the ebook title. Note this post is gated lead-generation collateral: it opens by promoting the company's free ebook, recommends a commercial verification tool (verifyprofile.ai), and closes on Vidoc's own product. It is a first-party account by an interested party, not a neutral write-up.
  • AI fakers exposed in tech dev recruitment: postmortem. The Pragmatic Engineer (Gergely Orosz) (primary). Deep-dive published 2025-03-11. Re-fetched and content-matched 2026-09-02. This is not independent verification: the piece is built from an interview in which "the Pragmatic Engineer sat down with Vidoc cofounder, Dawid Moczadło," and its timeline is stated to be "based on Vidoc Security's records." It is nonetheless the most detailed account, and it is the source that records the company's own admission that it had no evidence for the first incident. Section 4, "Foreign state interference?", is paywalled and was not read; nothing in this file relies on it.
  • Deepfake Fraud Prevention: 17 Practical Strategies to Detect Fake IT Workers. Vidoc Security Lab, Zuzanna Mówińska (author), 2025 (primary). The company's gated ebook. Re-fetched and content-matched 2026-09-02. It is the only source that describes the hand-over-face request being partially complied with rather than only refused, and it records the wider pattern Vidoc says it saw across applicants: repeated CVs under different Eastern European names, freshly created LinkedIn profiles with AI-enhanced photos, and an applicant whose stated home address was a Warsaw court building. Commercial collateral, and first-party.
  • WTF, developer used AI to alter his appearance during a technical interview with me. LinkedIn / Dawid Moczadło (primary). Original public post dated 2025-02-04 carrying the recording of the second incident. Re-fetched and content-matched 2026-09-02. The post states the audio was removed: "I muted his audio for privacy reasons." Every audio-based tell in this case therefore rests on recollection and is not publicly checkable.
  • Story of how an AI-generated Polish politician came to our coding interview. LinkedIn / Klaudia Kloc (primary). Posted 2025-02-27. Re-fetched and content-matched 2026-09-02. This is the same company's second cofounder recounting the same incident, so it is repetition rather than corroboration. It is the origin of the politician-resemblance detail, which it attributes to public comment ("Many people pointed out...") and frames conditionally.
  • I'm a security expert and I almost fell for this IT job scam. The Register (Jessica Lyons) (secondary). Published 2025-02-11, based on an interview with Moczadło. Re-fetched and content-matched 2026-09-02. Confirms Vidoc's San Francisco HQ, the 2025-02-04 date, the five-hour cost claim, and the DOJ's cited $88M DPRK IT-worker figure. The reporter watched the video and described visible artifacts but stated explicitly that no forensic analysis was performed. This outlet withheld the second persona's surname as an editorial choice.
  • How to Tell If Your Job Candidate is an AI Deepfake. Inc. (Emily McCrary-Ruiz-Esparza) (secondary). Published 2025-03-03. Re-fetched and content-matched 2026-09-02. Its Vidoc content is another interview with the same cofounder, and it is the source for his description of the first candidate as intuition rather than evidence. The article independently interviews other recruiters and a detection vendor about the wider phenomenon, but not about these two incidents.
  • False Face: Unit 42 Demonstrates the Alarming Ease of Synthetic Identity Creation. Unit 42, Palo Alto Networks (Evan Gordenker) (secondary). Published 2025-04-21. Re-fetched and content-matched 2026-09-02. The nearest thing to third-party analysis this case has, and it must be described precisely: its input was "indicators shared in the Pragmatic Engineer report," so it is downstream of the same first-party account and examined no evidence of its own. It found that those indicators "align with known tactics, techniques and procedures (TTPs) attributed to Democratic People's Republic of Korea (DPRK) IT worker operations." Alignment is not attribution. It also misidentifies the victim as "a Polish AI company." Its detection section, based on Unit 42's own deepfake build, is the best available technical basis for the occlusion test.
  • Vidoc Security Lab secures $2.4M investment from Top Silicon Valley VCs. AIN.ua (secondary). Corroborates the seed round as $2.4M, announced October 2024 (not $2.5M/August 2024 as recalled in the Pragmatic Engineer interview), from Pebblebed, Firestreak Ventures, XFactor Ventures, and 500 Emerging Europe; also confirms Polish founders. Verified live and content-matched.
  • Cytowski & Partners and Kondracki Celej Advise on Vidoc Security Labs' USD 2.4 Million Seed Financing Round. CEE Legal Matters (secondary). Legal-deal reporting corroborating the $2.4M figure and describing Vidoc as Gdańsk-based (legal entity) working with Palo Alto-based lead investor Pebblebed. Verified live and content-matched; this source is the origin of the corrected finding that Palo Alto refers to the investor, not to Vidoc itself.
Cite this case

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

Attack Chain & Defense
1Reconnaissance and target selection
What happened

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.

The control that would have stopped it

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.

2Persona and asset fabrication
What happened

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.

The control that would have stopped it

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.

3Unsolicited rapport-building
What happened

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.

The control that would have stopped it

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.

4Application and initial screening
What happened

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.

The control that would have stopped it

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.

5Technical assessment (first persona only)
What happened

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.

The control that would have stopped it

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.

6Video concealment
What happened

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.

The control that would have stopped it

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.

7Tells under questioning
What happened

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.

The control that would have stopped it

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.

8Liveness challenge (second persona only)
What happened

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.

The control that would have stopped it

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.

9Intended objective (not achieved)
What happened

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.

The control that would have stopped it

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.

Quick Facts
Victim
Vidoc Security Lab, a San Francisco-headquartered, Polish-founded, remote-first, AI-assisted code-security startup (also operating a Polish legal entity, VIDOC SECURITY LAB SP.
Z O.O., registered in Gdańsk) cofounded by Dawid Moczadło and Klaudia Kloc (formerly ethical hackers/bug-bounty researchers), which had raised a $600K pre-seed/seed round in 2023 and a further $2.4M seed round in October 2024 (from Pebblebed, Firestreak Ventures, XFactor Ventures, and 500 Emerging Europe) and was hiring backend engineers for a Poland-based remote role at the time of both incidents.
Company
Vidoc Security Lab
Location
San Francisco, USA (Vidoc Security Lab's company HQ, confirmed by the company's own LinkedIn page and multiple company-data sites; a Palo Alto address belongs to lead investor Pebblebed, not to Vidoc itself) and Gdańsk, Poland (its Polish legal entity, VIDOC SECURITY LAB SP.
Z O.O.; the company was Polish-founded by Dawid Moczadło and Klaudia Kloc). The open backend-engineer role being hired for was a Poland-based remote position. Fake candidates claimed to be located in Poland and Serbia respectively.
Date
First incident: approx. December 2024 (exact date not published in primary sources; Inc. places it in late 2024).
Second incident: 2025-02-04 (per Dawid Moczadło's LinkedIn post, which says it happened that day). Vidoc Security Lab's own postmortem blog post published 2025-03-27; The Pragmatic Engineer newsletter deep-dive published 2025-03-11 (based on interview with cofounder before the blog post went up); Unit 42's commentary on the reported indicators published 2025-04-21.
Impact
No confirmed direct financial loss: neither candidate was extended an offer or paid a salary, and no funds were transferred.
Basisnot-a-lossNo offer extended and no funds moved; the only cost cited is interview time
The only quantified cost is Moczadło's statement to The Register about the first candidate, "We spent and lost more than five hours on him." That is a claim by an interested party recalling the event, not a measured accounting figure, and it covers the first candidate only. Remaining costs were operational and opportunity costs: recruiter and cofounder interview time, a disrupted hiring funnel for a role sourced from roughly 500 applications, and the security risk that would have materialized had either impostor been hired into a codebase-access engineering role at a security company. No dollar figure has been published by any source.
Status
Reported/alleged incident
Case Type
Real-World Incident
Sector
Cross-Sector / Multiple Industries, Cybersecurity Industry, Technology & Software
Threat Actor
unknown
Explore more

Related Cases

Browse by what this case has in common with others in the library.