2022 · Ukraine · O - Public administration and defence · Phishing intrusion attempt with infostealer malware against military users
Analysed 2026-11-06 by Hermes
Open this case in the tool →Phishing intrusion attempt with infostealer malware against military users
Expertise to Execution
Evidence coverage: 1/6 stages, weight 6/60
Decisive stage: entry (clearest evidence) · Alternative: none defensible
(1) Delta is the real-time battle-management and situational-awareness platform of Ukraine's armed forces, developed by the Defense Technology Innovation and Development Center with the Ministry of Digital Transformation and international partners; the victim organisation states cybersecurity is its priority, with multi-level protection, suspicious-behaviour detection protocols and regular vulnerability checks by international partners, and the known remedies for account takeover and infostealer delivery (credential monitoring, account protection, endpoint and mail defences) are standard for an organisation of this kind. (2) In practice, in mid-December 2022 the group CERT-UA tracks as UAC-0142 used a compromised Ministry of Defense employee email account and messengers to send Delta users fake root-certificate update notices whose PDF lures led to a signed, VMProtect-packed dropper on a fake Delta domain, deploying the RomCom RAT with the FateGrab and StealDeal stealers on user computers; CERT-UA's advisory documents the full execution chain, and the MoD said the incident was detained in the preparation stage, with no public indication that data theft succeeded. (3) The victim-side gap is therefore not a strategic one: no source shows a deferred decision, an unfunded programme or a discounted warning; the condition sits entirely in the material column - official-account credentials were exposed and monitoring did not catch the takeover before it was abused, and a code-signed, packed infostealer chain executed on user machines despite the known remedies - i.e. expertise and remedies existed but were not realised in operations: material origin, execution break. The classification rests on the entry stage, the only stage with a documented gap; detection, response and disclosure evidence points to alignment (advance CERT-UA tracking of activity against Delta users, report to CERT-UA within two days, prompt official disclosure, impact contained). The entry vector itself (phishing via the compromised account) is documented, but why the account and endpoint safeguards failed is not stated by any source, which caps confidence. (4) RM22 (Expertise to Execution lens): credential protection and monitoring did not detect that a legitimate MoD employee email account was under attacker control, so the takeover was not caught before the attacker used that trusted channel to reach Delta users - the identity-hygiene remedy was available but not executed on that account (causal role: Enabling). RM28 (Expertise to Execution lens): endpoint and mail defences proved ineffective against an infostealer toolkit already observed against Ukrainian organisations in the preceding months - a signed, VMProtect-packed chain delivered by email and messenger ran on user computers - so endpoint protection as a known control was not operationalised in the user environment (causal role: Enabling).
RM22 — Authentication / credential exposureRM28 — Endpoint / malware-protection gapTerminology caveat: the row description says the group compromised Delta, but the sources opened characterise the campaign as an attempt stopped before leverage - the MoD spokesperson said it was detained in the preparation stage, and The Record ran a correction saying the software was targeted, not breached; the EuRepoC impact fields record hijacking-not-used, no disruption and no data breach. The detained-in-preparation claim is one-sided (victim statement, no independent verification). Related row 3351 has no case file in cases-run500, so it could not be cross-read; the The Record article opened here describes the August 2022 predecessor (a fake Delta phishing site that took one user's data) - RM21 was considered for that recurrence but not coded, because the December campaign is characterised by the spokesperson as the first social-engineering attack on the system, it was stopped in preparation, and no source shows the earlier lessons were left unimplemented. Attribution: UAC-0142 is CERT-UA's tracking designation (attribution by the receiver government, media-reported, no independent confirmation); the unattributed actor does not affect the victim-side DV. No consent-requiring actions were needed or taken (unattended run).