2019 · Pakistan · O - Public administration and defence · Cyber-espionage via spear-phishing malware campaign (data theft, system hijacking)
Analysed 2026-11-06 by Hermes
Open this case in the tool →Cyber-espionage via spear-phishing malware campaign (data theft, system hijacking)
Expertise to Execution
Evidence coverage: 3/6 stages, weight 17/60
Decisive stage: entry (clearest evidence) · Alternative: Expertise to Leadership
(1) Pakistani government, defence and intelligence institutions were expected to defend their endpoints against a threat actor openly documented as targeting Pakistan since at least 2012 and using macro-based spear-phishing since at least 2018; the victim's own national cyber body (NTISB, Cabinet Division) formalised exactly these expectations in Advisory No. 18 (June 2019), ordering limited-privilege users, Software Restriction Policies against binaries from %APPDATA%/%TEMP%, operational endpoint and network firewalls, C2 blocking and PowerShell monitoring. (2) In practice, from March to July 2019 SectorE02's spear-phishing Excel documents reached these institutions, victims enabled macros, the YTY downloader and plugins ran, per-campaign recreated binaries kept antivirus detection 'Very low', and file, screenshot and keylogger plugins staged collected data that an uploader plugin sent to attacker servers. (3) This is an Expertise to Execution gap: the missing element was not strategic direction - the remedies sat with technical specialists, required no strategic decision and were in fact prescribed by the victim's own advisory - the chain broke in operational realisation, with government endpoints still executing payloads from user-writable paths, detection untouched and exfiltration unimpeded. The classification rests on the entry stage, whose origin and break are best documented (primary vendor forensics plus the government's own advisory); the detection and egress gaps point to the same type, so no tie-break is needed. The entry vector is documented and not load-bearing by itself: what carries the classification is the victim-side ineffectiveness of known endpoint controls, not the phishing technique. (4) RM28 (Expertise to Execution lens): endpoint and malware protection across the victim institutions stayed ineffective against a repeatedly documented macro-Excel TTP - payloads executed from user-writable paths while antivirus detection was rated 'Very low' by both the vendor report and Pakistan's own advisory, the very gap its prescribed SRP and application-control measures targeted (causal role: Enabling). RM34 (Expertise to Execution lens): available detection capability was not configured, tuned or maintained to catch this activity - the months-long campaign was surfaced by the external firm NSHC rather than the victims' own monitoring, and the advisory's instructions to enable PowerShell logging and keep firewalls operational show those capabilities were not in place operationally (causal role: Obscuring). RM35 (Expertise to Execution lens): staged data left the networks as routine HTTP uploads to attacker servers without detection or interruption, although egress prevention was possible and formally prescribed - the advisory expressly ordered organisations to blacklist the published C2 servers in their firewalls (causal role: Amplifying).
RM28 — Endpoint / malware-protection gapRM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapEuRepoC row: no receiver_name - victim named descriptively from receiver_category/subcategory (Government / ministries; Intelligence agencies). Case description matches the stated victim. The NTISB advisory does not name the actor; it documents the same 2019 multi-vector campaign wave against Pakistani defence/government organisations (its IOCs - gov-pk.org LNK/PowerShell variant - sit alongside NSHC's XLS-macro variant of the March-July 2019 campaign, which NSHC illustrates with a Pakistani government security advisory). The advisory PDF on cabinet.gov.pk was read via its text layer; the FBR-hosted copy (dated 25 June 2019) is an image-only scan that could not be read with the available tools, so the exact issue date is given as June 2019. Attribution rests on technical reports of the IT-security community (EuRepoC attribution basis); later reporting (Amnesty 2021 / ESET 2022) links the infrastructure to an Indian company that denies involvement - actor context only, not load-bearing for the DV assessment. Agency-level detection/notification status is not documented; the detection gap is read from external disclosure of the campaign. No related_rows in the case file.