The lure looked professional
A recruiter and a familiar employer name opened the conversation.
Check PointAn authentic signal does not tell you who controls the message that carries it.
In a new Operation Dream Job wave, attackers linked an employer name, signed software, OneDrive, a Windows zero-day and compromised resources in one route. Each element looked familiar. Together, they moved the victim from a recruitment conversation to infrastructure for the next attack.
Choose a signal. See what was genuine and how it was used.
"Real" describes a thing. "Safe" describes its relationship with the rest of the chain.Evidence status
Microsoft patched it and CISA listed it as actively exploited.
The attribution belongs to Check Point's analysis.
The organisation is not named publicly.
The research does not say what information was exfiltrated.
The new signal
Fake job offers linked to Lazarus have appeared before. In this wave, recruitment connected to genuine software, search results, OneDrive, a kernel zero-day, compromised web servers and an organisation used for later messages.
Check Point reports successful targeting in Western Europe, including France and Germany; the campaign also targeted other regions. A familiar domain, a valid signature or a mainstream cloud service describe the object itself. A defender must also check who introduced it into the message and how it connects to the rest of the route.
"Real" describes a thing. "Safe" describes its relationship with the rest of the chain.
01 · What happened
Check Point describes the campaign in four moments. The sequence below follows that reconstruction; the source does not publish a complete list of victims or their impact.
A recruiter and a familiar employer name opened the conversation.
Check PointA signed PDF viewer and OneDrive made the installation and traffic look ordinary.
Check PointCVE-2026-68820 in Windows AFD.sys enabled privilege escalation to SYSTEM.
CISACompromised web servers carried the traffic, and the organisation in France was used as the sender for later messages.
Check Point02 · The signals
Each row shows a signal used in the campaign. Open it to see what it confirms and what it leaves unverified.
The name was familiar. The published research does not indicate company involvement in the campaign. Open source: Check Point Research
An attacker can use a company name and a recruiter profile in a conversation about work or technology. Open source: Check Point Research
The signature confirms where the file came from. It says nothing about why the sender placed it in the chain. Open source: Check Point Research
A high search ranking made the pages look more credible. Open source: Check Point Research
A real service can carry malicious traffic. Open source: Check Point Research
Microsoft patched the vulnerability on 11 August 2026. CISA listed it as actively exploited. Open source: CISA · Known Exploited Vulnerabilities
The organisation is not named publicly. Attackers used its reputation to make later messages look credible. Open source: Check Point Research
Check Point identified at least 17 identifiers associated with likely compromised servers. Open source: Check Point Research
The investigation describes Troy, FudModule v3.1 and RelayShell as parts of the attack. Open source: Check Point Research
genuine in itself, while still usable in a malicious chain
an identity, page or context imitates a familiar signal
a legitimate resource was taken over and used by someone else
the component or action is part of the attack
03 · Privilege escalation
The timeline connects the recruitment message to the vulnerability that enabled SYSTEM access and the patch that followed.
CISA lists CVE-2026-68820 as actively exploited, and Microsoft published the patch on 11 August. The Lazarus / DPRK attribution comes from Check Point's analysis.
Researchers send it to Microsoft.
Microsoft begins coordinated remediation.
The vulnerability receives its public identifier.
Microsoft publishes the fix and CISA adds it to Known Exploited Vulnerabilities.
The Record treats confirmed exploitation and Check Point's attribution separately.
04 · Victim reuse
Check Point describes two ways the victim was reused. Compromised web servers carried implant communications, while the organisation in France was used as the sender for spear-phishing. Choose one branch.
Traffic passes through a compromised legitimate server and looks like ordinary HTTPS traffic.
compromised and reused
Roundcube / CMS + RelayShell
use a compromised server as a relay
the message appears to come from it
spear-phishing messages to other organisations worldwide
05 · What we know
This section separates documented facts, Check Point's attribution, the inference about technical continuity and information the research does not publish.
Microsoft patched CVE-2026-68820, and CISA listed it in the KEV catalogue as actively exploited.
Open source: CISA · Known Exploited VulnerabilitiesCheck Point attributes this wave to Lazarus / DPRK actors. Microsoft and CISA document the vulnerability and exploitation; the attribution comes from Check Point's analysis.
Open source: Check Point ResearchFudModule previously used a vulnerability in the same AFD.sys driver. That may indicate sustained attention to the same attack surface. This is an editorial inference; the source does not say who discovered each bug.
Open source: Check Point ResearchThe research does not say what defence information was exfiltrated from each victim, who used it or whether the operation changed any weapons programme.
Open source: Check Point ResearchThe Romanian question
The public material does not disclose a Romanian victim. Check Point's analysis names defence, drones, surveillance sensors, robotics and aerospace among the sectors involved. Romanian suppliers in those sectors are a question for separate checking; the page does not report a compromise.
See the target categories in Check Point's analysisWhat to check next time
When a message looks legitimate, ask:
In this campaign, the compromised organisation was used for the traffic and messages that followed.
Sources and limits
Check Point describes the campaign and the infrastructure it used. Microsoft published the patch, and CISA confirmed the actively exploited listing. The Record treats the exploitation record separately from Check Point's attribution.
Reconstruction of the campaign, its malware, relay servers and later use of the French organisation.
CVE-2026-68820 listed as actively exploited.
The official vulnerability record and Microsoft patch.
Separates the patch and exploitation record from Check Point's DPRK attribution.
Re-review if primary sources change the description of exploitation, the CVE-2026-68820 status, the attribution or the public information about victim impact.