2022 · Afghanistan · O - Public administration and defence · Cyber espionage (state-sponsored compromise of government networks)
Analysed 2026-11-06 by Hermes
Open this case in the tool →Cyber espionage (state-sponsored compromise of government networks)
No DV evidenced
Alternative: none defensible
(1) Strategic expectation at the victim: the affected organisations are state institutions (Afghan Ministry of Foreign Affairs, General Directorate of Intelligence, government ministries and consulates) whose networks carry sensitive government information; no source documents any Afghan policy, programme or control relevant to these networks, so no doctrinal expectation can be evidenced. (2) What happened in practice: between December 2022 and mid-2023 Storm-0156 used backdoors such as CrimsonRAT and Waiscot to compromise Afghan government networks for espionage; from December 2022 the Russian state actor Secret Blizzard (Turla) had also infiltrated Storm-0156's command-and-control infrastructure and from that position deployed its own malware (TwoDash, Statuezy) into the same Afghan government networks, with beaconing and significant data transfers observed from Afghan networks into 2024; how Storm-0156 initially entered the Afghan networks is not disclosed in the incident-specific reporting. (3) Why this is Unknown rather than a DV-Type: the classification requires a concrete, verifiable victim-side failure point on one of the axes, and here the reporting confirms impact only. The incident was disclosed in December 2024 by IT-security companies (Lumen Black Lotus Labs and Microsoft Threat Intelligence) studying the attackers' infrastructure; there is no statement from the Afghan authorities, no regulator or CERT finding, and nothing documented about the victim's detection, containment, recovery or response - not even whether the intrusions were ever noticed. The detection and dwell-time stages would only rest on the coder's own inference from beacon durations, which the method excludes as a basis; statements that Afghanistan's cyber capacity is weak are country-level context, not incident-specific mechanism. A secondary pattern that is visible is atypical, attacker-side: the second event in the row's description is one state intelligence actor hijacking another threat actor's access (Turla commandeering Storm-0156's C2 nodes and operator workstations), which has no victim organisation in the framework's sense. The entry vector is undisclosed and not load-bearing for any classification.
Data quality: the row's description merges two linked events from the same vendor research - Storm-0156's compromise of Afghan government networks (the row's incident) and Turla/Secret Blizzard's infiltration of Storm-0156's C2 nodes and operator workstations, reusing that access against the Afghan networks (the Turla part is atypical, attacker-side). The second source_url (zataz.com, an Auchan loyalty-card leak article) is unrelated to this case. eurepoc_extra.intelligence_impact ('No data breach/exfiltration...') contradicts incident_type/data_theft and the beaconing with significant data transfers that Black Lotus Labs documented from Afghan networks. Disclosure: by IT-security companies (Black Lotus Labs and Microsoft, 04-12-2024); the Afghan authorities never commented and no Afghan statement, CERT/regulator action or recovery/response record was found in English-language reporting; Afghan media coverage of Taliban-era cyber incidents (TalibLeaks 2025, Afghan Dragons 2025) describes different incidents and was not used. Set to Unknown because the sources confirm impact only and document no victim-side mechanism at any lifecycle stage; the entry vector of Storm-0156 into the Afghan networks is undisclosed.