Case Library / Deepfake & Synthetic Media / KnowBe4 hires a North Korean fake IT worker (2024)
Deepfake & Synthetic Media Documented incident

KnowBe4 hires a North Korean fake IT worker (2024)

KnowBe4 hired a North Korean operative using a stolen US identity and an AI-enhanced photo in 2024. Malware started on his laptop; it was contained in 25 min.

Share:

Social Engineering Examples·11 sources

In mid-2024, KnowBe4, a company that trains staff to spot social engineering, hired a principal software engineer who turned out to be a North Korean operative. He used a real but stolen US identity and an AI-enhanced stock photo, and passed four video interviews, a background check and reference checks. When his company Mac arrived, it started loading malware. KnowBe4 says its security team spotted it and contained the laptop in about 25 minutes. Status: Company disclosure, no data loss reported.

Key takeaways

  • Background checks passed because the identity was real. It just wasn't his.
  • The photo matched the person on video every time. The deception was in the identity, not a live deepfake.
  • Endpoint monitoring caught what hiring missed.
  • KnowBe4 says no malware ran and no data, code or systems were accessed.

The hire

Check Result
Application Real US identity, stolen; photo was an AI-enhanced stock image
Interviews Four separate video calls; he matched the photo each time
Background check Clear, because the identity was valid
References Checked
Laptop A company Mac shipped to him

Tip: a clean background check proves the identity exists. It doesn't prove the person in front of you owns it.

How he was caught

On 15 July 2024 at 9:55pm US Eastern time, KnowBe4's endpoint tools flagged odd activity on the new laptop: tampering with session history, moving suspicious files, running unauthorised software, and using a Raspberry Pi to help download an infostealer. The security team called him. He said he was troubleshooting his router, refused a video call and stopped responding. KnowBe4 says the device was contained by about 10:20pm.

KnowBe4 shared its findings with Mandiant and the FBI and published the story on 23 July 2024, followed by an FAQ and, in October, a list of changes to how it hires.

Why this matters

North Korea has placed IT workers in Western companies using stolen identities, both to earn money and to get inside networks. This case is unusual because the victim wrote it up in detail, and because it's a security awareness company. If a firm that teaches people to spot social engineering can be fooled at the hiring stage, anyone can. See synthetic identity and recruitment fraud.

What stops it

  • Check identity in person or with a live ID check, not just a background check.
  • Watch for laptop delivery mismatches, like shipping to an address that doesn't match the candidate.
  • Limit new hires' access until onboarding is complete.
  • Monitor new devices closely in the first days. That's what worked here.
  • Be wary of refusals to go on camera when something goes wrong.

See also Contagious Interview, another North Korean hiring-themed operation.

Common questions

Did KnowBe4 hire a North Korean hacker?

Yes. In 2024 it unknowingly hired a North Korean operative using a stolen US identity and an AI-enhanced photo.

Was KnowBe4 breached?

KnowBe4 says no. The laptop was contained in about 25 minutes, no malware ran, and no data or systems were accessed.

How did he pass the interviews?

He appeared on video himself, matching an AI-enhanced version of a stock photo, while using a real person's stolen identity for the background check.

Was this a deepfake?

Not a live video deepfake. The photo was AI-enhanced, but he appeared as himself on calls. The identity was stolen.

Sources
Cite this case

Social Engineering Examples. “KnowBe4 hires a North Korean fake IT worker (2024)”. Accessed 3 November 2026. https://socialengineeringexamples.com/knowbe4-fake-north-korean-it-worker-2024

Attack Chain & Defense
1Identity and persona sourcing
What happened

The documented incident involved a valid but stolen US citizen identity and supporting credentials.

The control that would have stopped it

KnowBe4's documented response included stronger identity verification and related hiring-process controls after the incident.

2AI-enhanced photo preparation
What happened

A stock photograph was run through AI image-enhancement tooling to produce a synthetic headshot engineered to plausibly match the operative's real face, intended to defeat photo-to-application and photo-to-video-interview matching.

The control that would have stopped it

Reverse-image-search screening of submitted photos and requiring active liveness checks on video calls (for example, asking a candidate to turn their head or hold ID next to their face) can catch a static AI-enhanced photo that a simple side-by-side match would miss.

3Application and targeting
What happened

The operative applied through KnowBe4's normal applicant tracking system for a fully remote Principal Software Engineer role.

The control that would have stopped it

Flagging resumes for career-history inconsistencies and treating fully-remote-only availability plus a rushed timeline as a risk signal, per KnowBe4's own recommended process improvements.

4Interview infiltration
What happened

The operative sat for four separate live video-conference interviews, relying on the AI-doctored photo and rehearsed, resume-consistent answers to pass HR's photo-match and technical screening each time.

The control that would have stopped it

Training interviewers to ask spontaneous, location- and detail-specific questions, which the FBI advisory notes genuine applicants answer easily but scripted operatives struggle with, rather than relying on photo-match alone.

5Background and reference-check evasion
What happened

KnowBe4 stated that the stolen identity was real and valid, and that the background and other standard pre-hire checks came back clear.

The control that would have stopped it

KnowBe4 documented stronger identity and reference-verification measures among its post-incident hiring-process changes.

6Laptop-farm logistics
What happened

The operative requested the company-issued Mac workstation be shipped to a US address that functioned as an 'IT mule laptop farm,' consistent with the FBI's May 2024 advisory describing US-based facilitators who receive and remotely host company hardware so North Korean workers can VPN in while appearing to be US-based.

The control that would have stopped it

Shipping new-hire equipment only to a staffed pickup location requiring photo ID (KnowBe4 moved to a local UPS Store model) instead of a self-reported home address, and flagging any mismatch between the shipping address and the claimed residence.

7Post-hire endpoint compromise attempt
What happened

Immediately upon receiving the laptop, the operative began manipulating session-history files, transferring files, and using a Raspberry Pi to help download infostealer malware, likely attempting to establish persistent remote access or harvest credentials before onboarding restrictions could tighten.

The control that would have stopped it

According to KnowBe4, endpoint detection and response tooling plus 24/7 SOC monitoring, paired with a least-privilege new-hire onboarding model gating platform, source-code, and production access behind Okta until training completes, caught and contained this device within about 25 minutes.

8Objective
What happened

At KnowBe4, the attempted objective was to obtain access through the new-hire role; containment occurred before onboarding was completed.

The control that would have stopped it

Because the device was contained before the account completed onboarding or received platform, source-code, or customer-data access, the attempted access objective was denied.

Quick Facts
Victim
KnowBe4, Inc.
Company
KnowBe4, Inc.
Location
United States
(KnowBe4 headquartered in Clearwater, Florida); worker operated remotely, assessed as based in North Korea or over the border in China
Date
2024-07-15 (malware detected/contained); hiring process preceded this in mid-2024; publicly disclosed 2024-07-23
Impact
Not disclosed by KnowBe4.
Basisnot-a-lossNo loss at KnowBe4; the dollar figures belong to the wider DPRK worker ecosystem
KnowBe4 reported no data loss, compromise, or exfiltration on its systems; the cited DOJ figures concern a separate related scheme, not a reported KnowBe4 loss.
Status
Documented incident
Case Type
Real-World Incident
Sector
Cybersecurity Industry
Threat Actor
nation-state
Explore more

Related Cases

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