← Breach analysis by the Dual Vulnerabilities framework

Ukrainian military backdoor campaign (Secret Blizzard, 2024)

2024 · Ukraine · O - Public administration and defence · State-sponsored espionage: backdoor deployment via hijacked criminal botnet

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

State-sponsored espionage: backdoor deployment via hijacked criminal botnet

Dual vulnerability type

Expertise to Execution

Evidence coverage: 2/6 stages, weight 12/60

Decisive stage: detection (clearest evidence) · Alternative: none defensible

Why this classification

(1) The devices sat in a state-defence environment targeted by one of the most closely tracked espionage actors (CISA attributes Secret Blizzard to FSB Center 16), where the baseline technical expectation is that endpoint anti-malware stays enabled and monitored - and the Defender tool that carries detections for Amadey, Tavdig and Kazuar was in fact present on the devices. (2) In practice, between March and April 2024 a commodity Amadey bot took hold on specifically selected Ukrainian military devices; Microsoft states that several of the targeted devices had Microsoft Defender disabled during initial infection, the attacker's survey tool inspected Defender's detection-log folder to confirm nothing had flagged, and the Tavdig and KazuarV2 implants were only observed by Microsoft weeks or months after deployment, with disclosure coming from Microsoft in December 2024, months after the campaign. (3) This is a knowing-doing gap inside the material column: the remedy was technical, available and already installed (origin material), yet it was not realised in device operations - the protection ran disabled and victim monitoring never caught a publicly documented, signature-covered malware family (break execution). It is not a Strategy-to-* gap because no source documents any victim policy, programme or leadership decision bearing on the control, and not Expertise to Leadership because no source shows experts warning leadership; who disabled Defender and why is undisclosed, so the execution placement is inferred from the documented facts. The initial delivery path of the Amadey bot itself is undisclosed and is not load-bearing; the classification rests on the detection stage (entry shows the same gap). (4) RM28 (Expertise to Execution lens): the endpoint protection tool existed but its coverage was not realised on the front-line device fleet - several targeted devices ran with Defender disabled during initial infection, so a commodity Amadey bot executed unimpeded and delivered the backdoor chain (causal role: Enabling). RM34 (Expertise to Execution lens): the available tooling was not configured or maintained to detect the activity - the attacker could query Defender's detection logs to confirm nothing had fired, and the implants surfaced only to an outside vendor weeks or months after deployment, not to the victim's own monitoring (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row: receiver_name missing, victim named descriptively from receiver_subcategory 'Military' and the Microsoft report ('devices associated with the Ukrainian military'). The dataset's incident_type 'Hijacking without Misuse' refers to attacker-side hijacking - Secret Blizzard commandeered the Amadey/Storm-1919 botnet and a Storm-1837 backdoor - not to victim infrastructure, so it does not change the victim-side reading. Who disabled Defender and why is not documented; the execution break is inferred from the documented facts (stage source type: inference). No victim statement exists; disclosure was by IT-security company (Microsoft, 11-12-2024). Earlier comparable incident: CERT-UA reported a Turla Kazuar espionage campaign against Ukraine's Defence Forces in July 2023 (February 2023 phishing campaign, as summarized by LevelBlue), and Microsoft notes this is at least the second use of a cybercrime foothold in Ukraine since 2022; the recurrence is noted here and RM21 was not coded because no source links a documented 2023 recommendation that went unimplemented to this 2024 campaign. The January 2024 Storm-1837/COOKBOX foothold in the same Microsoft report is part of the same case narrative. Research done within policy: only vendor reports, established press and a security-vendor retrospective were opened; no leak sites or attacker infrastructure were contacted.