Lazarus Spent 5 Weeks Inside Windows
Before Microsoft Noticed the Zero-Day
North Korea’s Lazarus Group exploited a Windows kernel flaw undetected from early June through August 11. The entry point was a fake LinkedIn recruiter message. The payload was a new backdoor nobody had seen before.
The LinkedIn message looked exactly like a real recruiter reach-out. A defense engineer at a European aerospace firm received a connection request from someone claiming to represent a well-known company. The attached job description was plausible. The follow-up PDF with compensation details looked legitimate. What it actually contained was SecurityPDF — a trojaned open-source viewer that Lazarus Operation Dream Job had been distributing across defense, aerospace, and aviation targets in France, Germany, Brazil, and India since at least early June 2026.
Opening the attacker-prepared PDF inside SecurityPDF triggered a hidden payload that loaded Troy, a previously undocumented Lazarus backdoor with 17 remote commands, into memory. A second stage used MISTPEN, an in-memory downloader that communicates exclusively through Microsoft OneDrive and Microsoft Graph, to pull in the component that mattered most: an exploit for CVE-2026-68820, a use-after-free race condition in afd.sys — the Ancillary Function Driver for WinSock, the kernel-mode component that underpins every Windows network socket operation. With that exploit running, the attacker’s foothold escalated from user-level code execution to SYSTEM privileges on the full machine, and a new version of the FudModule kernel-mode rootkit planted itself deep in the Windows kernel.
Check Point Research discovered the campaign, reported the zero-day to Microsoft on July 28, received acknowledgment on July 31, and watched Microsoft assign CVE-2026-68820 on August 5 and patch it on August 11 as part of the month’s Patch Tuesday release. By then, the North Korean group had been running the exploit for roughly five weeks. CISA added it to the Known Exploited Vulnerabilities catalog the same day, with a federal remediation deadline of August 25. The CVSS score is 7.0 — Important, not Critical. Security teams that triage by severity score would have seen 42 Critical patches in the same release land ahead of it in the queue. That is exactly backwards.
How did Lazarus get in?
Fake recruiter messages on LinkedIn, impersonating well-known companies with attractive job offers. Victims were sent either a ZIP with a malicious DLL and a signed PDF viewer, or SecurityPDF — a trojaned open-source viewer purpose-built to execute a hidden payload when attacker-prepared PDFs are opened.
What is CVE-2026-68820?
A use-after-free race condition in afd.sys, the Windows Ancillary Function Driver for WinSock. When two threads race to access socket state without synchronization, an attacker can corrupt freed memory and obtain a kernel read/write primitive that yields SYSTEM privileges. Microsoft rated it CVSS 7.0 — Important.
What is Troy?
A newly documented Lazarus backdoor delivered as a 64-bit DLL with 17 remote commands covering file enumeration, upload and download, interactive command shell, DLL injection into running processes, process termination, and directory compression for exfiltration. Troy operates entirely in memory after loading.
Who did Lazarus Operation Dream Job hit?
Defense, aerospace, and aviation organizations specifically. Confirmed victim countries include France, Germany, Brazil, and India. The campaign continues Operation Dream Job, a Lazarus initiative running since 2020 that has previously targeted defense and technology professionals across dozens of countries.
How Lazarus Operation Dream Job Actually Worked
Two infection chains, same social engineering foundation
Entry pointCheck Point documented two separate infection chains running simultaneously within Lazarus Operation Dream Job’s latest wave. The first chain begins when a target receives a ZIP archive containing a legitimate, digitally signed PDF viewer called SmartaPDF.exe alongside a malicious DLL named libmupdf.dll and an encrypted payload file. When the victim opens SmartaPDF, it sideloads the DLL via DLL search-order hijacking. The DLL decrypts the payload using a hardcoded key, displays a convincing decoy PDF to avoid suspicion, and silently executes MISTPEN — an in-memory downloader that has appeared in previous Lazarus campaigns.
The second chain uses SecurityPDF, a modified version of the legitimate open-source MuPDF viewer. SecurityPDF looks and behaves like a normal PDF viewer for standard documents but contains a hidden check: when it opens an attacker-crafted PDF containing a specific embedded marker, it decrypts and executes an embedded payload using a single-byte XOR key, writes a loader to the user’s temporary directory, and reflectively loads Troy into memory. No suspicious installation dialogs, no UAC prompts for a viewer the user just installed voluntarily.
MISTPEN routes everything through OneDrive and Microsoft Graph
C2 designMISTPEN is an in-memory downloader that Check Point has observed in multiple Lazarus campaigns. Its defining characteristic is its C2 channel: it communicates exclusively through Microsoft Graph API and OneDrive, the same infrastructure that every legitimate Microsoft 365 user generates traffic through every day. From a network monitoring perspective, MISTPEN’s communications are indistinguishable from an employee syncing files to OneDrive or an application calling the Graph API for calendar or mail access. There is no suspicious domain to flag, no unusual IP to block, no self-signed certificate to catch.
After establishing communication, MISTPEN runs a reconnaissance module that profiles the compromised system — OS version, installed software, user context, network configuration — and sends the results to the operator infrastructure. Based on that profile, MISTPEN retrieves the next stage: the CVE-2026-68820 exploit module, packaged for the specific Windows 11 build running on the target machine. The exploit was built to support Windows 11 builds 26100 and 26200 specifically, which tells researchers that the Lazarus group profiled their target population carefully before selecting which Windows versions to invest exploit engineering resources in.
Lazarus Operation Dream Job’s afd.sys race condition and kernel exploit
Technical coreCVE-2026-68820 is a use-after-free vulnerability in afd.sys, the Ancillary Function Driver for WinSock. afd.sys is the kernel-mode component that manages network socket operations for virtually every Windows application — it sits at the foundation of how Windows handles TCP/IP, UDP, and all higher-level networking protocols. A use-after-free bug in afd.sys occurs when two competing threads race to access a socket state object without proper synchronization: thread A frees the object while thread B is still using it, and the attacker times the race to access the freed memory and control its contents.
In Lazarus Operation Dream Job’s implementation, successfully racing the condition yields a kernel read/write primitive — the ability to read from and write to arbitrary kernel memory addresses. From that primitive, the exploit chain elevates the attacker’s process from the user’s privilege level to SYSTEM, the highest privilege available on a Windows machine. This is the point at which the FudModule kernel-mode rootkit is installed. FudModule is a well-documented Lazarus tool that operates inside the Windows kernel to tamper with security monitoring telemetry — it was observed killing 94 security-monitoring channels in this campaign according to Techtimes coverage.
Troy — a 17-command backdoor nobody had documented before
New toolingTroy is a newly documented backdoor, delivered as a 64-bit DLL and loaded entirely in memory. Check Point’s report enumerates 17 commands: drive and directory enumeration, file listing with attributes, file upload to the operator, file download to the victim, interactive command shell execution, DLL injection into a specified running process, process termination by PID, configuration retrieval and update, directory compression and exfiltration as an archive, and several additional reconnaissance and control commands. Everything an intruder needs to conduct a complete intelligence collection operation once inside a network.
Troy operates in memory without writing persistent components to disk, which limits what signature-based endpoint detection can find on a post-incident disk image. Its communications route through the same MISTPEN infrastructure — Microsoft Graph and OneDrive — meaning that Troy’s operational traffic blends with legitimate Microsoft 365 activity at the network layer. The final backdoor in the chain is ForestTiger, a well-documented malware family with long attribution history to the Lazarus threat group, which provides the persistent foothold once the in-memory stages have completed initial exploitation and data collection.
Hijacked servers as relay infrastructure
InfrastructureRather than building dedicated attack infrastructure that could be traced back to North Korean IP ranges or known malicious hosting, the campaign’s latest wave uses compromised legitimate servers as relay nodes. The servers used were breached through a combination of leaked credentials and exploitation of known unpatched vulnerabilities — not custom zero-days. Compromised Roundcube mail servers and content management systems appear in Check Point’s indicator-of-compromise list as relay infrastructure.
This design means that organizations whose servers have been compromised and turned into relay nodes are themselves victims of the campaign even if they are not the intended intelligence targets. Their servers are handling Lazarus traffic, potentially generating log entries that could expose their infrastructure to law enforcement inquiries, and consuming bandwidth and processing resources for an operation they have no knowledge of. Check Point’s full indicator-of-compromise list includes these relay domains specifically so that organizations can check whether their own infrastructure has been enrolled in the campaign.
If your vulnerability management program
triages by severity score,
this one will land behind bugs nobody has exploited yet.
That is exactly backwards.
Why Lazarus Operation Dream Job Changes How You Triage
CVSS 7.0 exploited — why Lazarus Operation Dream Job beats the severity queue
Triage lessonAugust 2026’s Patch Tuesday contained 421 CVEs. Forty-two of them were rated Critical. CVE-2026-68820 was rated Important at CVSS 7.0. In a vulnerability management program that works through Patch Tuesday releases from highest score to lowest, that means the flaw Lazarus had been actively exploiting for five weeks was queued behind 42 vulnerabilities for which there was no confirmed exploitation. Every day that queue ran, the window for Lazarus Operation Dream Job to operate on unpatched machines extended.
The EPSS model — the Exploit Prediction Scoring System — addresses this gap. EPSS scores reflect the probability that a vulnerability will be exploited in the wild within 30 days, based on technical properties and real-world exploitation signals. A vulnerability that is already being actively exploited when the patch ships should have an EPSS score approaching 1.0. CISA’s KEV listing is the bluntest version of the same signal: if a vulnerability is on the KEV list, it has been observed exploited. That fact should move it to the front of any rational patching queue regardless of its CVSS severity band.
LinkedIn is now a declared attack surface
Social engineeringThis campaign has been running LinkedIn-based recruiting lures for years. The consistent success of the technique against defense and aerospace targets — technically sophisticated professionals who should be skeptical of unsolicited contact — reveals something important about how people process professional risk versus operational security risk. An engineer who would never open a cold email attachment from an unknown sender will open a PDF sent by a LinkedIn connection who appears to work at a company they recognize and aspire to work at.
The social engineering is doing the hardest part of the attack chain. All of the technical sophistication — the MISTPEN OneDrive C2, the CVE-2026-68820 kernel exploit, the FudModule rootkit — operates after a human being has made a voluntary decision to open a file. No vulnerability was involved in that decision. No patch can close it. The access control that failed was the employee’s judgment under conditions of motivated reasoning, and this North Korean campaign has spent six years optimizing for exactly that failure mode.
FudModule killing 94 security channels is a SOC dead zone
Post-exploitationOnce CVE-2026-68820 delivers SYSTEM privileges, Lazarus installs the latest version of FudModule — a kernel-mode rootkit the group has continuously updated since it was first documented by ESET in 2022. In this campaign’s version, FudModule was observed killing 94 security-monitoring channels according to Techtimes reporting. This is the same anti-forensics approach that DeadLock ransomware uses to wipe event logs, applied at the kernel level: rather than deleting log files, FudModule tampers with the kernel-mode structures that security tools use to hook into the OS monitoring layer, leaving those tools running but blind.
A SOC monitoring an environment where FudModule has been installed sees a machine that appears healthy — Defender is running, the EDR agent reports normal status, the event log is generating events — but every security-relevant event is being intercepted and discarded before it reaches any monitoring system. This is harder to detect than dead processes or missing log files because everything looks normal from the monitoring platform’s perspective. The only reliable detection requires something outside the endpoint’s own reporting chain: network flow analysis, hardware-level telemetry, or external red-team validation.
- Apply the August 2026 Patch Tuesday update immediately — CVE-2026-68820 is the only actively exploited Windows vulnerability in the release; it goes to the front of any rational queue
- Brief employees on LinkedIn-based recruiting lures — Lazarus Operation Dream Job’s social engineering uses professional platform context to lower suspicion; generic “unknown sender” training does not cover it
- Block execution of unknown PDF viewers dropped into temp directories — SecurityPDF and SmartaPDF are legitimate tools being abused; application allowlisting stops them before payload execution
- Monitor Microsoft Graph and OneDrive API calls for anomalous application access — MISTPEN and Troy C2 traffic is indistinguishable from normal activity without app-level telemetry
- Hunt for Troy IOCs from Check Point’s report — specific DLL hashes and file paths are publicly available; these are the highest-confidence indicators for confirming compromise
- Treat security tool telemetry gaps as a FudModule signal — if an endpoint’s EDR reporting is unexpectedly sparse, the absence of data is evidence of tampering, not evidence of clean operation
⚠️ What Patching CVE-2026-68820 Does Not Fix
1. Existing compromises are not evicted by the patch. CVE-2026-68820 is the privilege escalation step in a multi-stage chain. Patching it prevents new escalations but does not remove ForestTiger persistence, FudModule rootkit components, or any data already exfiltrated. Active threat hunting is required for any organization in the defense, aerospace, or aviation sectors that has not already confirmed clean status.
2. LinkedIn as a delivery vector stays open. The phishing lure is not a vulnerability Microsoft can patch. Organizations need to treat unsolicited PDF files from LinkedIn connections as a live threat vector and configure endpoint controls to restrict PDF viewer execution to approved, organizational software.
3. MISTPEN’s OneDrive C2 does not generate signature-based alerts. Once Troy is running, its traffic routes through Microsoft’s own infrastructure. Network controls built around blocking suspicious destinations will not flag it. Behavioral analysis of Microsoft 365 application access — specifically looking for applications accessing Graph or OneDrive from unexpected machines or user contexts — is the detection path.
The attackers used a previously unknown
Windows vulnerability to gain full control
and evade EDR visibility.