2023 · Russia · O - Public administration and defence · Data theft and doxing via social engineering of military family members
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft and doxing via social engineering of military family members
Strategy to Execution
Evidence coverage: 3/6 stages, weight 14/60
Decisive stage: entry (clearest evidence) · Alternative: Expertise to Execution
(1) The strategic expectation at a regiment of the Russian Air Force and its ministry is doctrinal: OPSEC rules that also cover military families (dependents do not share identifying information, official contacts are verified) and data-handling rules that keep regiment records out of private mailboxes and weakly protected portal accounts. (2) In practice the commander's wife was contacted by a hacker posing as an officer of her husband's regiment and, with no verification procedure available to her, organised a 'patriotic photoshoot' in which 12 officers' wives posed on the airfield in dress uniforms with ranks and medals in clear view, letting the attackers identify pilots, duty stations and aircraft; the group also accessed the colonel's MoD portal account for his salary statements and worked through months of his private mailbox correspondence, from which pilot lists, evaluations and memos were published. (3) That is a knowing-doing gap inside the doctrinal column's translation into practice: the expectations existed as standing military doctrine but were not operationalised at this unit - no verification path or deception training for the officer-family network, no enforcement of data-handling rules - so formal doctrine never became operational reality; this is Strategy to Execution rather than merely weak security. The technical entry into the mailbox is not documented and is not load-bearing; the detection gap (months of undetected control) rests solely on the attackers' own claim and was not allowed to decide the type. The classification rests on the entry stage, the best documented in independent reporting. RM24 (Strategy to Execution lens): awareness, verification and acceptable-use requirements for the unit's community were never translated into procedures the families could apply, so a fabricated regiment officer could gather identifying data from thirteen households without any check (causal role: Enabling). RM34 (Strategy to Execution lens): monitoring and alert-handling for the commander's accounts, if required by doctrine at all, was not operated - the attackers report months of undetected correspondence control and the victim never detected anything itself (causal role: Obscuring). RM16 (Strategy to Execution lens): classification and handling requirements for personnel and operational data were not implemented in practice - the regiment's pilot lists, evaluations, memos and the colonel's salary statements sat reachable in a private mailbox and a single portal account, amplifying one deception into a regiment-wide exposure (causal role: Amplifying).
RM24 — Human-factor / social-engineering susceptibilityRM34 — Monitoring / detection / alert-handling gapRM16 — Data governance / minimisation gapAll operational detail originates in the attacker disclosure (Cyber Resistance via InformNapalm, 27-03-2023); the Russian MoD and the colonel never commented, so mechanism claims are attacker statements relayed by press (Vice/Motherboard, Hackread, Just Security) - confidence reflects that. The InformNapalm page is cited as the attacker-side disclosure report; no leaked dump data was accessed. Source-quality caveat: the case file's databreaches.net source_url describes a different Cyber Resistance episode (a pro-Russian blogger's AliExpress account, April 2023) and the corriere.it link is a war live-blog; neither is cited. The victim column pairs an individual (Col. Atroshchenko) with the MoD; the photoshoot deception targeted his family network and the MoD portal account was the data source. Related row 1626 (Ministry of Defence (Russia), result read) is a separate, later and disputed 2024 GUR claim classified Unknown there; nothing there bears on this row, and no comparable earlier unremediated weakness is established (RM21 not coded). Case files of related rows 3273, 3388, 3396 and 3406 are not present in the run's case folder, so nothing is stated about their incidents. Personal data of the colonel's family is recorded only as public reporting describes the incident. Link check: informnapalm.org blocks automated access (HTTP 403); the page was opened and read during research.