2022 · O - Public administration and defence · State-sponsored espionage intrusion via spear phishing and Active Directory credential abuse
Analysed 2026-11-06 by Hermes
Open this case in the tool →State-sponsored espionage intrusion via spear phishing and Active Directory credential abuse
Expertise to Execution
Evidence coverage: 2/6 stages, weight 9/60
Decisive stage: entry (clearest evidence) · Alternative: none defensible
(1) The expectation at the victim is the standard one for its kind: a European diplomatic entity is precisely the target set that APT29 (SVR), tracked since at least 2014, persistently phishes, so specialist-level protection of the perimeter against embassy-impersonating phishing and hygiene of Active Directory credential storage are known, available remedies. No artefact of the victim's own doctrine (policy, programme, leadership decision) is documented in any source, so no doctrinal expectation can be named. (2) In practice, in early 2022 a phishing attack succeeded and gave APT29 a foothold; during the (short) intrusion the group ran numerous LDAP queries with atypical properties against Active Directory, including the Credential Roaming attribute msPKI-CredentialRoamingTokens, and Mandiant reports it ultimately abused the Credential Roaming feature - a legacy, opt-in Windows feature that synchronises certificates, credentials and DPAPI master keys into AD attributes, where privileged access can extract and decrypt them. Mandiant detected and responded; no exfiltration or disruption was reported. (3) Both documented gaps sit in the material column and break at execution: the remedies for the documented diplomatic spear-phishing vector are known specialist controls whose absence no source attributes to any leadership decision (entry, decisive, load-bearing), and Credential Roaming was left enabled with credentials resident in the directory even though decommissioning and clean-up guidance (Microsoft's 2012 whitepaper, Grafnetter's extraction research, Mandiant's own recommendation) had long existed with specialists (containment, contributing). The zero-day reading in the case file is contradicted by the primary report - CVE-2022-30170 was discovered during the analysis of the observed LDAP queries, not exploited - so no patch-latency gap exists in this case, and the entry mechanism itself is not the basis of the type: the victim-side non-execution of known remedies is. (4) RM22 (Expertise to Execution lens): the entity's credential-management architecture kept the legacy Credential Roaming feature enabled, leaving DPAPI master keys and roaming credentials resident in Active Directory attributes; that specialist hardening and clean-up knowledge was not realised in the operational directory, leaving exactly the credential store APT29 queried during the intrusion (causal role: Enabling). RM41 (Expertise to Execution lens): after the phished foothold the attacker could reach the restricted Private-Information credential attributes and abuse the roaming mechanism - a directory-hygiene path that Mandiant's abuse scenarios tie to elevated AD privileges, though the report does not disclose the privilege level actually reached - while the documented directory hardening and clean-up steps had not been executed (causal role: Amplifying).
RM22 — Authentication / credential exposureRM41 — Privilege-escalation / directory-hygiene pathData quality: the case file states APT29 used CVE-2022-30170 to elevate privileges and codes zero_days=Yes; the primary Mandiant report instead documents that the vulnerability was discovered during Mandiant's analysis of the observed LDAP queries (submitted to Microsoft 20 April 2022, patched 13 September 2022), and SecurityWeek reports it does not appear to have been exploited in attacks - RM18 was therefore not coded and no zero-day is counted. The dataset's phrasing that Credential Roaming was exploited to gain access also overstates: phishing gave the access; the feature was abused during the intrusion. Victim unnamed and receiver_country only Europe (region), so Country stays null; victim naming is descriptive per the dataset convention. The source_url lead to Poland's CERT.PL / Military Counterintelligence advisory campaign is used via BleepingComputer reporting of that advisory (same November 2022 reporting wave, broader campaign against NATO/EU diplomatic targets); the socradar link is a general legitimate-software-abuse article and the Security Affairs newsletter a roundup - neither is cited. Mandiant's old URL mandiant.com/resources/blog/apt29-windows-credential-roaming now redirects to a homepage; the report was read at the Google Cloud live mirror and its 2023-12-13 Internet Archive snapshot.